I'm using Debian stretch (9.0), the current stable. My arch is AMD64. My root and boot partitions are LVM volume groups on top of an MD RAID 1 device.
According to my understanding of the documentation, uncommenting
GRUB_DISABLE_LINUX_UUID=true
in /etc/default/grub
should stop GRUB2 from using UUIDs in /boot/grub/grub.cfg
. However, it continues to use UUIDs even after I have made that change.
I'm not sure if this is somehow user error on my part, but the instructions seem simple enough.
A couple of additional comments.
- There is also a file
/usr/share/grub/default/grub
, which has identical contents (same md5sum) to/etc/default/grub
. I'm not sure what the point of that file is. - I would expect
/usr/sbin/grub-mkconfig
to include a check forGRUB_DISABLE_LINUX_UUID
, but I don't see one, though that script does includeGRUB_DISABLE_LINUX_UUID
. Can someone explain to me where this script is checkingGRUB_DISABLE_LINUX_UUID
?
I can post more details if it would help, of course.
Background: I was motivated to change this because the UUID of my root VG changed, and my machine refused to boot, saying that the UUID didn't exist. Which was correct. It didn't any longer. See Unable to determine sync status errror when trying split LVM2 RAID 1 mirror for how that happened.
Debian bug report: grub-common: Setting GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub does not work as expected.