Re: ASC/ASCQ: Write Append Position Error

On Wed, May 10, 2006 at 02:38:58PM +0200, Andreas_Hallmann wrote:
> Hi all,
> 
> last backup stoped with a tapeing error.
> >From /var/log/messages I got a more descriptive reason.
> 
> ------------------------------------------
> May  9 22:11:01 kukalda /netbsd: st0(esiop1:0:4:0):  DEFERRED ERROR, key = 0x3
> May  9 22:11:01 kukalda /netbsd: st0(esiop1:0:4:0):  Check Condition on CDB: 
> 0x0a 00 00 80 00 00
> May  9 22:11:01 kukalda /netbsd: SENSE KEY:  Media Error
> May  9 22:11:01 kukalda /netbsd: INFO FIELD:  32768
> May  9 22:11:01 kukalda /netbsd: ASC/ASCQ:  Write Append Position Error
> May  9 22:11:01 kukalda /netbsd: 
> May  9 22:11:01 kukalda /netbsd: st0(esiop1:0:4:0):  Check Condition on CDB: 
> 0x10 00 00 00 02 00
> May  9 22:11:01 kukalda /netbsd: SENSE KEY:  Media Error
> May  9 22:11:01 kukalda /netbsd: ASC/ASCQ:  Write Append Position Error
> May  9 22:11:01 kukalda /netbsd: 
> ------------------------------------------
> 
> /dev/st0 is an Exabyte 8505 XL.

Are you really using st0, not nst0, for amanda.
Or perhaps the messages are generic, not really
referencing the drive name that was opened.

> 
> The Exabyte Manual is not realy helpful, except pointing me to 
> my backup software vendors suport (heavy waving -- huhu )
> 
> The SCSI Specs speficy that "ASC/ASCQ: Write append position error" is a
> more precise version of the message "media error".
> 
> May be I'm stupid, I don't know what "Write append position error" meens.
> 
> I'm getting nervous. After four years of sitting silently side by side on my 
> desk,
> my Exabyte talks to me and I don't want to fail in this "first contact" by 
> just not
> even understanding the first sentence ;-)
> 
> Well i guess i know what a media error is, but please can anybody tell me
> what fenomenon is described by  "Write append position error".

Only from googling:

        E6076 - Write append error

        Problem
        If a WRITE or WRITE FILEMARKS command fails because the append
        point was unreadable, this error occurs.

Another google hits said this occurs when a write is attempted at EOT.
And one said some "platforms" gave this error when a write was attempted
in the middle of an existing tape file rather than at its end.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)