Hello Mark, On Tue, 2010-04-20 at 09:45 +0100, Mark Adams wrote: > Hi Paul, > > > On Mon, Apr 19, 2010 at 04:39:06PM -0700, Paul Yeatman wrote: > > Mark, > > > > On Mon, 2010-04-19 at 20:42 +0100, Mark Adams wrote: > > > Hi Paul, this is my issue, it doesn't appear to show any previous > > > errors > > > > I see! > > > > > The only thing before the message is tar saying it is skipping > > > to the next header, which I've assumed is tar moving to the chunk on > > > the next tape. > > > > Yes, I'm guessing that there is some failure to read the data on the > > next tape and tar is left with nothing to read and fails. > > > > > > > > Is there a way to run amrecover in 'debug' mode? > > > > Not that I am aware of. > > > > I think I would begin carefully reading the second tape (with the tape > > write-locked :) to see if I can successfully read back at least the > > first file or so. If so, I would also check that file's Amanda header. > > How can I tell what file will be on the start of the 2nd tape?
You can run amadmin with the find option. This will show which parts of the backup are on which tapes. Reading the 32k block at the beginning of each tape file should agree with this information. > > > > > If you are fortunate enough to have 2T of free disk space, I would also > > give using amfetchdump a try to first read back the full image to disk > > before sending it to tar. In absence of a free 2T, you could use the -p > > option to pipe it to tar but may be only right back at the same spot. > > > > There does seem to be some issue with continuing the read on the second > > tape. Regards, Paul
