krowitz@RICHTER.MIT.EDU (David Krowitz) (01/04/89)
I've got a problem with a new DN3500 with the 690MB disk ... if I shut down the node, I can't salvage the disk. If I boot the machine diskless off of another node, I can bring up AEGIS and then run SALVOL, but the stand-alone version of SALVOL just hangs (whether the machine is booted off of its own disk or it's booted diskless). If I boot the machine off of another node, I am able to run the winchester disk diagnostic under DEX (using the default settings) with no problems. If I try to run DEX off of the DN3500's disk, the winchester diagnostic will not execute (I get a message about a bad PV label (?)), but the other diagnostics (CPU, FPU, MEM, RING) all seem to run OK. If I bring the machine up as a diskless machine, salvage the disk, shut it down again, and boot it off of it's own disk it seems to be fine. I get no disk errors, I can run SAX -CIT, I can do a backup -- no problems -- but if I then shut the machine down again and try running salvol, it hangs again. I've checked the SR9.7 and SR9.7.1 release notes, and I don't see anything about bugs in either salvol or the winchester diagnostics for DEX. I've called this in as a possible hardware problem, but I'm not really certain that there is anything wrong with the disk. Does anyone have any knowledge of problems with salvol/DEX and the 690MB disks? -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter@eddie.mit.edu krowitz%richter@athena.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)
ferguson@garnet.bucknell.EDU ("Scott R. Ferguson") (01/04/89)
How about trying this:
Boot the node diskless, and mount the volume:
$ mtvol w /disk
Next, copy the salvol from another sau7 directory:
$ cpf /sau7/salvol /disk/sau7/salvol -r
I was thinking maybe your "salvol" file is corrupted, and simply
replacing it might do the trick.
When you're done, remember to dismount the volume:
$ dmtvol w /disk
Good Luck.
Scott Fergusonkrowitz@RICHTER.MIT.EDU (David Krowitz) (01/04/89)
I found the problem ... It turns out that the stand-alone (SAU) version of SALVOL does not correctly handle the new 690MB disk under SR9.7.1 The on-line version of SALVOL does, though, so what you have to do is to boot the machine diskless off of another SR9.7.1 disk, bring up AEGIS, run SALVOL, shut the machine down again, and then boot it off of its own disk. This is not mentioned in the release notes for SR9.7.1. SR10.0 will, I'm told, handle the new large disks correctly. -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter@eddie.mit.edu krowitz%richter@athena.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)