9 Feb
2014
9 Feb
'14
8:56 p.m.
was also able to boot the VMS I read off of the RD53.
Its running MicroVMS Version V4.6 and has 12M of memory.
I didn't get any disk errors and was able to copy a directory tree. I didn't
figure out how to do an equivalent of diff -r to check the tree copy.
Any simple tests under VMS to verify that writing is working fine? With the
other tests and validating that the image file is still valid after the
testing I think its working pretty good now.
$ BACKUP /COMPARE DISK:[FOO...] DISK:[BAR...]
will compare two directory trees. There is no output if everything compares
ok. Throw in /LOG to make it list each file compared for extra comfort.
$ BACKUP /IMAGE Real-disk: Emulated-Disk:
would do lots of writing and give you something to compare too.
It had a few errors on the first disk check that went away with repair.
These two just keep alternating though. Anyone know what this indicates?
$ analyze /disk/repair dua0:
%VERIFY-I-BACKLINK, incorrect directory back link [SYS0]SYSMAINT.DIR;1
$ analyze /disk/repair dua0:
%VERIFY-I-BACKLINK, incorrect directory back link [000000]SYSMAINT.DIR;1
No new errors have shown up.
Can you check on the real disk and see if they were there before you started?
If they turn up again,
$ DUMP /HEADER /BLOCK=COUNT=0 <filename>
might give some indication of what the problem is. This will list (amongst
other things) the FID of the directory the file lives in. This can be checked
with:
$ DIRECTORY /FILE_ID
Regards,
Peter Coghlan.