From: pchapin@ecet.vtc.edu
Date: Mon Sep 16 2002 - 18:27:01 EDT
Thanks to:
Tom Linden
John Galt
"Dr Thomas.Blinn@HP.com"
"Adametz, Bluejay"
Timothy Brown
Peter Sherwood
alan
Based on the results of testing I am forced to conclude that my disk is
dead, dead, dead. Several people pointed out the importance of not
jumping to conclusions about the disk when there might be other (nicer)
possibilities (for example the SCSI controller). However in my case, it
does appear to be, in fact, the disk. Alan's reply was particularly
good. I repeat it here:
-----> begin quote <-----
See if you can boot from the CDROM distribution and let
cycle through to the point that you can get the standalone
system. That will let you check with the problem is the
disk or something generally wrong with the system. If the
CDROM and system disk are on different busses, it also
checks the bus. With the standalone system booted, you
can use scu(8) to check the disk. A simple "tur" for
Test Unit Ready is a good first test. If the disk isn't
ready and a "start" doesn't get it ready, your problem is
the disk. Get a replacement and restore it from your
backup.
-----> begin quote <-----
In talking to one of the students here (we are a college) I also found
out that the power flickered several times last weekend and included
some "brown out" periods. Nasty. Quite a few machines across campus were
left in an unhappy state. I guess it's time to get a decent UPS for this
box! (Nothing like closing the barn doors after... well, you get the
idea).
My original question follows.
Peter
-----> cut here <-----
There was a short thunderstorm here this morning that involved lightning.
Now my Tru64 system (DS10) won't boot. I suspect hardware failure but I
could use a second opinion.
When powered up it flashes an amber light on the front panel a few times.
My console manual tells me that this means the operating system is trying
to "alert" me. The green disk activity light is not active to any
noticable degree.
The very first test to appear on the screen during the boot up is as
follows:
initializing GCT/FRU at 1ea000
Testing the System
Testing the Disks (read only)
dka0.0.0.14.0 has no media present or is disabled via the RUN/STOP switch
file open failed for dka0.0.0.14.0
The system then goes on to attempt to boot but it simply spews the message
"dka0.0.0.14.0 is not ready" over and over again.
Is there something I should try that might nurse this thing back to life?
This thing is running some moderately important services so getting it
back up in a timely manner is desirable.
Peter
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:53 EDT