Description of problem: installation of rhel5 does not work because disks are not detected - scsi raid card Adaptec 2010S (supermicro server) 06:01.0 RAID bus controller: Adaptec (formerly DPT) SmartRAID V Controller (rev 01) - works in RHEL3 (i2o driver) Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.start installation 2.create disk layout 3.disks are not detected Actual results: installation fail - disks are not detected Expected results: installation succed - disks are detected Additional info: dmesg from rhel3 Loading Adaptec I2O RAID: Version 2.4 Build 5 Detecting Adaptec I2O RAID controllers... Adaptec I2O RAID controller 0 irq=72 BAR0 f883e000 - size= 100000 BAR1 f893f000 - size= 1000000 dpti: If you have a lot of devices this could take a few minutes. dpti0: Reading the hardware resource table. TID 008 Vendor: ADAPTEC Device: AIC-7902 Rev: 00000001 TID 009 Vendor: ADAPTEC Device: AIC-7902 Rev: 00000001 TID 519 Vendor: SUPER G Device: GEM318 Rev: 0 0 TID 526 Vendor: ADAPTEC R Device: RAID-1 Rev: 3B0AD TID 527 Vendor: ADAPTEC R Device: RAID-5 Rev: 3B0AD scsi0 : Vendor: Adaptec Model: 2010S FW:3B0A Vendor: ADAPTEC Model: RAID-1 Rev: 3B0A Type: Direct-Access ANSI SCSI revision: 02 Vendor: ADAPTEC Model: RAID-5 Rev: 3B0A Type: Direct-Access ANSI SCSI revision: 02 Vendor: SUPER Model: GEM318 Rev: 0 Type: Processor ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0 installation of RHEL4 does not detect disks BUT offer to load i2o modules then disks are detected installation of RHEL5 load i2o_core but nothing else modprobe i2o_block etc. does not work (alt-f2 in install process)
workaround 1. boot with "linux noprobe text" 2. add driver "i2o block" 3. after that disks are detected (complete installation not tested now)
requested by Jams Antill
We believe this issue is fixed in 5.1. Please test and verify. If not, please reopen the bug with your support representative who will raise it through the appropriate channels. Thanks.
Confirmed that workaround suggested does give read/write access from the installer console. Have not proceeded with destructive install as of yet so isn't fully tested. Expect to complete this this weekend, so this ticket can be closed September 5 in absence of negative feedback to the contrary.
I've just completed destructive install of server and can confirm that the workaround suggested in comment #1 works flawlessly. There was a minor issue with the installer itself in that it doesn't complete final install tasks after reboot until system is booted into runlevel 5, and performing a text-mode install defaults the runlevel to 3. Might want to point this out as an addendum to process above as a newbie sysadmin wouldn't necessarily recognize that the installer wasn't finished its tasks. Thanks for your assistance with this process - much obliged