On Wed, 16 Feb 2005, Hauke Fath wrote:

> Am 16.02.2005 um 22:09 Uhr +0200 schrieb Peter L. Peres:
>> I am trying to continue my taping experience. I was able to test a tdc 
>> 4200 under netbsd and it gave me io errors on access.
>
> The exact error messages could help here.

Ok, some follow below. Keep in mind that I do not know if the drive is 
ok. It did not pass its self test but the code it flashed relates to a 
lock and not to a failure. I do not know enough about this streamer to 
draw conclusions.

>> I am not sure if I used a compatible cartridge though. This drive is 
>> reported as 'rogue' by the detect code in the kernel. Before I waste too 
>> much time with this, has anyone got a tdc 4200 or similar tape working 
>> under netbsd ?
>
> I ran a 4220 for years with a hacked st driver -- the QIC EOM handling is 
> special. Without seeing your error messages it's hard to tell, though, 
> whether the quirk entries are still needed.

this is typical for what I get:
Feb 16 10:28:06 netbsd /netbsd: st1 at scsibus0 target 0 lun 0: 
<TANDBERG, TDC 4
200, =07:> SCSI2 1/sequential removable
Feb 16 10:28:06 netbsd /netbsd: st1: rogue,
Feb 16 10:28:06 netbsd /netbsd: drive empty
Feb 16 10:28:06 netbsd /netbsd: st1: async, 8-bit transfers
Feb 16 10:29:05 netbsd /netbsd: st1: error 5 in st_load (op 1)

then this:
Feb 15 19:57:49 netbsd /netbsd:     SENSE KEY:  Media Error
Feb 15 19:57:49 netbsd /netbsd:    INFO FIELD:  27
Feb 15 19:57:49 netbsd /netbsd:      ASC/ASCQ:  ASC 0x00 ASCQ 0x07
Feb 15 19:57:49 netbsd /netbsd:
Feb 15 20:31:02 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x08
  01 00 00 3c 00
Feb 15 20:31:02 netbsd /netbsd:     SENSE KEY:  Media Error
Feb 15 20:31:02 netbsd /netbsd:    INFO FIELD:  20
Feb 15 20:31:02 netbsd /netbsd:      ASC/ASCQ:  End-Of-Partition/Medium 
Detected
Feb 15 20:31:02 netbsd /netbsd:
Feb 15 20:40:00 netbsd /USR/SBIN/CRON[279]: (root) CMD 
(/usr/libexec/atrun)
Feb 15 20:47:07 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x08
  01 00 00 3c 00
Feb 15 20:47:07 netbsd /netbsd:     SENSE KEY:  Blank Check
Feb 15 20:47:07 netbsd /netbsd:    INFO FIELD:  60
Feb 15 20:47:07 netbsd /netbsd:      ASC/ASCQ:  No Additional Sense 
Information
Feb 15 20:47:07 netbsd /netbsd:
Feb 15 20:47:37 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x08
  01 00 00 3c 00

goes on like this for a while, then:

Feb 15 21:11:56 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x0a
  01 00 00 3c 00
Feb 15 21:11:56 netbsd /netbsd:     SENSE KEY:  Illegal Request
Feb 15 21:11:56 netbsd /netbsd:      ASC/ASCQ:  No Additional Sense 
Information
Feb 15 21:11:56 netbsd /netbsd:
Feb 15 21:11:56 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x10
  00 00 00 02 00
Feb 15 21:11:56 netbsd /netbsd:     SENSE KEY:  Illegal Request
Feb 15 21:11:56 netbsd /netbsd:      ASC/ASCQ:  No Additional Sense 
Information
Feb 15 21:11:56 netbsd /netbsd:
Feb 15 21:11:56 netbsd /netbsd: st0(pcscp0:0:1:0):  Check Condition on 
CDB: 0x0a
  01 00 00 03 00

several times (meanwhile the command hung, so I killed it and reset the 
scsi bus so the messages stopped).

this drive is almost 10 years old and I am not sure whether I want to 
waste a lot of time on it. An equally old Viper QIC-150MB worked well 
with this setup (just for testing).

thanks,
Peter