[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#388501: Installation Report

On Wednesday 20 September 2006 21:18, Michael S. Peek wrote:
> Comments/Problems:
> Installation works fine, but unable to mount the root filesystem on
> reboot.  Checking /proc/cmdline shows "root=/dev/sda1 ro", which is
> correct, but no /dev/sda1 exists (/dev/sda exists though).

This may be due to a mismatch between the kernel version used by the
installer (2.6.17) and the one installed for the new system (2.6.16).

Please use the rescue mode of the installer to upgrade the kernel to
2.6.17 and see if that solves your problem.


Aha! I figured it out! --I don't know how to fix it, but I figured it out.

The hardware:
- SuperMicro X6DHE-XG2 (Intel E7520 chipset, ICHR5 SATA controller)
- w/ 3ware 9550sx card installed

I neglected to mention the 3ware card because I didn't think that it had a bearing on anything, but it turns out that it does.

When the installer discovers the hardware for drives, it discovers them in this order:
1) Motherboard (ata_piix) --> sda
2) 3ware (3w_9xxx) [array #1] --> sdb
3) 3ware (3w_9xxx) [array #2] --> sdc

During installation I partition and install to sda. (sdb+sdc have no partitioning information and no filesystem.) The kernel is installed with root=/dev/sda1 as part of the command line to the kernel, as it should according to the list above.

Then, after the base installation finishes and I reboot, the hardware is discovered in a different order:

1) 3w_9xxx [#1] --> sda
2) 3w_9xxx [#2] --> sdb
3) ata_piix --> sdc

The kernel is looking for root to be on /dev/sda1, but since the drivers are loaded in a different order, root is actually on /dev/sdc.

In order to fix, I must edit the kernel command line listed in /boot/grub/menu.lst and change "root=/dev/sda1" to "root=/dev/sdc1" before reinstalling the 3ware card.

Did I do something wrong during the installation?
Is there a better way to do this?

Michael Peek

Reply to: