[Info-vax] Odd BACKUP error: unsupported file structure !

[John Wallace]

On Nov 11, 9:56 am, JF Mezei <jfmezei.spam... at vaxination.ca> wrote:
> Turns out that the /NOIMAGE backup just appeared to be faster because I
> kept the source to just the device name so it only copied files in the
> current directory of that device.
>
> Have now begun a /IMAGE again. Now it is telling me about 8 hours to
> completion instead of 12 to 15 before. I have opened the window to cool
> that room down as much as possible. I was thinking of perhps sutting it
> down for a few hours to let it cool. But am affraid the disk might not
> start up again.
>
> That message about invalid file struture level appears once so far, but
> on a different file and did not appear for the files that generated it
> the last time around. That is scary.
>
> Do I have any assurance that Backup will get the right data off the disk ?

If you want the data off the disk and you have lost confidence in
either the disk hardware or the file structure it contains, have you
considered doing a block for block copy to something else (a container
file or a whole other drive) using your favourite block-by-block copy
tool (BACKUP /PHYSICAL? Maybe something other than BACKUP if you're
worrying about BACKUP doing the right thing quickly enough?)

OK this will copy empty space as well as occupied space but if you're
really worried about filesystem integrity that may be a GOOD thing to
do (there may be useful recoverable data in that "empty" space).

Before taking this backup I'd also want to check the error log, check
that IDE cables were properly seated, and perhaps even replace the IDE
cable in question with a "known good" one from elsewhere.

Then you hopefully have a safe (ish) copy of the data to work on.

Have fun.