I have two freebsd boxes.  Box A is 4.4.  Box B is 4.7.

Box A has a cybernetics DAT tape drive.

Box B has a cybernetics AIT/dlt tape drive.

I found that with the DAT drive I must set the tape density and
blocksize or else the tapes are unreadable, ie the default driver
status set the tape to variable block with some strange density.  If
it don't set the blocksize to 512 and the density to dds4 prior to
writing to the tape, it is unreadable.  

That lead me to check these parms on the AIT drive.  However, issueing
a density command causes an error.  See below.  I was using linux on
this system prior to fbsd.  I made tapes of data sets I wanted to
restore with tar.  However, after fbsd was installed, the tapes were
unreadable.  So, I thought I'd hit the same issue with density and
blocksize.  But I can't set density.  I'm beginning to really hate
tape units as they all see very different in the way they behave.
Is there a really good FAQ on tape units for fbsd?

=======================================

# Issuing commands

mt density 0x41
mt: /dev/nsa0: density: Invalid argument
assurbanipal# mt density DLTapeIV
Using "DLTapeIV" as an alias for 0x1a:DLTapeIV(20GB)
mt: /dev/nsa0: density: Invalid argument

# cause these kernel messages

(sa0:ahc1:0:10:0): MODE SELECT(06). CDB: 15 0 0 0 c 0
(sa0:ahc1:0:10:0): ILLEGAL REQUEST asc:26,0
(sa0:ahc1:0:10:0): Invalid field in parameter list sks:8f,4
(sa0:ahc1:0:10:0): MODE SELECT(06). CDB: 15 0 0 0 c 0
(sa0:ahc1:0:10:0): ILLEGAL REQUEST asc:26,0
(sa0:ahc1:0:10:0): Invalid field in parameter list sks:8f,4

mt blocksize 512
assurbanipal# mt status
Mode      Density              Blocksize      bpi      Compression
Current:  0x30                 512 bytes      0        unsupported
---------available modes---------
0:        0x30                 512 bytes      0        unsupported
1:        0x30                 512 bytes      0        unsupported
2:        0x30                 512 bytes      0        unsupported
3:        0x30                 512 bytes      0        unsupported
---------------------------------
Current Driver State: at rest.
---------------------------------
File Number: 0  Record Number: 0        Residual Count 0

================================

not also that in the man page for mt, there is no 0x30 density mode
listed.. And I have tried other modes as well.  They all through
errors.


-- 
David Bear
phone:  480-965-8257
fax:    480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
 "Beware the IP portfolio, everyone will be suspect of trespassing"
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to