Patrik Jansson wrote: > Christian Affolter wrote: > > Can you provide the SCSI/RAID related dmesg output from the live-CD? > > Do you have a SCSI-CD Rom or an IDE/(S)ATA one? > Ofcourse: > > megasas: 00.00.02.04 Fri Feb 03 14:31:44 PST 2006 > megasas: 0x1028:0x0015:0x1028:0x1f03: bus 2:slot 14:func 0 > ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 78 (level, low) -> IRQ 19 > scsi2 : LSI Logic SAS based MegaRAID driver > Vendor: FUJITSU Model: MAX3147RC Rev: D206 > Type: Direct-Access ANSI SCSI revision: 03 > Vendor: FUJITSU Model: MAX3147RC Rev: D206 > Type: Direct-Access ANSI SCSI revision: 03 > Vendor: DP Model: BACKPLANE Rev: 1.00 > Type: Enclosure ANSI SCSI revision: 05 > Vendor: DELL Model: PERC 5/i Rev: 1.00 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sdb: 285474816 512-byte hdwr sectors (146163 MB) > sdb: test WP failed, assume Write Enabled > sdb: asking for cache data failed > sdb: assuming drive cache: write through > SCSI device sdb: 285474816 512-byte hdwr sectors (146163 MB) > sdb: test WP failed, assume Write Enabled > sdb: asking for cache data failed > sdb: assuming drive cache: write through > sdb: sdb1 sdb2 sdb3 > sd 2:2:0:0: Attached scsi disk sdb > > > Have you ever tried to use /dev/sda in your grub config and fstab (as > > your kernel recognizes an sda SCSI disk) ? > > gregorcy wrote: > > I had the same issue with the PERC 5i card and gentoo. What happened > > was the LiveCD saw the drive as /dev/sdb but when I installed and then > > rebooted it came up as /dev/sda. I just pointed my grub.conf at the > > /dev/sda and it booted correctly. > > That has already been tried but thanks anyway. As I said in the first > mail, at the point where the root device can't be mounted I may open a > simple shell. And with that I can see /dev/sda and /dev/sdb but no > numbers after (for partitions). > I remember having problems with Dell RAID controllers which were related to the kernel-version. The driver was offering both harddisks in the raid as devices, and offering the RAID-device as the same device. This confused the heck out of us at first as well....
Upgrading the kernel to >2.6.16 pulled in a newer driver and this solved our problem. Grtz Ramon -- [email protected] mailing list
