Thanks to all who replied.
Here is my original post:
-----------------------------8<--------------------------------------------
A couple of weeks ago, we had to shut down our servers for electrical
maitenance in the office, we unplugged the servers from the outlet just to
be sure that the electricians would not fry them.
When the job was done, we restarted the servers. One of the disks
(containing a swap partition and an advfs file domain) did not restart
correctly. The amber light was lit and the kernel would just not boot. We
power cycled the servers and everything ran just fine.
The drive seems to run well since that time. Has anyone ever seen
something like this before ? Should I trust that disk or replace it ?
Thanks !
--------------------------------------------8<--------------------------
Answers:
A few people told me to not worry about it. Many have seen the same kind of
behavior.
Other people told me to check with DEC if there is not a problem with disk
firmware and/or HSZ40 firmware. We've ordered the new HSZ software and are
still waiting for it (6-8 weeks ago)
Some people replaced the drive. On this last subject, if anyone can help me
with the following, I'll be glad:
That drive contains SWAP + Part of an advfs filedomain (That we added with
addvol). The machine refused to complete the boot process, it hanged when
it was time to mount this filedomain. We waited 2-3 minutes before
power-cycling the server. I wonder what happened if the disk would have
been physically damaged. Can someone explain me what happens and should be
done when:
a) A disk containing ONLY swap space breaks. How do I prevent swapping to
occur on the failed disk ?
b) A disk containing other data breaks (Boot to single user and remove the
file domain before restoring from tape ?)
Thanks
Received on Thu Jan 09 1997 - 02:15:31 NZDT