I can see this problem, or something similar is present in natty grub
1.99~rc1-4ubuntu1
update-grub put:
linux /vmlinuz-2.6.38-7-generic-pae root=/dev/md123 ro ...
as the entry in grub.cfg
It should never do this, because /dev/md123 is correct only at that
time, and may very well be incorrect on the next boot. My fstab has:
LABEL=natty3_md / ext3 noatime,errors=remount-ro 0 1
LABEL=boot1t /boot auto noatime 0 0
fyi, if I change fstab LABEL=natty3_md to UUID=...., and re-run update-
grub, the problem is still there.
In my example, my boot partition was non-raid, regular ext3 partition
and the other partitions, except swap, are mdraid (raid1). In my
mdadm.conf if have:
ARRAY /dev/md/amy:natty3 metadata=1.2 UUID=b1211dcb-67a1-4032-364a-
12057c183e9a name=amy:natty3
To work-around this problem, I added the following line to
/etc/default/grub:
GRUB_DEVICE="LABEL=natty3_md"
which created the correct root=LABEL=natty3_md in the grub.cfg
This worked for me, but I don't think it is a good solution for the
average user. Really, update-grub should use root=LABEL= or root=UUID=
in grub.cfg whenever possible, rather than /dev/md... or /dev/sd...
** Summary changed:
- hard disk device name ordering non-deterministic
+ update-grub sets root= non-deterministic device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738297
Title:
update-grub sets root= non-deterministic device
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
