Our team has been having issues drives on a DAE3P enclosure.  There were 15 drives in the enclosure, so it was full.  All were operating correctly.  The other day, one drive went down.  We assumed it had gone bad.  Luckily, all 15 drives were in a RAID5 config, so the raid group could survive a drive failure.  However, when we tried to replace the bad drive, all of our spares would enter the "Powering Up" status, then immediately go to the "Removed" faulted status.  This happened on 6 drives that we tried to replace it with.  We decided to try and test some of the drives, to see if we actually had that many bad drives.  During the testing process, one of the known good drives from the raid group was removed (we didn't mind losing the data in the raid group).  Later, after some testing that seemed to confirm that all 6 of our off-the-shelf spares were bad, when we tried to put the known good drive back in, it started to reporting "Removed" as well.

Since we couldn't get the enclosure to re-accept the drive, we removed all LUNs and destroyed the RAID group.  Navisphere now reports that there are 13 good drives in the enclosure, and 2 empty slots.  If we put in one of the drives (either the spares or the one that was known good before) it will do the "Powering Up" status, then drop to "Empty" status, even though there is a drive in the slot.

We have tried rebooting/power-cycling the SP and the enclosure with no success at the enclosure accepting the drives.

Any advice on what might be the issue here?  While it is possible that we did get a bad batch of drives, with that many bad drives, and also possible that the "known good" drive went bad during our testing, it still seems suspect.  We suspect there might some configuration issue that is preventing the enclosure from re-accepting these drives for some reason.