Arch Linux

bgmeulem

Member

Registered: 2024-05-27

Posts: 8

GRUB "unable to determine parition UUID of boot device" but boots fine

I configured my grub to autostart the first boot entry. In /etc/default/grub:

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_TIMEOUT_STYLE=hidden

and regenerate with

grub-mkconfig -o /boot/grub/grub.cfg

This works fine, it boots into my first entry successfully. However, during boot, I see an error/warning:

Unable to determine partition UUID of boot device

Which confuses me.

My "/boot" is my first partition, VFAT, and has a UUID. I see the same error/warning when "GRUB_TIMEOUT_STYLE=countdown", but not when "GRUB_TIMEOUT_STYLE=menu".

Why does this happen? Does this need to be fixed, and if so, how?

Many thanks in advance for any pointers.

$ lsblk -fs
NAME      FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1p1 vfat   FAT32 boot  54E0-DA51                             597.3M    42% /boot
└─nvme0n1                                                                        
nvme0n1p2 swap   1     swap  235b5fc9-9cd2-4c0b-a172-531d532d4b0c                [SWAP]
└─nvme0n1                                                                        
nvme0n1p3 btrfs        root  63f8e3c9-ec86-41bf-a5b0-4f2772e54e64  685.9G    26% /
└─nvme0n1

/etc/mkinitcpio.conf

HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems resume fsck)

unixman

Member

Registered: 2015-03-12

Posts: 181

Re: GRUB "unable to determine parition UUID of boot device" but boots fine

when grub say "UUID of boot device" it intents "UUID of root device"
it say it because of somethings eg no UUID= specifier for root device.
root device specified by other means.

Yeah all above is my speculations/2cents.

But specifing root via UUID is more reliable therefore recommended by gurus.