EOF, check amidxtaped.debug
--- This text was originally contributed to the AMANDA-FAQ-O-Matic by [email protected]. ---
If amrecover fails with a message that includes:
EOF, check amidxtaped.debug file. amrecover: short block 0 bytes
You might need to rewind the tape. AMANDA uses the non-rewinding version of the tape device, so that you can append data after amdump/amflush.
amrecover DOES NOT REWIND THE TAPE FOR YOU, because it has no way of knowing what part of the tape you want to restore from. A simple
mt -f /dev/yourtapedevice rewind
before amrecover is a good idea.
sgw: A common trick is to run that command in a second shell while amrecover waits for you to start the extraction-process.
--- This text was originally contributed to the AMANDA-FAQ-O-Matic by [email protected]. ---
To solve my EOF troubles with amrecover, I found that specifying the tape device on the amrecover command line did the trick:
amrecover -C SANhomedirs -d /dev/nst0
If I do not specify the tape drive, everything seems to work OK until I attempt an extract, at which point I get the dreaded EOF.