Hi,

Brett Lymn <blymn@baesystems.com.au> wrote:

[...]

> Use the raw device when using tar/dump/pax because they are writing
> their own data format.

Hmm, after further testing the drive in deed seems to work when
accessed via the raw device.

But I encountered some more difficulties:

# mt -f /dev/rst0 setblk nnn

does nothing according to the output of

# mt -f /dev/rst0 status     or
# mt status

other mt commands as status, erase or rewind appear to be working
whether or whether not the target is specified.

BTW: There ist only one tape drive connected to the system, but the
device entries exist for both (r)st0 and (r)st1.



# mt setblk nnn

_without_ specifying the target works, but the next call of mt status
lets the drive forget the given blocksize and it falls back to the
default 0, meaning variable blocksize. Calling mt status twice gives
the choosen blocksize the first time and zero the next time.



Additionally, mt erase (with or without target) works, but outputs the
following message to /dev/console and /var/log/messages:

Aug 16 17:16:48 popeye /netbsd: st0(esp0:0:6:0): esp0: timed out [ecb 0xf047c0a8 (flags 0x101, dleft 0, stat 0)], <state 1, nexus 0x0, phase(l 10, c 100, p 3), resid 0, msg(q 0,o 0) >

I already had this issue when accessing some HDDs. What does the
message mean? Is there anything wrong with the SCSI H/W, termination,
.... ?


cheers,
\end{kryz}

-- 
Q: How is "SunOS" spelled?
A: As one speaks it. With capital "S-O-S".