DAT 72 in RH Linux AS 3 on ML 370

[Ayman_8]

Hi all

i installed a tape drive after the installation of linux .
i cant access the tape drive :
mt -f /dev/st0 status
gives me
/dev/st0: No such device

in the dmesg output i can find these two lines
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36

and here is the output of lsmod :
st 32388 0 (unused)
sg 38060 0 (autoclean) (unused)
ide-cd 35776 0 (autoclean)
cdrom 34144 0 (autoclean) [ide-cd]
parport_pc 19204 1 (autoclean)
lp 9220 0 (autoclean)
parport 39072 1 (autoclean) [parport_pc lp]
autofs 13780 0 (autoclean) (unused)
tg3 57736 1
floppy 59056 0 (autoclean)
microcode 5248 0 (autoclean)
vfat 13196 0 (autoclean)
fat 40184 0 (autoclean) [vfat]
keybdev 2976 0 (unused)
mousedev 5688 1
hid 22404 0 (unused)
input 6208 0 [keybdev mousedev hid]
usb-ohci 23688 0 (unused)
usbcore 83168 1 [hid usb-ohci]
ext3 95784 6
jbd 56856 6 [ext3]
cciss 46276 7
aic7xxx 165616 1
sd_mod 13744 0 (unused)
scsi_mod 116904 4 [st sg cciss aic7xxx sd_mod]

and here is the output of cat /proc/scsi/scsi
Attached devices: none

i have also a folder /proc/scsi/aic7xxx
contains two files 0 and 1 . here is the content of the 0 file :
Adaptec AIC7xxx driver version: 6.2.36
Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Allocated SCBs: 6, SG List Length: 85

Serial EEPROM:
0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a
0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a
0x08f4 0x605d 0x2807 0x0010 0x0301 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x4a50

Target 0 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

i hope that you can find the problem from these outputs .
kindly advise about how to solve the problem

[Steven E. Protter]

As i start, I'd look at the hardware. It has a little setting button setup on the back for the SCSI id. If it is set to the same scsci id as the scsci card you will have issues like this.

Power off the unit and change the id on the device. The default id for a card is usually zero.

These tape drives do much better btw when they are not daisy chained with any other devices like disk. You'll get better throughput and less interference that way.

SEP

[Stuart Browne]

Internal or External unit?

As SEP points out, it'd be good to check the SCSI ID.

Reboot the server, and watch the SCSI card initilisation. It should report the tape drive there. If it doesn't, then check cabling.

In an ML370, it should be attached to one of the Adaptec (on-board) SCSI controllers, as against the RAID controllers.

If it's external, ensure that it's powered up, and terminated correctly, before powering the server up.

If it's internal, make sure the SCSI string has a terminator on the end of it.

If it's still not coming up after doing all of that, then make sure that the device is getting power. The lights should flash green upon power-up.

If it is showing up in the SCSI BIOS during boot-up, then the device should be available from the OS. There will be a 'Sequential Access' device listed in '/proc/scsi/scsi'.

If it is showing up in that file, then the '/dev/st0' should be linked correctly. You may want to run 'kudzu' to just make sure of that.

Anyway, some things to look at.