Sorry for this late post, but I was trying to deal with further disk
problems on my system.
Many thanks to the following for their continued contributions:
alan_at_nabeth.cxo.dec.com
Jeff.Beck_at_orcas.iasl.ca.boeing.com
sxkac_at_java.sois.alaska.edu
ggallen_at_slackinc.com
BYRD_at_mscf.med.upenn.edu
Jeff mentioned that on his system, he had to upgrade the firmware
of his disks (to version 442D) before they got working reliably.
Alan Nabeth suggested that any device on the bus could be causing the
problems I was seeing, even though all the uerf messages pointed to SCSI
BUS 0 and TARGET 0, which was the root disk. This led me to try some
things when the system acted up again. I found that when one of my
users attempted to access one external drive (also an IBM 0664), the
system would start hanging (disk access light comes on solid). I could
get the system out of the condition by power cycling the drive, only to
see it happen again. In the mean time, the error log is still blaming
BUS 0, TARGET 0, the boot disk.
So, I'm now replacing that external drive that flaked out. I noticed
that it and the cabinet it's mounted in were rther warm, indicating that
the 1" vent fan may not be up to the task of cooling the drive and power
supply.
So, my suspicion of insufficient cooling was right, but the problem was
not the AS 250 chassis, but may be this 3rd party low profile box.
Also, Alan suggested that sometime when UNIX systems crash, their clocks
can get wierd. I think my system got its year set back after the first
time I had to hard halt it with the front panel button when it hung up
the first time last Thursday.
thanks again for all the inputs.
eyc
Received on Wed Apr 16 1997 - 03:29:47 NZST