Bug#462701: Seeing this issue or a similar one on md partitions
Loïc Minier
lool at dooz.org
Mon Feb 11 09:36:48 UTC 2008
Hi,
I had an unbootable system as a result of the "savedefault" command
too, but I can't tell whether it's the exact same bug that the other
submitters reported. In my case I have:
/dev/md0 => Debian's /boot
/dev/md1 => Ubuntu's /boot
/dev/md2 => LVM PV
debian-root LV => Debian /
ubuntu-root LV => Ubuntu /
...
With md0, 1 and 2 being RAID 1 made of sda and sdb 1 2 and 3
(respectively).
I am chainloading the md1's grub from md0's grub and md0's parts are
flagged bootable; sda/sdb have a MBR from the mbr package. I think I
grub-installed from Debian on /dev/sda1 and sdb1 then md0 and from
Ubuntu on sda2 and sdb2 then md1.
After a while, this broke without reason; presumably after a grub
update.
I grub-installed on sda* again instead of md, and this seemed to work
again, but I decided to not use "default saved" and "savedefault" until
I read about this bug.
Let me know if you prefer a separate report.
Cheers,
--
Loïc Minier
More information about the Pkg-grub-devel
mailing list