HPE EVA Storage

4354r StorageWorks error. Connected to a DL580 G1

 
blindahl
Occasional Advisor

4354r StorageWorks error. Connected to a DL580 G1

Sensor 0 of internal storage device on Port 2 of
Array Controller in slot 4 is reporting the temperature has exceeded the preset limit.
The controller may attempt to shut down power to the storage device and/or spin down the installed disk drives.

Note: The StorageWorks has a "Enclosure Fault" amber LED on.
5 REPLIES 5
cnb
Honored Contributor

Re: 4354r StorageWorks error. Connected to a DL580 G1

Are you using ACU & ADU? Can you attach the ADU report? More information on your configuration would be helpful (controller model, f/w, o/s, etc...)

Check the fans and power supplies in the back of the enclosure. Are they working?


blindahl
Occasional Advisor

Re: 4354r StorageWorks error. Connected to a DL580 G1

Thanks for the quick response. I will check on the items you mentioned.

So far we are using Windows server 2000
and have a Smart Array Ctl 5304 connected to the StorageWorks 4354s by one I/O cable. There are 8 hard drives in the 4354r.

I will followup on the other questions.
blindahl
Occasional Advisor

Re: 4354r StorageWorks error. Connected to a DL580 G1

So I got the OK to run Smart Start 7.9 on server. 8.15 just stalled and would not load.
* Rebooted server with Smart Start but during POST it noted that hard drive ID #2 in StorageWorks was not responding. I went ahead and ran Smart Start anyway.
* Smart Start ran OK on all HDs except ID #2. It did not even see ID #2 and did not report any errors on server.
* I powered down server and replaced HD.
* Rebooted server and POST came through OK noting that ID #2 had to be rebuilt.
* Server came up OK without the StorageWorks "Fault" LED coming on.

It looks like the problem was the HD all the time. I closed the call.
Thanks again
cnb
Honored Contributor

Re: 4354r StorageWorks error. Connected to a DL580 G1

Rob Leadbeater
Honored Contributor

Re: 4354r StorageWorks error. Connected to a DL580 G1

Hi,

> It looks like the problem was the
> HD all the time

If you read the error message again, that's actually quite obvious...

Cheers,

Rob