DL380 RedHat ES 3 DAT 20/40 HotPlug Carbon

[Romeo_4]

Hi,

The hotplug DAT 20/40 carbon is not configured on redhat Es3. It doesn't work. When boot the system the Smart Array show disks con channel 0 and the tape on channel 1 but when boot linux teh only controller is c0 and the devive d0. The tape is not configured. I have not found any new driver for red hat es 3 but is available new driver for AS2.1 and Smart Array updated to august.

Some one have found the same problem? some suggestion or solutions ? thanks

[Kodjo Agbenu]

Hi,

The device file used to access the DAT is /dev/st0 (or /dev/nst0 for no-rewind), not /dev/cciss/cXdY.

To check if the tape device is detected :

cat /proc/scsi/scsi

You can also have a look at boot messages in syslog (/var/log/messages).

Good luck.

Kodjo

[Romeo_4]

Proc/scsi/scsi
attached device: none

message doesn't show the device

sigh!!

[Kodjo Agbenu]

Try : modprobe aic7xxx, then check /proc/scsi/scsi again.

Kodjo

[Stuart Browne]

No, the hot-plug tape drive runs of the cciss (raid) controller.

It does however require one or two settings to be configrued within the kernel.

Specifically the 'CONFIG_CISS_SCSI_TAPE' setting.

This defaults to 'y' on a RHES3 system however.

Here's an note in the kernel documentation with regards to this feature:

(taken from /usr/src/linux-2.4/Documentation/cciss.txt)
-----
Additionally, note that the driver will not engage the SCSI core at init time. The driver must be directed to dynamically engage the SCSI core via the /proc filesystem entry which the "block" side of the driver creates as /proc/driver/cciss/cciss* at runtime. This is because at driver init time, the SCSI core may not yet be initialized (because the driver is a block driver) and attempting to register it with the SCSI core in such a case would cause a hang. This is best done via an initialization script (typically in /etc/init.d, but could vary depending on distibution).
For example:

for x in /proc/driver/cciss/cciss[0-9]*
do
echo "engage scsi" > $x
done

Once the SCSI core is engaged by the driver, it cannot be disengaged (except by unloading the driver, if it happens to be linked as a module.)
-----

So basically, you need to tell the cciss driver to go looking, it won't do it by it's self.

I'd suggest reading through the above mentioned file for further details, i.e. how to re-scan the bus upon tape-drive change etc..

[Acharya]

i am getting the same kin d of problem please if u can help me ou twith the same