RHEL 4 and HP StorageWorks DAT 72h

Hi all,

I would like to share an info for those of you who happened to install RHEL 4 (Red Hat Enterprise Linux 4) and has trouble finding the HP DAT 72 tape drive.

My hardware specification :
- HP ProLiant DL380 G3
( with HP Smart Array 5i RAID controller - cciss )
- HP StorageWorks DAT 72h (hot plug)
( plugged to the HP Smart Array 5i )

I installed RHEL 4 and was surprised to see that my tape drive was not detected. I re-traced "dmesg" and confirmed that it's not there.
I had no previous problem with my RHEL 3.

After 30 minutes of search here's the solution to the problem.
Step by Step:[list=1][*]First try to see with :

# modprobe st

( if you have no error message, then you are good to go )
[*]Do the following :

# echo "engage scsi" > /proc/driver/cciss/cciss0
# echo "rescan" > /proc/driver/cciss/cciss0

[*]Check dmesg again

# dmesg

[*]Verify that you should have /dev/st0 and /dev/tape hardlink-ed to it
( automatically created for you )[*]Finally put the above 2 echo command to the /etc/rc.local so that it will be executed everytime the system start.[/list=1]

The above can be applied to any tape drives connected to the Smart Array 5i (cciss).
Hope it helps ...

Thanks for posting information. I personally have no use for it, but I am pleased to see someone providing information rather than asking questions. It's a nice reprieve from the hundreds of questions posted withou first consulting google.

I have a similar configuration, and while it loads the cciss scsi driver and finds the tape drive, the system comes up with the following kernel errors:

ERROR: SCSI host `cciss' has no error handling
ERROR: This is not a safe way to run your SCSI host
ERROR: The error handling must be added to this driver

Do you get these messages, and if so, does it cause any problems?

Thanks for the info, though - it's definitely a bit step in the right direction.

Mykel

Ketut Mahaindra ,
I would like to thank you for posting this solution. I have been struggling for the past few days to get the HP Storage Products DAT 40 Tape drive detected on a HP Proliant DL 380 G4 Server running REDHAT Enterprise AS Version 3 Operating System.

After following the solution that you have posted, I was finally able to see the tape drive being
attached.

#cat /proc/scsi/scsi

The above command have listed the Tape Drive under the Attached Devices.

Thanks very much for posting this solution, and getting me past this hurdle.

Sagar

Originally Posted by mykel I have a similar configuration, and while it loads the cciss scsi driver and finds the tape drive, the system comes up with the following kernel errors: ERROR: SCSI host `cciss' has no error handling ERROR: This is not a safe way to run your SCSI host ERROR: The error handling must be added to this driver Do you get these messages, and if so, does it cause any problems? Thanks for the info, though - it's definitely a bit step in the right direction. Mykel

Yes, I have the same kernel errors.
But so after I have not seen any problems with the tape drive.
My backup system work perfectly well on backup and restore with the tape drive.
I checked with RedHat support and they say that this is not their responsibility as the cciss driver is provided by HP. So they are waiting or should I say put the responsibilities on HP to fix this issue.

p.s.
- I am using bacula as my backup system, it's free and it works perfectly for me

I am runing on RedHat EL 4 update 3. Although I run this 2 command
# modprobe st
# echo "engage scsi" > /proc/driver/cciss/cciss0
# echo "rescan" > /proc/driver/cciss/cciss0


while I browse the dmesg, I get this,
cciss0: SCSI subsystem already engaged.

May I know what is refering to and got any one got solution to solve it.

Hello,

That message should be ok, the commands is instruct the system to perform the SCSI detection process again.
What you should try to see in your dmesg is whether you see the tape drive being detected or not.

Hi kmahaindra,

thanks for your hint! Allthough it is quiet "old", I was faced with this problem actually and it saved me another trial-and-error session.

Best regards,
Dirk