Hi!, I've some problems with various tapes and my amanda. 

1 - In my last amcheck I can see the following:

Amanda Tape Server Host Check
-----------------------------
ERROR: /dev/nst0: reading label: Input/output error
       (expecting tape FURV-POLICY05 or a new tape)
NOTE: skipping tape-writable test
Server check took 0.051 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 0.129 seconds, 0 problems found

(brought to you by Amanda 2.4.2p2)

The first problem is that the tape inserted in nst0 is the FURV-POLICY05. The 
last backup to this tape was right ( bcause amreport was right ). When I try to 
amcheck or amverify FURV-POLICY05 the result is always the message above.

2 - My last backup with FURV-POLICY04 said:

FAILURE AND STRANGE DUMP SUMMARY:
  xaloc      /dev/sdc2 lev 0 FAILED [out of tape]
  xaloc      /dev/sdc2 lev 0 FAILED ["data write: Connection reset by peer"]
  xaloc      /dev/sdc2 lev 0 FAILED [dump to tape failed]

FAILED AND STRANGE DUMP DETAILS:

/-- xaloc      /dev/sdc2 lev 0 FAILED ["data write: Connection reset by peer"]

... Do you think there was any intranet-problem? Is the reason probably another?

I've been looking for into logs and I've encountered the following:

May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc kernel: st0: Error on write filemark.
May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc sendbackup[14906]: index tee cannot write [Broken pipe]
May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc kernel: st0: Error with sense data: Current st09:00: 
sense key Medium Error
May 22 03:21:09 xaloc kernel: Additional sense indicates Excessive write errors
May 22 03:21:09 xaloc kernel: st0: Error on write filemark.

It corresponds (surely) with the FURV-POLICY04 backup. When I try to amverify 
FURV-POLICY04 contents the result is:

No tape changer...
Tape device is /dev/nst0...
Verify summary to rcruz AT stq.urv DOT es cllorach AT stq.urv DOT es apoto AT 
stq.urv DOT es
Defects file is /tmp/amanda/amverify.27490/defects
amverify furv-policy
Fri May 23 10:12:05 CEST 2003

Using device /dev/nst0
Waiting for device to go ready...
Rewinding...
Processing label...
Volume FURV-POLICY04, Date 20030522
Rewinding...
Checked xaloc._etc.20030522.1
Checked kannagara._etc.20030522.1
Checked xaloc._dev_sdd1.20030522.1
Checked xaloc._dev_sdc1.20030522.1
** Error detected (xaloc._dev_sdc2.20030522.0)
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore:   0: restoring xaloc._dev_sdc2.20030522.0

gzip: stdin: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
64+0 records in
64+0 records out
Checked xaloc._etc.20030522.1
Checked kannagara._etc.20030522.1
Checked xaloc._dev_sdd1.20030522.1
Checked xaloc._dev_sdc1.20030522.1


*** What about these two problems with FURVPOLICY 04 and 05? What can I do? or 
what must I do? *****


Best regards,
 
Raúl
rcruz AT wild-spain DOT com