Hi Folks,
I'm about to give up on this Adaptec aic-94xx RAID controller, but I continue to be puzzled by the fact that when I run the installer (anaconda), it recognizes the RAID devices, but once CentOS is installed, all it can see are the individual drives.
General explanation (details below signature):
For instance, when doing the install, I get asked if I want to use /dev/sda (a 590+ GB RAID0 array) and /dev/sdb (a 490+GB RAID1 array) as part of the install. There's also 4 other individual drives in the server. They all show as expected when setting up the install partitions and mount points. But, whether or not I choose to include the RAID arrays as mounted elements of the install or not, once CentOS gets to booting, all it will recognize are the individual drives that comprise the RAID arrays (and the drive designations are completely different--sda now points to the first of the 4 separate drives (that's where I mapped the / filesystem) and the RAID0 array (/dev/sda during install) is now two 300GB drives designated as /dev/sde and /dev/sdh.
Now, if this were just a case of the RAID controller's not being supported, I would just deal with it (although a couple of other threads I found on the AIC 94xx driver or 9410 controller suggested support would be added at a 2.something.19 kernel rev--I can't find that thread now, of course--drat it!) But if the 2.6.18 kernel of this CentOS install just doesn't support it, why is anaconda able to see the RAID devices I've defined via the RAID BIOS setup, but the installed OS insists they're separate drives? The installer loads the driver module aic-94xx module; but that module also seems to load fine during boot-up. Clearly something is different about the installed boot-up vs. the anaconda boot-up.
If there were a way to get the installed CentOS to behave like the installer does (with regard to seeing the defined RAID devices), that'd be useful.
Install and hardware details are below.
Any insights appreciated.
Thanks,
John
Distro:
CentOS 5.5
uname -r:
2.6.18-194.el5
lspci output shows the RAID device as expected:
02:06.0 RAID bus controller: Adaptec AIC-9410W SAS (Razor ASIC RAID) (rev 09)
dmesg seems to show the appropriate kernel module loading correctly. But the dmesg output then lists device identifiers being associated with the individual drives attached to the controller, rather than the RAID devices. The 2 300GB SAS drives are defined as a RAID0 array; 2 500GB SATA drives, RAID1--but the individual drives show up instead: sde [300GB SAS], sdf [500GB SATA], sdg [500GB SATA], sdh [300GB SAS]
(Recall that in the installation phase, I'm seeing the RAID devices as /dev/sda and /dev/sdb.)
Code:
...
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.2-2 loaded
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 18 (level, low) -> IRQ 169
aic94xx: found Adaptec AIC-9410W SAS/SATA Host Adapter, device 0000:02:06.0
scsi4 : aic94xx
aic94xx: using sequencer V35
aic94xx: device 0000:02:06.0: SAS addr 500e0810000392d4, PCBA SN , 8 phys, 8 enabled phys, flash present, BIOS build 1608
Vendor: SEAGATE Model: ST3300656SS Rev: 0006
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sde: 585937500 512-byte hdwr sectors (300000 MB)
sde: Write Protect is off
sde: Mode Sense: b3 00 10 08
SCSI device sde: drive cache: write back w/ FUA
SCSI device sde: 585937500 512-byte hdwr sectors (300000 MB)
sde: Write Protect is off
sde: Mode Sense: b3 00 10 08
SCSI device sde: drive cache: write back w/ FUA
sde: unknown partition table
sd 4:0:0:0: Attached scsi disk sde
ata5.00: native sectors (1) is smaller than sectors (976773168)
ata5.00: ATA-8: ST3500418AS, CC38, max UDMA/133
ata5.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
Vendor: ATA Model: ST3500418AS Rev: CC38
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdf: 976773168 512-byte hdwr sectors (500108 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: drive cache: write through
SCSI device sdf: 976773168 512-byte hdwr sectors (500108 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: drive cache: write through
sdf: sdf1
sd 4:0:1:0: Attached scsi disk sdf
ata6.00: native sectors (1) is smaller than sectors (976773168)
ata6.00: ATA-8: ST3500418AS, CC38, max UDMA/133
ata6.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata6.00: configured for UDMA/133
Vendor: ATA Model: ST3500418AS Rev: CC38
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdg: 976773168 512-byte hdwr sectors (500108 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: drive cache: write through
SCSI device sdg: 976773168 512-byte hdwr sectors (500108 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: drive cache: write through
sdg: sdg1
sd 4:0:2:0: Attached scsi disk sdg
Vendor: SEAGATE Model: ST3300656SS Rev: 0006
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdh: 585937500 512-byte hdwr sectors (300000 MB)
sdh: Write Protect is off
sdh: Mode Sense: b3 00 10 08
SCSI device sdh: drive cache: write back w/ FUA
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com
SCSI device sdh: 585937500 512-byte hdwr sectors (300000 MB)
sdh: Write Protect is off
sdh: Mode Sense: b3 00 10 08
SCSI device sdh: drive cache: write back w/ FUA
sdh:
sd 4:0:3:0: Attached scsi disk sdh
cat /boot/config-2.6.18-194.el5 | grep -i aic94 shows:
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
Let me know if there's other info I should provide.
