Grub Rescue prompt is shown and computer doesn't boot into OS.

Question

Grub Rescue prompt is shown and computer doesn't boot into OS.

SamilKaraduman opened this issue a year ago · comments

Ever since I reinstalled Ubuntu on my computer, it booted only once into Ubuntu (first setup) and every time after that refused to boot. Uboot, (or rather grub) displays a grub rescue prompt looking like the one in the picture. How can I resolve this?

OS: Ubuntu 23.04 Lunar Lobster
Host: MBA (M1, 2020)

Any help is heavily appreciated.

Ernest Tapias commented a year ago

same

Tobias Heider commented a year ago

yes

Tobias Heider · Answer 1 · Wed Jul 05 2023 14:02:37 GMT+0800 (China Standard Time)

Hi @SamilKaraduman, there was a known bug that caused similar problems, but I thought that was fixed. Did you reinstall recently?

Samil Karaduman · Answer 2 · Wed Jul 05 2023 21:52:10 GMT+0800 (China Standard Time)

Yes, I have reinstalled recently. About a day ago to be precise.

Tobias Heider · Answer 3 · Wed Jul 05 2023 23:27:09 GMT+0800 (China Standard Time)

Sounds like bad news. Last time it was caused by a race in the first-boot script, so it wasn't triggered reliably. You could try reinstalling and see if first-boot.service succeeds before rebooting the machine. I will try to replicate it on my test machine, but that will take a few days.

Samil Karaduman · Answer 4 · Wed Jul 05 2023 23:53:08 GMT+0800 (China Standard Time)

Sure. I can do that. But I also want to clear boot policies on my drive, since too many can also cause problems. But how would I go about doing that?

Tobias Heider · Answer 5 · Thu Jul 06 2023 02:58:33 GMT+0800 (China Standard Time)

I usually start into recovery mode, open a terminal there and run curl -L https://alx.sh/cleanbp | sh to clean the boot policies. Watch out though because I think that nukes everything but macos.

Samil Karaduman · Answer 6 · Thu Jul 06 2023 04:40:52 GMT+0800 (China Standard Time)

Cleaned the boot policies. The script worked just fine, and I rebooted into macOS. I then reinstalled Ubuntu (before the script I already removed Ubuntu from my computer) and everything went fine, I booted into Ubuntu, got everything setup until the next boot... Grub/Uboot still gave me the grub rescue screen. What do I do now? I haven't poked around with anything and now I am unable to boot into Ubuntu.

Tobias Heider · Answer 7 · Thu Jul 06 2023 05:59:58 GMT+0800 (China Standard Time)

ok, so what we need is the actual error message. I am assuming what's failing is the first-boot script, so we need the output of sudo journalctl -eu first-boot after a fresh reinstall. I can't reproduce it on my machine so I will need some help here.

Samil Karaduman · Answer 8 · Thu Jul 06 2023 06:28:13 GMT+0800 (China Standard Time)

So I'm gonna need to do a 3rd install?!?!

Tobias Heider · Answer 9 · Thu Jul 06 2023 06:33:53 GMT+0800 (China Standard Time)

Not necessarily. The alternative would be booting an usb image like https://files.tobhe.de/ubuntu/ubuntu-desktop-live-23.04-20230329.img by flashing it to a usb drive and typing run bootcmd_usb0 into the u-boot prompt, then mounting the ubuntu filesystems, chrooting into the mounting system and fixing it from there.

I think running sudo update-grub might be enough to fix it, but I can only guess with the little info I have right now.

Samil Karaduman · Answer 10 · Thu Jul 06 2023 08:43:03 GMT+0800 (China Standard Time)

Used dd to flash the image onto a spare flash drive of mine, and it also gives a grub rescue boot menu. Perhaps something is corrupted with the latest images?

Tobias Heider · Answer 11 · Thu Jul 06 2023 15:10:48 GMT+0800 (China Standard Time)

urgh no this actually makes a lot of sense. the usb is build from the same script as the regular install so their filesystem UUIDs collide (further hardening the suspicion that this is a first-boot bug). Another usb image such as https://arvanta.net/alpine/install-alpine-m1/ should work.

