Hi again.

Quick summary of the thread:

Replaced the tape drive in backup server. After that, got problems with 
amrestore:

> The backup ran for the first time tonight. The output that amdump sent
> me after the backup looked entirely normal, and also I could restore
> some files from the tape with amrecover. However, amverify is not
> happy (see output at the end of message).

> When I tried running amrestore directly from the command line, the
> following happened:

> kuller# amrestore /dev/nsa0 kuller.raad.tartu.ee / amrestore:
> WARNING: not at start of tape, file numbers will be offset
> amrestore: 0: reached end of information
> kuller#

Yesterday I wrote that the problem disappeared after using the cleaning 
tape. As it turns out, however, something is still wrong. I can now 
successfully extract backup images with amrestore (and I've always been 
able to recover individual files with amrecover), but amverify still 
fails with the same messages:

Tapes:  PAEV13
Errors found: 
PAEV13 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore:   0: reached end of information 
** No header 
0+0 in 
0+0 out
PAEV13 (): amrestore: WARNING: not at start of tape, file numbers will
be offset 
amrestore:   0: reached end of information 
** No header 
0+0 in
0+0 out
(...etc...)

Given that amrestore works OK from the command line, what might cause 
it to fail when invoked by amverify?
--
Toomas Aas | toomas.aas AT raad.tartu DOT ee | http://www.raad.tartu.ee/~toomas/
* My wife ran off with my best friend, and i sure do miss him.