Hello, I wasn't sure where to post this issue so I figured I could do it here. It's both a GRUB and BURG issue, both work the same way.
Anyways, I have GRUB version 1.98-1ubuntu13. I just did some modifications to my partitions using GParted. Everything went fine and my other OSses were detected fine by the OS-prober script. I had a problem with my Archlinux partition though. The UUID is detected fine on the "--fs-uuid --set" line from /boot/burg/burg.cfg, since it matches the device UUID label on /dev/disk/by-uuid/ and the GParted right-click "information" option. However, the kernel line's UUID (linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet") doesn't match that UUID. I honestly don't know where that UUID came from. I've tried uncommenting the "GRUB_DISABLE_LINUX_UUID=true" line on /etc/defaults/burg so BURG could use a device label instead of the UUID, but after running update-burg, it still uses the UUID for the kernel line. I know I could just edit the burg.cfg file to use a device label instead of the UUID, or set the right UUID on the kernel line, but I want to do it the right way. Is there any way to make update-burg or burg-mkconfig commands use the right UUID? Oh, I've tried the same on GRUB, same results.
menuentry "Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gn$
search --no-floppy --fs-uuid --set 7d3f6e9b-90cf-4f1d-9290-dc4fba7ee1dc
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet