Hi everyone,
I am trying to get a DAT tape drive going under kernel 2.2.16. I am using
the supplied aha1542 module.
The DAT drive is a SONY SDT 4010 (DDS1).
I load the scsi modules and get the following messages
Jun 21 00:30:35 talbot kernel: Configuring Adaptec (SCSI-ID 7) at IO:330,
IRQ 11, DMA priority 6
Jun 21 00:30:35 talbot kernel: scsi0 : Adaptec 1542
Jun 21 00:30:35 talbot kernel: scsi : 1 host.
Jun 21 00:30:36 talbot kernel: Vendor: SONY Model: SDT-4000
Rev: 2.05
Jun 21 00:30:36 talbot kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Jun 21 00:30:36 talbot kernel: st: bufsize 32768, wrt 30720, max buffers 5,
s/g segs 16.
Jun 21 00:30:36 talbot kernel: Detected scsi tape st0 at scsi0, channel 0,
id 4, lun 0
The tape is loaded into the drive as below
[root@talbot /root]# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (1010000):
ONLINE IM_REP_EN
[root@talbot /root]#
I can also do OK
[root@talbot /root]# mt -f /dev/st0 retension
I then try to access with ARKEIA (X based tape backup)
Jun 21 00:37:29 talbot kernel: aha1542.c: Trying device reset for target 4
Jun 21 00:37:42 talbot kernel: Sent BUS RESET to scsi host 0
Jun 21 00:37:52 talbot kernel: st0: Error with sense data: [valid=0] Info
fld=0x0, Current st09:00: sense key Unit Attention
Jun 21 00:37:52 talbot kernel: Additional sense indicates Power on, reset,
or bus device reset occurred
Jun 21 00:37:52 talbot kernel: st0: Error with sense data: [valid=0] Info
fld=0x0, Current st09:00: sense key Not Ready
Jun 21 00:37:52 talbot kernel: Additional sense indicates Logical unit is in
process of becoming ready
It seems to crash the aha1542 driver as I get
[root@talbot src]# mt -f /dev/st0 status
/dev/st0: Device not configured
Reloading the modules allows me to the above all over again!
Can anyone suggest anything?
Thanks
Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
