[Bug 1012025] Re: update-grub not reading UUID's properly
Phillip Susi
psusi at ubuntu.com
Wed Jun 13 16:06:43 UTC 2012
I believe it gets it from /etc/fstab, which is why you need to update
the /etc/fstab on sdc7 to list the new uuid you gave to sdc7 instead of
the old uuid of sdc1.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1012025
Title:
update-grub not reading UUID's properly
Status in “grub2” package in Ubuntu:
Incomplete
Bug description:
Bug report
update-grub not reading UUID's properly
Grub2
xubuntu 12.04
garry at welland-precise-xfce:~$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
grub2 1.99-21ubuntu3.1
What happened?
1) I did a partimage backup of xbunutu 12.04 off sdc1, then restored that backup to sdc7.
2) I changed sdc7's UUID from ~~~~898 to ~~~~000
3) Back in sdc1, and in another OS on sda7, I used both yannubutu-boot-repair and (update-grub + grub-install).
4) I couldn't boot my new sdc7. (actually booted, but to repair menu, which I couldn't understand.)
5) On both other OS's grub.cfg kept reading as follows (note last 3 chars of UUID) :-
search --no-floppy --fs-uuid --set=root 9d6412d7-0277-4b1e-b56e-76eb9fb7e000
linux /boot/vmlinuz-3.2.0-23-generic root=UUID=9d6412d7-0277-4b1e-b56e-76eb9fb7e898 ro quiet splash $vt_handoff
5) When I edited the starting grub menu to make linux~~~~898 ->
linux~~~000, and update-grub + grub-install, sdc7 booted ok. From
there I update-grub + grub-install again, all is OK now.
I struggle with bash, but I suspect /etc/grub.d/10_linux line 124
linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}
is the culprit.
garrytreth at gmail.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1012025/+subscriptions
More information about the foundations-bugs
mailing list