I have a client that had been having random shutdowns for the past few months. I was able to stop the shutdowns by improving ventilation in the server closet (I suspected a heat problem). This seemed to calm everything down as the server ran fine for about 8 weeks. I recommended to the client that they should replace the hard drive as soon as possible.

In the last few days the shutdowns started again. Below are two copies of the screen after problems occur. The first one is typical of what is always seen until today after a reboot. The second is the message they now get. I'm guessing the hard drive is failing. Any guidance/input would be appreciated. Thanks.

--------------------------------------------------------------------------
7-26-2013 3:55:40 pm: COMN-3.27-1092 [nmID=A0025]
NSS-3.00-5001: Pool FSA/VOL3 is being deactivated.
An I/O error (10(zlssMSAP.c[1796])) at block )(file block 0)(ZID 0) has
compromised pool integrity.

7-26-2013 3:55:40 pm: COMN-3.27-1092 [nmID=A0025]
NSS-3.00-5001: Pool FSA/VOL2 is being deactivated.
An I/O error (10(zlssMSAP.c[1796])) at block )(file block 0)(ZID 0) has
compromised pool integrity.

7-26-2013 3:55:40 pm: DS-20217.6-266
Bindery close requested by the SERVER

7-26-2013 3:55:40 pm: DS-20217.6-263
Directory Services: Local database has been closed.

7-26-2013 3:56:03 pm: SERVER-5.70-1534 [nmID=B0013]
Device "[V026-A0-D0:0] ST31000340AS f:/w:SD15" deactivated by driver due to
device failure.

-----------------------------------------------------------------------

System halted Thursday, August 1, 2013 9:07:11 am <NO TIME ZONE>

Abend on P01: SERVER-5.70-1937: CPU Hog Detected by Timer
OS version: Novell NetWare 5.70.08 October 3, 2008

...Debug symbols are enabled!
Running Process: Interrupt service routine (nested count 1)
Interrupt process: Processor 1 IDLE Process
Stack: A3 7B F1 FB 9A C8 06 87 00 D9 D5 72 A0 90 AD 72
57 1C C2 7C 01 00 00 00 01 00 00 00 FF FF FF FF
01 00 00 00 00 D8 D5 72 00 00 00 00 00 00 00 00

Additional Information:
The NetWare OS detected a problem with the system while executing a process
owned by SERVER.NLM. It may be the source of the problem or there may have
been a memory corruption.

---------------------------------------------------------------------