[Bug 1012025] Re: update-grub not reading UUID's properly

[Garry Trethewey]

I think you could be right. For no good reason I'd commented out the line
#UUID=9d6412d7-0277-4b1e-b56e-76eb9fb7e898  /  ext3  errors=remount-ro 0  1
on the source partition, so the new one was the same.

Nothing else was effected, the old one still booted ok, so I didn't
notice.

The interesting thing is that it seems grub2 didn't find that line
(unless it did a grep /), so I spose it then just kept the old "linux
/boot/vml..."  line.

I don't spose we can really call this a bug then - software writers
can't be expected to cope with every unusual dumb thing that people
might do.

Thanks for your help.
Garry

-- 
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