Hardy Install constructs GRUB config incorrectly when using PCI RAID card with IDE drives attached to it
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
I have a PC with an Asrock motherboard with one SATA drive connected to onboard SATA port and three IDE drives on a PCI RAID card's IDE ports. I have booted with 8.04.1 i386 live CD and it put the SATA drive behind the three IDE drives in the /dev/sd* order (SATA drive became sdd). All the drives and partitions on them could be mounted properly.
I have installed Ubuntu Hardy using the live CD onto the SATA drive. The installation went without problem, but at the first boot the GRUB menu appeared and if any option was selected, the error message "Error 22: No such partition" appeared.
After some investigation I found out that during boot time, when GRUB gets loaded it doesn't see the IDE drives connected to the PCI RAID card, so for GRUB the system (and only) drive was hd0 (sda), but the installation configured the menu.lst and devices.map in a way that the SATA drive was hd3 (sdd).
Actually I cannot even select the IDE drives in BIOS if I want to specify the boot order, but they get shown in the list of connected HDs.
After editing the menu.lst to refer to hd0 instead of hd3 the system booted properly. This is my first PCI RAID card, so I'm not sure it is normal that the drives connected to it cannot be seen during boot time. I still don't understand why Ubuntu identifies the IDE drives first as sda, sdb and sdc, and only after them comes the SATA drive connected directly to the motherboard as sdd.
Let me know if any additional information is needed.
| Tor (panda726) wrote | #1 |
| Phillip Susi (psusi) wrote | #2 |
| Changed in ubiquity (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in ubiquity (Ubuntu): | |
| status: | Incomplete → Expired |
I believe this is probably related to Bug #46520 in which IDE disks and SATA disks are handled in differing orders between OS and BIOS/grub. This bug is easy enough to work around in exactly the way you did in all cases, but it really would be good to get it fixed, as this seems to affect everyone who has both SATA and IDE disks, regardless of configuration. Hopefully we can get this whole situation well enough documented that the devs can get it properly fixed.
Tor