HP Smart Array 6400 and Sure Store 40 Dat Drive on DL380 G2

luciogodoy · 05-05-2008, 04:57 AM

Hi All;

I have a DL380 G2, running box standard Fedora Core 8, Kernel 2.6.23.1-42.fc8 and i have installed a HP Smart Array 6400 - 2 ports with 128Mb of memory with the following setup:

Disks 1 and 2 = RAID 1 for Linux OS
Disks 3/4/5/6 = RAID 5 for data storage

All works well, the system boots and does what is suppost to do, my problem is with an external HP Sure Store 40 Dat Drive, connected on port 1 ID 4, which is detected by the 6400 board on boot time, but it is not available on Fedora at all!

#dmesg | grep scsi
scsi0 : pata_serverworks
scsi1 : pata_serverworks
scsi 0:0:0:0: CD-ROM COMPAQ CD-ROM SN-124Q QA17 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray
sr 0:0:0:0: Attached scsi CD-ROM sr0
sr 0:0:0:0: Attached scsi generic sg0 type 5

# cat /proc/version
Linux version 2.6.23.1-42.fc8 (kojibuilder@xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Tue Oct 30 13:55:12 EDT 2007

#ls /lib/modules/2.6.23.1-42.fc8/kernel/drivers/scsi/
3w-9xxx.ko
3w-xxxx.ko
a100u2w.ko
aacraid
advansys.ko
aha152x.ko
aha1542.ko
aic7xxx
aic7xxx_old.ko
aic94xx
arcmsr
atp870u.ko
BusLogic.ko
ch.ko
dc395x.ko
fdomain.ko
gdth.ko
hptiop.ko
imm.ko
initio.ko
ips.ko
iscsi_tcp.ko
libiscsi.ko
libsas
libsrp.ko
lpfc
megaraid
megaraid.ko
osst.ko
pcmcia
ppa.ko
qla1280.ko
qla2xxx
qla4xxx
qlogicfas408.ko
raid_class.ko
scsi_mod.ko
scsi_tgt.ko
scsi_transport_fc.ko
scsi_transport_iscsi.ko
scsi_transport_sas.ko
scsi_transport_spi.ko
scsi_wait_scan.ko
sd_mod.ko
sg.ko
sr_mod.ko
stex.ko
st.ko
sym53c8xx_2
tmscsim.ko

Can any of you share some light please?

Many thanks

Lucio Godoy

farslayer · 05-05-2008, 11:05 AM

Doesn't that controller use the cciss module as the driver ? This module was loaded automatically on my HP server when I installed Debian 4.0

Code:

mail:~# lsmod | grep scsi
scsi_mod              124168  2 sg,cciss


mail:~# modinfo cciss
filename:       /lib/modules/2.6.18-6-686/kernel/drivers/block/cciss.ko
author:         Hewlett-Packard Company
description:    Driver for HP Controller SA5xxx SA6xxx version 3.6.10
license:        GPL
vermagic:       2.6.18-6-686 SMP mod_unload 686 REGPARM gcc-4.1
depends:        scsi_mod



mail:~# cat /var/log/dmesg | grep cciss

Kernel command line: root=/dev/cciss/c0d0p2 ro
cciss0: <0x3230> at PCI 0000:06:00.0 IRQ 114 using DAC
 cciss/c0d0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 >
Adding 2931852k swap on /dev/cciss/c0d0p3.  Priority:-1 extents:1 across:2931852k
EXT3 FS on cciss/c0d0p2, internal journal
EXT3 FS on cciss/c0d0p1, internal journal
EXT3 FS on cciss/c0d0p5, internal journal
EXT3 FS on cciss/c0d0p9, internal journal
EXT3 FS on cciss/c0d0p6, internal journal
EXT3 FS on cciss/c0d0p7, internal journal
EXT3 FS on cciss/c0d0p8, internal journal

cciss_vol_status can be used to check on the status of drives connected to the device..

Code:

DIAGNOSTICS
       Normally, a logical drive in good working order should report a  status
       of "OK."  Possible status values are:

       "OK." (0) - The logical drive is in good working order.

       "FAILED."  (1)  -  The  logical  drive  has failed, and no i/o to it is
       poosible.

       "Using interim recovery mode." (3) - One or more drives has failed,
              but  not  so  many that the logical drive can no longer operate.
              The failed drives should be replaced as soon as possible.

       "Ready for recovery operation." (4) -  Failed drive(s) have been
              replaced, and the controller is about to begin rebuilding redun-
              dant parity data.

       "Currently recovering." (5) - Failed drive(s) have been replaced,
              and  the  controller  is  currently  rebuilding redundant parity
              information.

       "Wrong physical drive was replaced." (6) - A drive has failed, and
              another (working) drive was replaced.

       "A physical drive is not properly connected." (7) - There is some
              cabling or backplane problem in the drive enclosure.

So What module is running your controller ?

luciogodoy · 05-05-2008, 01:54 PM

Hi farslayer;

When the mcahine is post, i can see messages about the Data unit on port 1 id 4, but when linux fedora bootsnothing is there.

this is the out fron the commands:

# lsmod | grep scsi
scsi_mod 119757 5 usb_storage,libata,cciss,megaraid,sd_mod

# modinfo cciss
filename: /lib/modules/2.6.23.1-42.fc8/kernel/drivers/block/cciss.ko
license: GPL
version: 3.6.14
description: Driver for HP Controller SA5xxx SA6xxx version 3.6.14
author: Hewlett-Packard Company
srcversion: B21680A0AB9ABE0077D5612
alias: pci:v0000103Cd*sv*sd*bc01sc04i*
alias: pci:v0000103Cd00003230sv0000103Csd0000323Dbc*sc*i*
alias: pci:v0000103Cd00003230sv0000103Csd00003237bc*sc*i*
alias: pci:v0000103Cd00003238sv0000103Csd00003215bc*sc*i*
alias: pci:v0000103Cd00003238sv0000103Csd00003214bc*sc*i*
alias: pci:v0000103Cd00003238sv0000103Csd00003213bc*sc*i*
alias: pci:v0000103Cd00003238sv0000103Csd00003212bc*sc*i*
alias: pci:v0000103Cd00003238sv0000103Csd00003211bc*sc*i*
alias: pci:v0000103Cd00003230sv0000103Csd00003235bc*sc*i*
alias: pci:v0000103Cd00003230sv0000103Csd00003234bc*sc*i*
alias: pci:v0000103Cd00003230sv0000103Csd00003223bc*sc*i*
alias: pci:v0000103Cd00003220sv0000103Csd00003225bc*sc*i*
alias: pci:v00000E11d00000046sv00000E11sd0000409Dbc*sc*i*
alias: pci:v00000E11d00000046sv00000E11sd0000409Cbc*sc*i*
alias: pci:v00000E11d00000046sv00000E11sd0000409Bbc*sc*i*
alias: pci:v00000E11d00000046sv00000E11sd0000409Abc*sc*i*
alias: pci:v00000E11d00000046sv00000E11sd00004091bc*sc*i*
alias: pci:v00000E11d0000B178sv00000E11sd00004083bc*sc*i*
alias: pci:v00000E11d0000B178sv00000E11sd00004082bc*sc*i*
alias: pci:v00000E11d0000B178sv00000E11sd00004080bc*sc*i*
alias: pci:v00000E11d0000B060sv00000E11sd00004070bc*sc*i*
depends: scsi_mod
vermagic: 2.6.23.1-42.fc8 SMP mod_unload 686 4KSTACKS

# cat /var/log/dmesg | grep cciss
cciss0: <0xb178> at PCI 0000:00:01.0 IRQ 18 using DAC
cciss1: <0x46> at PCI 0000:08:04.0 IRQ 19 using DAC
cciss/c1d0: p1 p2
cciss/c1d1: p1
EXT3 FS on cciss/c1d1p1, internal journal
EXT3 FS on cciss/c1d0p1, internal journal

I haven't altered anything on the fedora install.

Any clues.

Thanks

Lucio

farslayer · 05-05-2008, 02:16 PM

do you have the ccis_vol_status utility available ?

https://sourceforge.net/project/show...kage_id=223791

luciogodoy · 05-05-2008, 04:59 PM

Just installed...

# cciss_vol_status -q /dev/cciss/c*d0
/dev/cciss/c0d0: (Smart Array 6400) RAID 1 Volume 0 status: OK.
/dev/cciss/c0d0: (Smart Array 6400) RAID 5 Volume 1 status: OK.

thanks

Lucio

farslayer · 05-05-2008, 10:44 PM

Guess that wasn't all that helpful for the current issue then... was worth a shot though. hmmm

luciogodoy · 05-06-2008, 01:36 PM

My friend at work said that there is a trick to connect the DAT tape onto the onboard compaq, rather than the Smart Array.

He didn't tell me the whole story, will find out tomorrow - chapter 2