![\"\"](\"https:\/\/www.seven-stones.biz\/blog\/wp-content\/uploads\/boot-manager.jpg\")
<\/a><\/figure>\n\n\n\nHere is my setup: <\/p>\n\n\n\n
- \n
- Apple MBP M4<\/li>\n\n\n\n
- VMware Fusion 13.6.3<\/li>\n\n\n\n
- VM – Ubuntu 24.04 Server ARM<\/li>\n<\/ul>\n\n\n\n
Maybe this article is not for you – here’s a quick summary to help you decide for yourself; create an Ubuntu ARM Server (Server was the only ARM version in Ubuntu town) bootable disk, attach the USB drive to the VM, boot from the USB drive, break out of the Ubuntu Server install and drop to a shell (this was not straightforward – see below), mount the correct \/dev devices on \/mnt and \/mnt\/boot\/efi, along with dev, proc, etc directories. From here there’s one or both of two deviants who are liikely guilty – GRUB<\/a> corruption, or kernel corruption. In my case it was GRUB corruption and the fix is below… <\/p>\n\n\n\n
The Bootable Disk<\/h2>\n\n\n\n
This was a very helpful article: Create a bootable USB stick on Ubuntu<\/a> – this should have got you all the way to a bootable USB drive. The iso to use is of course the ARM server version if you on M1-4 Mac. At the time of writing there is no Ubuntu Desktop 24 for ARM architectures. <\/p>\n\n\n\n
Connecting Your USB Drive To Your VM<\/h2>\n\n\n\n
Having followed the link Create a bootable USB stick on Ubuntu<\/a> , you will have got your MBP to recognise the USB drive. Boot your VM. You may not see the USB as a selectiable boot drive in the top menu, in which go down to ‘Reset The System’. This worked for me. Boot from the USB drive. <\/p>\n\n\n\n
Ubuntu ARM Server install Breakout<\/h2>\n\n\n\n
You should see the following Grub screen … <\/p>\n\n\n\n
![\"\"](\"https:\/\/www.seven-stones.biz\/blog\/wp-content\/uploads\/grub.png\")
<\/a><\/figure>\n\n\n\nThere is an option there – ‘Try or Install Ubuntu Server’. The menu is lying to you – do not believe it. There is no ‘try’, there is only install. Unless you find an off-script way to break out. Hit enter for the try\/install option and then select the help option in the top right (as below), within which menu there is a shell option …<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.seven-stones.biz\/blog\/wp-content\/uploads\/USB-installer-shell-breakout.png\")
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
Mounting Your Ubuntu Drive and Repairing Your GRUB<\/h2>\n\n\n\n
Entering the shell, you are in a world where you are running a shell of the OS from the USB drive. You are not yet on the planet you want to be on, which is your broken Ubuntu 24 partition. <\/p>\n\n\n\n
List your devices<\/h3>\n\n\n\n
From the shell prompt use the command: <\/p>\n\n\n\n
lsblk<\/code><\/pre>\n\n\n\nThis will list the filesystems by device. One of them will be your boot partition, another will be the device that holds your broken VM’s root filesystem. In my case the 2 partitions of interest were
\/dev\/nvme0n1p1<\/code> and\/dev\/nvme0n1p2<\/code>, the latter of which is my root partition.<\/p>\n\n\n\nMount these two partitions<\/h3>\n\n\n\n
- \n
mount \/dev\/nvme0n1p1 \/mnt<\/code><\/li>\n\n\n\nmount \/dev\/nvme0n1p2 \/mnt\/boot\/efi<\/code><\/li>\n<\/ul>\n\n\n\nYou should see your famiiliar old files and directories under \/etc and \/home. <\/p>\n\n\n\n
Mount the necessary system directories:<\/h3>\n\n\n\n
for i in proc dev sys; do mount --bind \/$i \/mnt\/$i; done<\/code><\/p>\n\n\n\nChroot into your not-booting VM:<\/p>\n\n\n\n
chroot \/mnt<\/code><\/p>\n\n\n\nPost-chroot Diagnostic Steps<\/h3>\n\n\n\n
Re-install the kernel… <\/p>\n\n\n\n
- \n
apt update<\/code><\/li>\n\n\n\napt install --reinstall linux-image-generic<\/code><\/li>\n<\/ul>\n\n\n\nCheck the contents of the EFI folder:<\/p>\n\n\n\n
ls \/mnt\/boot\/efi<\/code><\/pre>\n\n\n\nYou should see something like this: <\/p>\n\n\n\n
EFI\/\n\u2514\u2500\u2500 ubuntu\/\n\u251c\u2500\u2500 grubaa64.efi\n\u2514\u2500\u2500 grub.cfg<\/code><\/pre>\n\n\n\nIf the directory is empty, you need a GRUB fix…<\/p>\n\n\n\n
Hopefully you don’t need to reinstall GRUB. This should be enough: <\/p>\n\n\n\n
update-grub<\/code><\/pre>\n\n\n\nTo re-install: <\/p>\n\n\n\n
grub-install --target=arm64-efi --efi-directory=\/boot\/efi --bootloader-id=ubuntu --recheck\n\nupdate-grub\n\n<\/code><\/pre>\n\n\n\nin my case i did not need to re-install GRUB, the update was sufficient.<\/p>\n\n\n\n
Restart<\/h3>\n\n\n\n
umount \/mnt\/boot\/efi\numount \/mnt\nreboot<\/code><\/pre>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
I recently encountered a situation where my Ubuntu 24.04 VM was failing to boot. The blue screen DOS-style Boot Manager would be displayed and booting was halted here, with an implicit ‘you shall not pass’. This post covers how i addressed the problem, Continue reading