Samil Karaduman · Answer 12 · Thu Jul 06 2023 23:53:38 GMT+0800 (China Standard Time)

sigh Tried to boot Alpine, and I still got a grub rescue error! I then tried booting Fedora, another grub rescue prompt! Something is definitely very wrong here...

dheerajgattupalli · Answer 13 · Fri Jul 07 2023 13:48:17 GMT+0800 (China Standard Time)

I am facing similar issue, I am working with a bluetooth keyboard so actually stuck at grub rescue... @SamilKaraduman did you try the update-grub command?

Tobias Heider · Answer 14 · Fri Jul 07 2023 15:24:37 GMT+0800 (China Standard Time)

@dheerajgattupalli and this also happened after a fresh 23.04 install's first reboot? Would you mind trying to reproduce it and BEFORE you configure everything and restart the system share your systemd journal and in particular sudo journalctl -u first-boot?

dheerajgattupalli · Answer 15 · Fri Jul 07 2023 15:39:43 GMT+0800 (China Standard Time)

log_firstboot.log

here is the log, didnt restart yet.. let me know if you need anything else

btw I am using a Mac Mini M1 with Ventura 13.4 ..

Edit: I seeing some random UUID set for devices, not sure if its relevant I have a external hard disk always connected to the mac mini..

Tobias Heider · Answer 16 · Fri Jul 07 2023 15:49:35 GMT+0800 (China Standard Time)

Thank you @dheerajgattupalli! I don't see any obvious errors there. A few more things that would help: lsblk --fs /dev/nvme0n1 and the contents of /boot/grub/grub.cfg to see if the file system UUIDs in the config match what's actually there.

dheerajgattupalli · Answer 17 · Fri Jul 07 2023 15:52:41 GMT+0800 (China Standard Time)

lsblk --fs /dev/nvme0n1 output:

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 apfs f5e60141-983a-45d1-a1a4-bfde1824a10d
├─nvme0n1p2 apfs f453a203-6f62-4547-9ae8-171b86f27544
├─nvme0n1p3 apfs 62af437f-abd4-4fa2-880f-79334ae699c4
├─nvme0n1p4 vfat FAT32 EFI - UBUNT F73D-093D 404.1M 15% /boot/efi
├─nvme0n1p5 ext4 1.0 ubuntu-root aebcdc29-7122-4f09-aee3-f8edd81e45f3 30G 18% /var/snap/firefox/common/host-hunspell
│ /
└─nvme0n1p6 apfs bc59d466-ddd6-436f-bd81-83c375fefddc

grub.txt
and this is the grub.cfg

Tobias Heider · Answer 18 · Fri Jul 07 2023 16:14:49 GMT+0800 (China Standard Time)

Thanks, this also looks correct. We can see that your root UUID is aebcdc29-7122-4f09-aee3-f8edd81e45f3 which matches the boot menu entry which sets root=UUID=aebcdc29-7122-4f09-aee3-f8edd81e45f3 which again matches what we see in the first-boot log. Your installation looks fine to me.

dheerajgattupalli · Answer 19 · Fri Jul 07 2023 16:30:23 GMT+0800 (China Standard Time)

Thanks for your help, just restarted i didnt get the error this time. sorry, so those logs may not be useful.. first time i applied ubuntu updates before restart so maybe those messed up my installation. is it ok to apply software updates? one of the update was called "ubuntu-base"

Tobias Heider · Answer 20 · Fri Jul 07 2023 16:38:01 GMT+0800 (China Standard Time)

The fact that the bug is not reliably reproducible even on the same hardware is already valuable information, thanks again for your help @dheerajgattupalli! Software updates absolutely should be safe to apply.

Samil Karaduman · Answer 21 · Fri Jul 07 2023 22:39:47 GMT+0800 (China Standard Time)

As for me, what should I go about doing now? Seeing that I can't even boot off of a flash drive theres not much I can do. Has there been any updates pushed out yet? I'm willing to do a fresh install if everything is fixed, unless there is another way.

Tobias Heider · Answer 22 · Fri Jul 07 2023 22:49:09 GMT+0800 (China Standard Time)

