grub fails to boot OS images on second hard drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Dell Precision T3400
SATA Slot0: (sda) Xubuntu 12.04 + Win7 (new hard drive)
SATA Slot1: DVD-RW drive
SATA Slot2: (sdb) Kubuntu 10.04 + Win Vista (old hard drive moved from SATA slot0)
I recently installed Xubuntu 12.04 on my machine. I wanted to preserve the Win Vista and Kubuntu 10.04 installs that already existed on the machine and add a Win7 install.
Here are the steps I took:
1) remove original hard drive from SATA slot0
2) install new hard drive on SATA slot0
3) install win7 on first partition of new HD
4) install the old HD in SATA slot2 (SATA slot1 has DVD)
5) install Xubuntu 12.04 on second partition of new HD
During Xubuntu install, all of the OS's were detected (Xubuntu 12.04 + Win7 on SATA slot0, and Kubuntu 10.04 + Vista on SATA slot2).
When I boot, there are grub menu entries for all four OS's, but only Win7 and Xubuntu (both on the new HD in SATA slot0 - sda) are bootable.
If I select either OS (Vista or Kubuntu 10.04) on the original HD (now in SATA slot2 - sdb) I get the message "you need to load the kernel first" and I eventually get returned to the grub menu.
On advice in this thread (http://
Boot info output from boot-repair is here (http://
After running boot-repair, the error I now get when trying to boot from either OS on sdb is "no such partition". **Intersetingly**, If I hit 'c' on the grub menu and type in the 'ls (hd1,5)/' command, I get 'no such partition'. I then type 'exit' to get back to the menu and hit 'c' again and repeat 'ls (hd1,5)/' and it works. There is a vmlinuz and an initrd.img. If I continue with the commands below, the screen eventually goes blank and seems to hang.
linux (hd1,5)/vmlinuz root=/dev/sdb5 ro
initrd (hd1,5)/initrd.img
boot
Note that if I boot into the Xubuntu 12.04 OS I can mount and inspect all of the other OS partitions on sda and sdb.
It sounds like the drive may be dieing, or at least there is some problem communicating with it. Please open the disk utility and check the SMART status of the drive. You may also want to run the long self test. If that all checks out, then try to repeat the ls (hd1,5) command and see if it consistently fails the first time, then starts working.