From: johnb@HOBBES.MDC.COM (John Breen)
Newsgroups: comp.sys.apollo
Subject: HELP - DSP90 storage module won't salvol
Date: 6 Oct 92 14:28:36 GMT
Distribution: world
Organization: McDonnell Douglas Missile Systems Company

We have a DSP90, sr10.3, with two 500MB storage modules.  Ever since a power
outage yesterday, I've been unable to salvol the second disk.  A typical
transcript follows:
----------------
    $ salvol
    
    
    Salvol, revision 10.3, June 18, 1990  12:56:18 pm
    
    
    
    Select disk: [w=Winch|s=Storage mod|f=Floppy|q=Quit][ctrl#:][unit#] s1
    
    Salvol options:
         -a : read all blocks in all files
         -f : fix disk errors without prompting
         -n : only salvage if disk needs it
         -s : print statistics at the end of salvage
         -p : polite mode, pause before overflowing screen
         -v : verify only (don't write anything to disk)
    Please input lv_num (1)[-option]... : -a
    
        Preparing file list...
    
        Salvaging...  % complete
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
    Reading blocks in large files now, this part may take a while...
        (chk_hdr) page should be: 128 but is: 127
        (chk_hdr) daddr should be: 67C23 but is: 67C1F
        (chk_hdr) page should be: 25A but is: 259
        (chk_hdr) daddr should be: 680BF but is: 680BA
        (chk_hdr) page should be: 29A but is: 299
        (chk_hdr) daddr should be: 680C0 but is: 680BB
        (chk_hdr) page should be: 29A but is: 29F
        (chk_hdr) daddr should be: 680C0 but is: 680DA
        (chk_hdr) page should be: 433 but is: 432
        (chk_hdr) daddr should be: 6A7FC but is: 6A7F7
        (chk_hdr) page should be: 433 but is: 43F
        (chk_hdr) daddr should be: 6A7FC but is: 6A837
            20
    Reading blocks in large files now, this part may take a while...
        (chk_hdr) page should be: 85 but is: 84
        (chk_hdr) daddr should be: 6577B but is: 65776
        (chk_hdr) page should be: 85 but is: 8F
        (chk_hdr) daddr should be: 6577B but is: 657AC
    ?(sh) "/com/salvol" - access violation (OS/fault handler)
---------------

After a number of attempts I was able to get it to finish the first stage (ie,
"100" as the percent complete), but then it would ask me about various header
errors, and whether they shoul be fixed (which I answered "y").  After the
second attempt at this, salvol crashed with a disk block header error,
apparently on the *first* disk.  Since then, I haven't been able to get past
40%.

Am I sunk?  Why does salvol keep getting access violations?  Would running, say,
an sr10.4 salvol help, or would it completely corrupt the disk (I tried a 10.3.5
salvol - no difference)?

If I mounted it unsalvaged as a last resort, would I be able to at least see the
dates of files? (I think our backups are up to date, but I'd like to double
check).  Would mounting it read-only (unsalvaged) give me any protection?

Any help appreciated.
-- 
John A. Breen                           |  johnb@hobbes.mdc.com
McDonnell Douglas Missile Systems Co.   | "I have no personal opinions;
Tel: (314)234-4341                      |  I'm a product of my environment."
Newsgroups: comp.sys.apollo