@SamilKaraduman No updates yet since we don't know what's happening. We need someone to share a log of the breakage to figure out what's going on. Unfortunately I can't really think of another way other than booting from USB which also seems to be broken.

If you just want it to work I propose the following:

reinstall
DON'T REBOOT
check/share your logs to see what's wrong
fix it by hand (if you don't know how, I can certainly help)
have a working system

Maybe if you are lucky we can even skip some points if it magically works this time.

Samil Karaduman · Answer 23 · Fri Jul 07 2023 23:59:39 GMT+0800 (China Standard Time)

Guess I'll be doing a full reinstallation then, will take about an hour or so. I'll post an update when I'm done.

Samil Karaduman · Answer 24 · Sat Jul 08 2023 02:47:42 GMT+0800 (China Standard Time)

System is up and running. I am currently running Ubuntu while typing this, and this is the output of the command:

`Jul 07 20:42:34 localhost.localdomain systemd[1]: Starting first-boot.service ->
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + set -e
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + trap cleanup EXIT
Jul 07 20:42:34 localhost.localdomain first-boot[584]: + findmnt -n -o UUID /
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + root_uuid_old=87c6b0ce>
Jul 07 20:42:34 localhost.localdomain first-boot[587]: + findmnt -n -o SOURCE /
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + root_dev=/dev/disk/by->
Jul 07 20:42:34 localhost.localdomain first-boot[590]: + findmnt -n -o SOURCE />
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + efi_dev=/dev/nvme0n1p4
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/disk/by-uuid>
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + echo Randomizing root >
Jul 07 20:42:34 localhost.localdomain first-boot[583]: Randomizing root filesys>
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + tune2fs -U random /dev>
Jul 07 20:42:34 localhost.localdomain first-boot[592]: tune2fs 1.47.0 (5-Feb-20>
Jul 07 20:42:34 localhost.localdomain first-boot[599]: + grep ^UUID=
Jul 07 20:42:34 localhost.localdomain first-boot[598]: + blkid -c /dev/null /de>
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + root_uuid=UUID=c32f8a9>
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + udevadm control -S
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + echo Root filesystem: >
Jul 07 20:42:34 localhost.localdomain first-boot[583]: Root filesystem: UUID=c3>
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + echo
Jul 07 20:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/nvme0n1p4 ]
lines 1-23

`

Samil Karaduman · Answer 25 · Sat Jul 08 2023 02:49:32 GMT+0800 (China Standard Time)

As for fixing the system, I would like some help on that. (Please!)

Tobias Heider · Answer 26 · Sat Jul 08 2023 13:46:36 GMT+0800 (China Standard Time)

@SamilKaraduman that log doesn't look complete and we need to find out why, if you look at log_firstboot.log above you can see that there are a few more commands after that. Did it hang up or did you not copy all of it?

As above: what do lsblk --fs /dev/nvme0n1 and /boot/grub/grub.cfg say about the uuid? it should be a new random one now and both outputs should match.

Samil Karaduman · Answer 27 · Sat Jul 08 2023 16:59:15 GMT+0800 (China Standard Time)

If i paste the above command, it only displays lines 1-23 in the terminal. If i resize the window the same output is outputted a couple of times, all saying the same thing. Where is the file even located? I'm currently up at 5am in my timezone trying to solve this issue.

Samil Karaduman · Answer 28 · Sat Jul 08 2023 17:00:47 GMT+0800 (China Standard Time)

Never mind, if i resize the window there seems to be a bit more than I thought.

`Jul 07 14:42:34 localhost.localdomain systemd[1]: Starting first-boot.service ->
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + set -e
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + trap cleanup EXIT
Jul 07 14:42:34 localhost.localdomain first-boot[584]: + findmnt -n -o UUID /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid_old=87c6b0ce>
Jul 07 14:42:34 localhost.localdomain first-boot[587]: + findmnt -n -o SOURCE /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_dev=/dev/disk/by->
Jul 07 14:42:34 localhost.localdomain first-boot[590]: + findmnt -n -o SOURCE />
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + efi_dev=/dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/disk/by-uuid>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Randomizing root >
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Randomizing root filesys>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + tune2fs -U random /dev>
Jul 07 14:42:34 localhost.localdomain first-boot[592]: tune2fs 1.47.0 (5-Feb-20>
Jul 07 14:42:34 localhost.localdomain first-boot[599]: + grep ^UUID=
Jul 07 14:42:34 localhost.localdomain first-boot[598]: + blkid -c /dev/null /de>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid=UUID=c32f8a9>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -S
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Root filesystem: >
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Root filesystem: UUID=c3>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/nvme0n1p4 ]
lines 1-23...skipping...
Jul 07 14:42:34 localhost.localdomain systemd[1]: Starting first-boot.service - Sets up system on first boot...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + set -e
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + trap cleanup EXIT
Jul 07 14:42:34 localhost.localdomain first-boot[584]: + findmnt -n -o UUID /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid_old=87c6b0ce-3bb6-4dc2-9298-3a799bbb5994
Jul 07 14:42:34 localhost.localdomain first-boot[587]: + findmnt -n -o SOURCE /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_dev=/dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799bbb5994
Jul 07 14:42:34 localhost.localdomain first-boot[590]: + findmnt -n -o SOURCE /boot/efi
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + efi_dev=/dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799bbb5994 ]
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Randomizing root filesystem UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Randomizing root filesystem UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + tune2fs -U random /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799b>
Jul 07 14:42:34 localhost.localdomain first-boot[592]: tune2fs 1.47.0 (5-Feb-2023)
Jul 07 14:42:34 localhost.localdomain first-boot[599]: + grep ^UUID=
Jul 07 14:42:34 localhost.localdomain first-boot[598]: + blkid -c /dev/null /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid=UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -S
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Root filesystem: UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Root filesystem: UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/nvme0n1p4 ]
Jul 07 14:42:34 localhost.localdomain first-boot[620]: + grep -q TYPE="vfat"
Jul 07 14:42:34 localhost.localdomain first-boot[619]: + blkid /dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Randomizing EFI system partition UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Randomizing EFI system partition UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + fatlabel -i -r /dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[639]: There are differences between boot sector and its backup.
Jul 07 14:42:34 localhost.localdomain first-boot[639]: This is mostly harmless. Differences: (offset:original/backup)
Jul 07 14:42:34 localhost.localdomain first-boot[639]: 65:01/00
Jul 07 14:42:34 localhost.localdomain first-boot[639]: Not automatically fixing this.
Jul 07 14:42:34 localhost.localdomain first-boot[644]: + blkid -c /dev/null /dev/nvme0n1p4 -o export
Jul 07 14:42:34 localhost.localdomain first-boot[645]: + grep ^UUID=
lines 1-35

Jul 07 14:42:34 localhost.localdomain systemd[1]: Starting first-boot.service - Sets up system on first boot...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + set -e
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + trap cleanup EXIT
Jul 07 14:42:34 localhost.localdomain first-boot[584]: + findmnt -n -o UUID /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid_old=87c6b0ce-3bb6-4dc2-9298-3a799bbb5994
Jul 07 14:42:34 localhost.localdomain first-boot[587]: + findmnt -n -o SOURCE /
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_dev=/dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799bbb59>
Jul 07 14:42:34 localhost.localdomain first-boot[590]: + findmnt -n -o SOURCE /boot/efi
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + efi_dev=/dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3a799bbb5994 ]
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Randomizing root filesystem UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Randomizing root filesystem UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + tune2fs -U random /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298-3>
Jul 07 14:42:34 localhost.localdomain first-boot[592]: tune2fs 1.47.0 (5-Feb-2023)
Jul 07 14:42:34 localhost.localdomain first-boot[599]: + grep ^UUID=
Jul 07 14:42:34 localhost.localdomain first-boot[598]: + blkid -c /dev/null /dev/disk/by-uuid/87c6b0ce-3bb6-4dc2-9298->
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + root_uuid=UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -S
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Root filesystem: UUID=c32f8a9e-9c43-4d9b-9322-20804d799f>
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Root filesystem: UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + [ -e /dev/nvme0n1p4 ]
Jul 07 14:42:34 localhost.localdomain first-boot[620]: + grep -q TYPE="vfat"
Jul 07 14:42:34 localhost.localdomain first-boot[619]: + blkid /dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + echo Randomizing EFI system partition UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: Randomizing EFI system partition UUID...
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + udevadm control -s
Jul 07 14:42:34 localhost.localdomain first-boot[583]: + fatlabel -i -r /dev/nvme0n1p4
Jul 07 14:42:34 localhost.localdomain first-boot[639]: There are differences between boot sector and its backup.
Jul 07 14:42:34 localhost.localdomain first-boot[639]: This is mostly harmless. Differences: (offset:original/backup)
Jul 07 14:42:34 localhost.localdomain first-boot[639]: 65:01/00
Jul 07 14:42:34 localhost.localdomain first-boot[639]: Not automatically fixing this.
lines 1-33

`

Tobias Heider · Answer 29 · Sat Jul 08 2023 17:10:20 GMT+0800 (China Standard Time)

The easiest way to make it readable would be piping it to a file and uploading that somewhere, so sudo journalctl -u first-boot > first-boot.log. I still don't see the service finishing in the log snippet you provided.

What do lsblk --fs /dev/nvme0n1 and cat /boot/grub/grub.cfg say?

Samil Karaduman · Answer 30 · Sat Jul 08 2023 17:20:29 GMT+0800 (China Standard Time)

first-boot.log

My bad, here it is.

As for the other two commands, the lsblk command linked above gives me this output:

`NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1

├─nvme0n1p1
│ apfs e9f44fd6-b2f5-40dd-b292-01dbbe9cc699
├─nvme0n1p2
│ apfs d29b84d7-7719-4303-ad69-5ff2e355f406
├─nvme0n1p3
│ apfs 10f0b933-78b5-4ffa-a0b7-a49e1ce92859
├─nvme0n1p4
│ vfat FAT32 EFI - UBUNT
│ C9AC-CB8E 404M 15% /boot/efi
├─nvme0n1p5
│ ext4 1.0 ubuntu-root
│ c32f8a9e-9c43-4d9b-9322-20804d799f03 87.5G 8% /var/snap/firefox/common/host-hunspell
│ /
└─nvme0n1p6
apfs 6467b3b6-c797-46c5-9c9b-cb109c475262
`

And the cat command will give this output:

`#

DO NOT EDIT THIS FILE

It is automatically generated by grub-mkconfig using templates

from /etc/grub.d and settings from /etc/default/grub

BEGIN /etc/grub.d/00_header

if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${initrdfail}" = 2 ]; then
set initrdfail=
elif [ "${initrdfail}" = 1 ]; then
set next_entry="${prev_entry}"
set prev_entry=
save_env prev_entry
if [ "${next_entry}" ]; then
set initrdfail=2
fi
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function initrdfail {
if [ -n "${have_grubenv}" ]; then if [ -n "${partuuid}" ]; then
if [ -z "${initrdfail}" ]; then
set initrdfail=1
if [ -n "${boot_once}" ]; then
set prev_entry="${default}"
save_env prev_entry
fi
fi
save_env initrdfail
fi; fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root c32f8a9e-9c43-4d9b-9322-20804d799f03
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=C
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0

Fallback hidden-timeout code in case the timeout_style feature is

unavailable.

elif sleep --interruptible 0 ; then
set timeout=0
fi
fi

END /etc/grub.d/00_header

BEGIN /etc/grub.d/05_debian_theme

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

END /etc/grub.d/05_debian_theme

BEGIN /etc/grub.d/10_linux

function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if [ ${grub_platform} != pc ]; then
set linux_gfx_mode=keep
elif hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c32f8a9e-9c43-4d9b-9322-20804d799f03' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root c32f8a9e-9c43-4d9b-9322-20804d799f03
linux /boot/vmlinuz-6.3.0-7-asahi root=UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03 ro quiet splash $vt_handoff
initrd /boot/initrd.img-6.3.0-7-asahi
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-c32f8a9e-9c43-4d9b-9322-20804d799f03' {
menuentry 'Ubuntu, with Linux 6.3.0-7-asahi' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.3.0-7-asahi-advanced-c32f8a9e-9c43-4d9b-9322-20804d799f03' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root c32f8a9e-9c43-4d9b-9322-20804d799f03
echo 'Loading Linux 6.3.0-7-asahi ...'
linux /boot/vmlinuz-6.3.0-7-asahi root=UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03 ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.3.0-7-asahi
}
menuentry 'Ubuntu, with Linux 6.3.0-7-asahi (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.3.0-7-asahi-recovery-c32f8a9e-9c43-4d9b-9322-20804d799f03' {
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root c32f8a9e-9c43-4d9b-9322-20804d799f03
echo 'Loading Linux 6.3.0-7-asahi ...'
linux /boot/vmlinuz-6.3.0-7-asahi root=UUID=c32f8a9e-9c43-4d9b-9322-20804d799f03 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.3.0-7-asahi
}
}

END /etc/grub.d/10_linux

BEGIN /etc/grub.d/10_linux_zfs

END /etc/grub.d/10_linux_zfs

BEGIN /etc/grub.d/20_linux_xen

END /etc/grub.d/20_linux_xen

BEGIN /etc/grub.d/30_os-prober

END /etc/grub.d/30_os-prober

BEGIN /etc/grub.d/35_fwupd

END /etc/grub.d/35_fwupd

BEGIN /etc/grub.d/40_custom

This file provides an easy way to add custom menu entries. Simply type the

menu entries you want to add after this comment. Be careful not to change

the 'exec tail' line above.

END /etc/grub.d/40_custom

BEGIN /etc/grub.d/41_custom

if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi

END /etc/grub.d/41_custom

`

Tobias Heider · Answer 31 · Sat Jul 08 2023 17:23:29 GMT+0800 (China Standard Time)

Thank you, so the job did finish and it looks like the uuids are all correct this time. c32f8a9e-9c43-4d9b-9322-20804d799f03 is the new random uuid and the log and grub config suggest it is in sync.

It will probably just work after reboot this time.

EDIT: But I would suggest trying it before setting up all your configs

Samil Karaduman · Answer 32 · Sat Jul 08 2023 17:30:50 GMT+0800 (China Standard Time)

EDIT: But I would suggest trying it before setting up all your configs

Try to reboot first?

Samil Karaduman · Answer 33 · Sat Jul 08 2023 17:41:48 GMT+0800 (China Standard Time)

Finally, it works! Thank you so very much for all your time! After all this, do you think it is safe to update in the future? Definitely don't want something like this to happen again!

Tobias Heider · Answer 34 · Sat Jul 08 2023 17:49:35 GMT+0800 (China Standard Time)

yes it should be safe to update. I take good care to test all updates but of course sometimes bugs happen that are related to a specific hardware/software combination. If that happens I am of course reading the reports here and try to get them fixed.

tyleraiv · Answer 35 · Wed Jul 19 2023 09:15:40 GMT+0800 (China Standard Time)

Apparently I'm experiencing the same issue. I've attempted approx. 5 installations. Installing the Arch Linux presents no issues. I've attached the following: lsblk, grub.cfg as grub.txt and first-boot.log. I've also included a pict of the boot screen at the failure state. It appears that the UUID in the failure screen is different from that of the grub file. This unit is a 2020 MacBook Air M1/8GB/256GB system. The attempts to install were all made yesterday July 17 and today July 18, 2023. Thank you.

lsblk.txt
grub.txt
first-boot.log

Mark Esler · Answer 36 · Wed Jul 19 2023 22:51:28 GMT+0800 (China Standard Time)

Thanks for the thorough report @tyleraiv

The UUID on your boot screen is the default UUID used during installation. During first-boot, the UUID should have been changed (and appears so in the log). @tobhe can you take a look?

Mark Esler · Answer 37 · Wed Jul 19 2023 22:55:51 GMT+0800 (China Standard Time)

closing for #49