Hi Jon, So it looks like Amanda can't find the volume even though I know this volume did exist.
Here's the messages I received from 'amrecover': Volume labeled 'PCBI38L4' not found. Load tape PCBI38L4 now Continue [?/Y/n/d]? Y Not an amanda tape: Can't open tape device chg-zd-mtx: No such file or directory Load tape PCBI38L4 now Continue [?/Y/n/d]? Y Not an amanda tape: Can't open tape device chg-zd-mtx: No such file or directory Continue [?/Y/n/d]? d New device name [?]: ? Enter a new device name or "default" New device name [?]: default Using default tape from server cronos.pcbi.upenn.edu. Continue [?/Y/n/d]? Y Got no header and data from server, check in amidxtaped.*.debug and amandad.*.debug files on server I also see this in the log file (/var/log/amanda/server/Daily1/amidxtaped.20111124183504.debug): [...] 1322177849.880209: amidxtaped: changer: << 39 tape:/dev/nst0 1322177856.739641: amidxtaped: Device /dev/nst0 error = 'No tapestart header -- unlabeled device?' 1322177856.739710: amidxtaped: Device /dev/nst0 setting status flag(s): DEVICE_STATUS_VOLUME_UNLABELED amidxtaped: slot 39: Error reading tape label: amidxtaped: slot 39: No tapestart header -- unlabeled device? [...] Is it an indication that the label got corrupted on the tape in slot 39 (tape label 'AHE948L4', volume label 'PCBI38L4')? This tape was definitely labeled and used by the backup I need to do a restore from. Note that that this is the same tape I got a tar error. What is the correct way to restore the label on the tape (if it got corrupted) without losing the contents? Is there a way to retrieve the contents from a bad tape manually? Best, Valeriu On Thu, Nov 24, 2011 at 06:43:21PM -0500, Valeriu Mutu wrote: > Hi Jon, > > Thanks for the quick response and detailed clarification. > I re-ran the restore and will note if I see the error again. > Is it possible to find the cause of this error in the Amanda logs? > > Best, > Valeriu > > > Tar encounters, and reports, at least two categories of errors. Some will > > affect the entire dump and will cause an immediate exit with a status 1. > > Others typically affect the dump of one file only and tar will note the > > file but continue dumping. Thus a "delayed" exit results and a status > > of 2 indicates the dump was not normal but was not terminated early. > > > > Errors causing the delayed error exit include things like "file contents > > changed as it was being backed up" or "file was removed before it could > > be backed up". The reason for your specific report is probably found > > where you put the ellipsis. > > > > Jon > > -- > > Jon H. LaBadie [email protected] > > 11226 South Shore Rd. (703) 787-0688 (H) > > Reston, VA 20190 (609) 477-8330 (C) > > -- > Valeriu Mutu -- Valeriu Mutu Systems Administrator Penn Center for Bioinformatics 215-573-8119
