Name: mbroga Date: January 4, 2005 at 09:42:25 Pacific Subject: boot problems OS: VAXserrver 3600 CPU/Ram: not known
Comment:
Hi,
We are using an old Vaxserver 3600. We had a power failure and the battery backup ran down. I cannot boot as dia0 (system disk) is not available. The power up boot sequence gets to 3... and fails with the statement "Normal operation not possible".
I can get a partial boot off another disk but I get the following messages:
% PIA0, DSSI terminator power failure possible blown fuse % PIA0, Port is going offline
Anyone have any ideas? I cannot find any fuses anywhere.
Additional information. The system is in one box. There are 7 hard drives. Five in a separate bay and I can see all of those. These are on disk controller 0. If I run "sho dev" at the ">>>" promt disk controller 1 is not shown. It should have 2 disks and a TK70 tape drive.
As far as I can tell all of the terminators are in place.
Ok, for starters, I am a bit suspicious about power. You say that you have two cabinets. Can you verify that the second cabinet powered up?
Also, is anything else amiss. Sudden power downs are always a potential for hardware problems. Digital engineered things very well, but I have seen some strange problems creep in.
At one client last year, a machine (in this case a MV 3400) developed a flakey power supply after essentially a decade of reliable operation. In this case, it manifested as a series of unexpected Machine Checks.
What does the console show when you display devices?
The reason I ask is that I used to work in the VMS Support Team at Digital/Compaq/HP. Even though I worked with SW-support, our databases were helpful when searching for HW-errormessages.
Can't do any searches anymore.....just try and error/success
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE