Hello-
I'm running an old ML350 G4 server with Windows SBS 2003 and a Smart Array 641 controller on firmware 2.34 B (I know that there is newer firmware but until just recently I've had no problems). I've experienced the following sequence of events twice now in the past month:
Event Log
--------------
19:26 - The device, \Device\Scsi\cpqcissm1, did not respond within the timeout period.
19:27 - Drive Array Physical Drive Status Change. The physical drive in Slot 3, SCSI Port 1 Drive 5 with serial number "XXX", has a new status of 3.
19:27 - Physical Drive on DEVICE ID 5 on Port 1 of Array Controller in slot 3 has failed. Failure Code: 0x07
19:45 - Environment Abnormality Auto Shutdown (EAAS) initiated due to thermal reasons, either resulting from the system overheating, or from the loss of cooling.
Smart Array Log
----------------------
19:27:13 - SCSI bus fault occurred on Storage Box box 0, , Port 0 of Array Controller in slot 3. This may result in a "downshift" in transfer rate for one or more hard drives on the bus.
19:27:13 - Physical Drive on DEVICE ID 5 on Port 1 of Array Controller in slot 3 has failed. Failure Code: 0x07.
19:27:13 - Logical Drive 2 of Array Controller in slot 3 has changed from status code 0 to status code 3.
20:07:59 - The Event Notification driver Cpqcisse.sys of Array Controller in slot 3 has started.
20:08:29 - Logical Drive 2 of Array Controller in slot 3 has changed from status code 3 to status code 4.
20:08:29 - Logical Drive 2 of Array Controller in slot 3 has changed from status code 4 to status code 5.
21:25:00 - Logical Drive 2 of Array Controller in slot 3 has changed from status code 5 to status code 0.
As indicated by the 19:45 event, the server overheats and then restarts. It's worth noting that this does happen once in a while, but it always accompanies this drive failure. After it automatically restarts it restores that failed drive and everything is fine.
It's also worth noting that I get the cpqcissm1 event ("The device, \Device\Scsi\cpqcissm1, did not respond within the timeout period.") maybe once or twice a week.
Now, for a little history:
At the beginning of this year one of my hard drives truly did fail and I replaced it with a "new" one (I say that because it was used but new to the server). That fixed the failed drive, obviously, but ever since that point the cpqcissm1 events began appearing. This may be coincidence and not consequence, but it could also be indicative of a bigger problem--a problem that these recent events are revealing. (Also, the original failed drive is not the same one as the one from the recent events).
I'm more of a server administrator by necessity than by education, so I've come here for your advice: what do you think is going on? I'm pretty sure that there's a hardware issue, but judging from these events I don't know whether it's a hard drive, the SCSI controller or the Smart Array controller (or perhaps something else entirely).
If it helps, I'll give a quick rundown of the RAID setup:
Logical Drive 1: 3x 72.8 GB, all on firmware HPB3 (it was one of these drives that originally failed)
Logical Drive 2: 3x 146 GB, all on firmware HPB4 (it is one of these drives that fails in the recent events)
Thanks for any help you can provide.
EDIT: I'm looking into buying a replacement controller just in case but I'm coming across two different part numbers: 291966-B21 and 305414-001. Which one should I be getting?
