topic Re: Smart Array 5i Controller driver for Linux in Operating System - Linux

Smart Array 5i Controller driver for Linux

Sanjay_23 — Wed, 03 Nov 2004 20:55:26 GMT

H/w: HP DL380

Friends,
I'm installing Sentry Firewall but when booting the OS using the CD & config floppy, I still can not access the local disk of the server.

When I give the #lsmod command, it shows that the CCISS modules is unused. I checked the /var/adm/messages file & it shows that the kernel recognises the HP CISS Driver but still not sure as why I can't see the local drives.
Why the CCISS module is shown as "unused".

Thanks in advance.

Re: Smart Array 5i Controller driver for Linux

Hein van den Heuvel — Wed, 03 Nov 2004 22:45:25 GMT

Are there logical drives defined and available on the smart array?

While you boot the box, it will output a section for each smart- array starting with the line 'initializing' (with those fake rotors at the end), a count of unites presented, and a prompt for to go on, to set up.
Hit that F8 and view the drives?

You may also want to download the "Array Control Utility' = ACU = cpqacuxe. Then again, if the driver is not active that might not be able to talk.

fwiw,
Hein.

Re: Smart Array 5i Controller driver for Linux

Sanjay_23 — Wed, 03 Nov 2004 22:55:39 GMT

The disk (c0d0) has already got Linux installed.

The process to install the Sentry Firewall is -

1. Boot from the CD.
2. The CD refers to the configuration file from the floppy & reads it.
3. It creates ramdisk partition where it copies all the config. files.

The issue is, I can access the ramdisk etc. But when trying to access the logical disk, I'm in trouble.

Do I need to modify any configuration changes in the floppy or copy any other files in the CD?

Here's the website to the Sentry Firewall webpage - http://www.sentryfirewall.com/ - Any other thoughts?

Re: Smart Array 5i Controller driver for Linux

Stuart Browne — Wed, 03 Nov 2004 23:45:00 GMT

It sounds like the kernel revision on the CD is a bit old, or stripped so it doesn't have full driver complement.

That being said, 1.5.0-rc15 says it's using a 2.4.27 based kernel, which should have a sufficient enough driver for a '5i', assuming it's compiled in.

You might want to look at the instructions at http://www.sentryfirewall.com/files/HOWTO/sentry-firewall-cd-howto-3.html#ss3.5 for modifying the CD's boot-kernel to try using a newer 'cciss' or something.

Re: Smart Array 5i Controller driver for Linux

Sanjay_23 — Thu, 04 Nov 2004 00:00:02 GMT

All steps followed from the url & updated the cd accordingly.

The kernel recognises the HP CISS driver & the entry gets into the /var/adm/messages file.

The kernel also identifies the cylinders, sectors etc. of the hard disk but the lsmod still shows the cciss module as "unused"?????

Re: Smart Array 5i Controller driver for Linux

Sanjay_23 — Thu, 04 Nov 2004 00:21:14 GMT

Below are the excerpt from the log files:

Nov 4 11:50:56 server1 kernel: HP CISS Driver (v 2.4.52)
Nov 4 11:50:56 server1 kernel: blocks= 142253280 block_size= 512
Nov 4 11:50:56 server1 kernel: heads= 255, sectors= 32, cylinders= 17433 RAID 1(0+1)
Nov 4 11:50:56 server1 kernel: Partition check:
Nov 4 11:50:56 server1 kernel: cciss/c0d0: p1 p2

Contents of /etc/modules.conf
--------------------------------
alias scsi_hostadapter1 cciss

Re: Smart Array 5i Controller driver for Linux

Stuart Browne — Thu, 04 Nov 2004 01:10:20 GMT

I'm afraid I've not used the firewall product, so can't help here. I'd see if there was a Sentry Filweall Mailing list, and ask them if they've witnessed similar behaviour.

Re: Smart Array 5i Controller driver for Linux

Sanjay_23 — Thu, 04 Nov 2004 17:22:01 GMT

Guys,

I found the solution -

The device file has to be created using the following script:
#!/bin/sh
# Script to create device nodes for SMART array controllers
# Usage:
# mkdev.cciss [num controllers] [num log volumes] [num partitions]
#
# With no arguments, the script assumes 1 controller, 16 logical volumes,
# and 16 partitions/volume, which is adequate for most configurations.
#
# If you had 5 controllers and were planning on no more than 4 logical volumes
# each, using a maximum of 8 partitions per volume, you could say:
#
# mkdev.cciss 5 4 8
#
# Of course, this has no real benefit over "mkdev.cciss 5" except that it
# doesn't create so many device nodes in /dev/cciss.

NR_CTLR=${1-1}
NR_VOL=${2-16}
NR_PART=${3-16}

if [ ! -d /dev/cciss ]; then
mkdir -p /dev/cciss
fi

C=0; while [ $C -lt $NR_CTLR ]; do
MAJ=`expr $C + 104`
D=0; while [ $D -lt $NR_VOL ]; do
P=0; while [ $P -lt $NR_PART ]; do
MIN=`expr $D \* 16 + $P`
if [ $P -eq 0 ]; then
mknod /dev/cciss/c${C}d${D} b $MAJ $MIN
else
mknod /dev/cciss/c${C}d${D}p${P} b $MAJ $MIN
fi
P=`expr $P + 1`
done
D=`expr $D + 1`
done
C=`expr $C + 1`
done

Thanks to the site owner of - http://www.ibiblio.org/peanut/Kernel-2.6.6/mkdev.cciss