Re: amrestore problems after replacing tape drive
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 | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * My wife ran off with my best friend, and i sure do miss him.
Re: amrestore problems after replacing tape drive
Hi, AFAIK you'll have to rewind the tape explicitly between amdump and amverify, as neither amdump nor amverify do that for you. Christoph Toomas Aas schrieb: 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 | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * My wife ran off with my best friend, and i sure do miss him.
Re: amrestore problems after replacing tape drive
Hi! Christoph Scheeder wrote: AFAIK you'll have to rewind the tape explicitly between amdump and amverify, as neither amdump nor amverify do that for you. Christoph I tried running mt rewind and then amverify from command line. Still the same errors... -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * The secret of the universe is @*^^^# NO CARRIER
Re: amrestore problems after replacing tape drive
Toomas Aas wrote: Hi again. 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 Whenever (very seldomly)I get the not at start of tape error, I ran the vtblc program that lists the contents of the tape header (the virtual table) and then it's O.K. But this advice may be QIC-specific, so YMMV (I use the ftape programm and tools). -- Regards Chris Karakas http://www.karakas-online.de
Re: amrestore problems after replacing tape drive
Hi! Yesterday, I wrote about my problems after replacing the tape drive: 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# And, from the lameness-of-the-day department, here's what solved the problem: Use the cleaning tape. Period. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Why is there so much month left at the end of the money?
amrestore problems after replacing tape drive
Hello! Please CC: any possible replies to me. I sent subscribe request a couple of hours ago, but nothing seems to have happened yet. I'm running Amanda 2.4.3b4 on FreeBSD 4.7. And yes, I understand that 'b' means beta. Yesterday I replaced the tape drive in the backup server. The old drive was HP C1537A (DDS3). The new drive is IBM DDS4, actually a re-badged Seagate 0624 drive. I also started using DDS4 tapes. I made no changes to any configuration files (yet). I'm using dump and restore as the backup software. The drive is set to do hardware compression. 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# The messages are returned immediately, without any kind of delay I imagined would be involved in dealing with the tape drive. I ran 'mt status' and got the following: kuller# mt status Mode Density Blocksize bpi Compression Current: 0x26:DDS-4 1024 bytes 97000DCLZ -available modes- 0:0x26:DDS-4 1024 bytes 97000DCLZ 1:0x26:DDS-4 1024 bytes 97000DCLZ 2:0x26:DDS-4 1024 bytes 97000DCLZ 3:0x26:DDS-4 1024 bytes 97000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 64 Residual Count 0 kuller# It seems that my tape drive uses 1k blocks. Assuming that this is the same blocksize which is used by amrestore, I tried telling amrestore to use it, but it refused: kuller# amrestore -b 1k /dev/nsa0 kuller.raad.tartu.ee / amrestore: minimum block size is 32k kuller# Is it possible that amrestore can't read the tape because it has been written with too small blocksize? Or am I barking under completely wrong tree here? It doesn't seem to be hardware problem, because, as I said, I can back up with amdump and restore with amrecover, the only thing that doesn't work is amrestore (and thus, amverify). Unfortunately I don't remember what the blocksize reported by 'mt status' was with the old HP DDS3 drive. Finally, as promised, here's tonight's amverify output. - cut here - Tapes: PAEV11 Errors found: PAEV11 (): 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 PAEV11 (): 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 PAEV11 (): 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 PAEV11 (): 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 PAEV11 (): 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 PAEV11 (): 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 amverify PAEV Tue Jan 14 23:16:55 EET 2003 Loading current slot... Using device /dev/nsa0 Volume PAEV11, Date 20030114 Checked kuller.raad.tartu.ee._var.20030114.0 ** Error detected () 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 Checked heerold.raad.tartu.ee._.20030114.0 ** Error detected () 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 Checked kuller.raad.tartu.ee._usr.20030114.0 ** Error detected () 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 Checked kuller.raad.tartu.ee._.20030114.0 ** Error detected () 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 Checked heerold.raad.tartu.ee._var.20030114.0 ** Error detected () 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 Checked heerold.raad.tartu.ee._usr.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of
