[Karmic Alpha 5] update-grub gets confused when a second hard drive is plug before running it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Rolf Leggewie |
Bug Description
Binary package hint: grub2
Karmic Alpha 5 live CD install, with only one HD (WD 640Go, SATA) connected on motherboard SATA1 port, Slave. The install doesn't pick up other OSes (see Bug #425379) though.
After install, I plug a second HD (Samsung 1To, SATA) on motherboard SATA0 port, Master. The HD with Karmic moves from /dev/sda to /dev/sdb, the Samsung becomes /dev/sda.
Running update-grub now picks up the other OSes, but throws these errors:
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-
> Found initrd image: /boot/initrd.
> grub-probe: error: Cannot find a GRUB drive for /dev/sdb5. Check your device.map.
>
> grub-probe: error: Cannot find a GRUB drive for /dev/sdb5. Check your device.map.
>
> Found memtest86+ image: /boot/memtest86
> Found Windows Vista (loader) on /dev/sda2
> Found Ubuntu 9.04 (9.04) on /dev/sdb2
> grub-probe: error: Cannot find a GRUB drive for /dev/sdb2. Check your device.map.
>
> Found Microsoft Windows XP Professional on /dev/sdb3
> grub-probe: error: Cannot find a GRUB drive for /dev/sdb3. Check your device.map.
>
> Found Ubuntu 8.10 (8.10) on /dev/sdb6
/boot/grub/
(hd0) /dev/sda
grub.cfg after running update-grub is attached to the bug report, the original configuration at install can be found on Bug #425379
Problem: only Karmic on /dev/sdb5 (WD) and Windows 7 Beta (reported as Windows Vista) on /dev/sda2 (Samsung) can boot. For booting Jaunty, grub2 reports this error:
Error - you need to load the kernel first.
Booting XP doesn't work either.
ubuntu-bug grub crashes repetedly, even after a reboot (doesn't crash against other programs), so I've added the Dependencies from the other bug, no updates in between.