Storage Enclosure not responding

[Anders Blomkvist]

I have a ProLiant DL380 with a Smart Array 4200 controller to which Im trying to connect a Storage enclosure. But regardless of what bus on the controller I connect the enclosure to I get the following error at boot:
1775-Slot 2 Drive Array ProLiant Storage Enclosure Not Responding
Both server and controller have the latest firmware and I've tried both connectors on the enclosure without success. I've also removed all disks from the enclosure but no go. Im running out of troubleshooting options here - anyone have an idea what it could be?

[Orion Quest]

POST 1775 and 1777 errors can be the result of a number of problems, including loose cables, bent cable pins, misattached cables, out-of-date array firmware, improperly seated boards, uninstalled or misinstalled system side cover, unseated or uninstalled fan jumpers.

[Anders Blomkvist]

Ok, all the status LED are OK - no problems shown. The 4200 controller seems to be working fine and the diagnostics does not report any errors there either. The only thing left seems to be the cable and I have requested a new cable to be sent to me so hopefully that will solve the problem.

[Charles_63]

I had the exact same problem with a StorageWorks 4300 with the exact same post error message. I tried changing cables, making sure all connections were tight. The problem ended up been a bad backplane in the Disk Farm. Hope this helps

[diekiller]

Today we had the same error with a smart array 3200 in a proliant 5500.

1775- Slot 7 Drive Array Proliant Storage Enclosure not responding
SCSI port 1: Check Storage enclosure power switch and cables.

The hard drives still had power, cause the lights litt up on boot.
But during the search for the logical drive the lights of all drives litt up just a fraction of a second...normally they are initialized one by one.

The engineer first replaced the controller (also switching the accellerator to prevent data loss) but that didn't resolve the problem. The integrated management log also indicated that there was a problem with de the drive cage... So he opened it and checked the power supply & scsi cable , they were connected. So the cage was seated again without changes. But after this the server booted normaly. So the drive cage cables were examined again closly this time. It turned out that the scsi cable was damaged (visibly in our case).

The damage was probably due to the replacement of a internal tape unit a few days before. For this the drive cage als had to be removed damaging the cable. Only at that time the damaged scsi cable didn't give a problem.