On Saturday 14 September 2002 21:24, Jason Thomas wrote:
>On Sat, Sep 14, 2002 at 12:40:02PM -0400, Gene Heskett wrote:
>> Does one or more of these drives inadvertantly have the terms
>> turned on even though its not the last device in the chain?
>
>I don't think so, but I will double check!
>
>> > They
>> > receive continual use all day serving home directory's and
>> > company documents.
>
>sorry Gene its was amverify:
>> >This is there error I get from amcheck:
>> >
>> >Tapes:  DailySet109
>> >Errors found:
>> >DailySet109 (imhotep.ext.tsa._imhotep.20020913.4):
>> >amrestore: WARNING: not at start of tape, file numbers will be
>> > offset
>
>and its not all of it, its just the first part and it repeats for
> a number of different filesystems.
>
>
>heres more:
>
>Loading current slot...
>Using device /dev/scsi/host0/bus0/target15/lun0/mtn
>Volume DailySet109, Date 20020913
>Checked imhotep.ext.tsa._opt.20020913.1
>Checked emma.tsa._emma_mp3_i.20020913.1
>Checked sobek.tsa._etc.20020913.0
>.
>.
>.
>Checked hathor.tsa._hathor_httpd.20020913.2
>Checked emma.tsa._emma_mp3_z.20020913.1
>Checked hathor.tsa._hathor_projects3.20020913.1
>Checked emma.tsa._emma_mp3_remixes.20020913.1
>** Error detected (imhotep.ext.tsa._imhotep.20020913.4)
>amrestore: WARNING: not at start of tape, file numbers will be
> offset amrestore:   0: restoring
> imhotep.ext.tsa._imhotep.20020913.4 /bin/tar: Skipping to next
> header
>/bin/tar: Error exit delayed from previous errors
>64+0 records in
>64+0 records out
>Checked emma.tsa._emma_mp3_q.20020913.1
>** Error detected (hathor.tsa._hathor_projects2.20020913.1)
>amrestore: WARNING: not at start of tape, file numbers will be
> offset amrestore:   0: restoring
> hathor.tsa._hathor_projects2.20020913.1 /bin/tar: Skipping to
> next header
>/bin/tar: Skipping to next header
>/bin/tar: Error exit delayed from previous errors
>64+0 records in
>64+0 records out
>Checked bast.tsa._bast.20020913.2
>Checked bast.tsa._backup_intraspect-backups.20020913.1
>Checked bast.tsa._etc.20020913.0
>Checked set.ext.tsa._etc.20020913.1
>End-of-Tape detected.
>Advancing past the last tape...

Odd, indeed.  I just fired mine off to work over the tape it will 
re-use in about an hour, so I may not be able to let it run 
completely thru the tape.  So far, and its now on the 37th tarfile 
of 37 of that tape, there have been no errors, and, no mention of 
using amrestore in what I see output here.  However, I note in the 
kpm report that amverify has indeed called amrestore, to read the 
tape I assume.

So far, if the terms are ok and all that, I'm beginning to think 
either that tape brand is a bit flaky, or that your drive is 
thinking seriously of dieing for good, worn head or some such.  If 
its the tape, I'd think the error would repeat at the same place on 
another run against the same tape, rather than moving around 
randomly.  

I assume that you have a cleaning tape, and that it has been used 
recently, just to see if it effected the error rate one way or the 
other.  Running the cleaning tape on a head thats about fini will 
often make the errors worse, sometimes very quickly.  Any SWAG as 
to how many actual tape running hours might be on it?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.15% setiathome rank, not too shabby for a WV hillbilly