On Tue, 2 Apr 2002, Toomas Aas wrote:

> Hi Doug!
> 
> On  1 Apr 02 at 17:46 you wrote:
> 
> > So for the non-rewinding tape device I put in /dev/nsa0, which seems to
> > make sense after reading the mt and sa man pages (I know, I shouldn't be
> > RTFM'ing before hand, but oh well ;).  I've tried both /dev/nsa0 and
> > /dev/nrsa0 -- both failed!
> 
> /dev/nsa0 works fine here with FreeBSD and SCSI DDS-3 drive.
> 
> > So, when I try to access the drive by running amflush I get this kernel
> > message:
> > 
> > (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
> > command to clear this state.
> 
> When I get this message it's always one of two things:
> - tape is bad and needs to be thrown away
> - tape drive needs cleaning

Well, I'm leaving it as /dev/nsa0 since that appears to be the correct
device.  Now I'm a bit confused.  I tried cleaning the drive (just did it
last month, but can't hurt to do it again), but still got that same error.  
Put a brand new tape in and voila, that worked.  So how many of my
existing 15 tapes will need to be replaced?  How many times do you
generally use each tape (rough number)?  I bet there's not much of a
difference between DDS3 and DDS4 tapes as far as useful duration.  The one
I replaced had been used 17 times over the last year or so, but some of
the other ones have even more, but I've never had any tape errors, so I
figured they were okay (uh-oh I can see that assumption biting
me!).  Perhaps the FreeBSD tape driver is a bit more sensitive about tape
errors.


> 
> >   DUMP: Dumping /etc to /dev/nsa0
> >   DUMP: bad sblock magic number
> >   DUMP: The ENTIRE dump is aborted.
> 
> Bad sblock magic number? Are you sure that /etc is a separate UFS 
> partition? If it's just a subdirectory on / partition, it cannot be 
> dumped.
> 

Uh, ooooops.  RTFM ....

> --
> Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
> * Dyslexics of the world, untie!
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Doug Silver
Network Manager
Quantified Systems, Inc
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to