Having a problem with a failed drive in a server I have at a remote site. Here is what I have so far. We have a server with 16 HD bays in it, in those bays we have 2 146GB 10K sas drives configured in a Raid 1 setup as a Logical Drive (ARRAY A), we have 14 500GB 7200K drives setup in a Raid 5 config as Logical Drive B (Array B). A few weeks ago we started having a error that we had a drive that has failed. At this remote site we have a low level tech who attempted to diagnose the issue he was having and once of his methods was to reboot the server (I know, not a good idea with a degraded array). The server started back up with the Array B being in Interim Recovery Mode. We ordered a new replacement drive (same part # as the failed drive) and sent it to the site. Gave instructions to tech to, while powered up, pull the bad drive and replace it with the new drive. In my expierence, the rebuidl process should have began immediatley. This did not happen. When I get into the server and look into the ACU GUI this is what I see.
Smart ARRAY p410i in Embedded Slot
Unassigned Drives (1)
500GB Sata Drive at Port 5C Box 2 Bay 8 (This is the replacement drive) in same slot as old failed drive
SAS Array A - 1 Logical Drives
Logical Drive 1 (136.7 GBm RAID 1)
SATA Array B - 1 Logical Drive
(Interim Recovery) Logical Drive 2 (5.9 TB, Raid 5)
What is weird though is that when I look at the Physical View it is still showing the New Drive in PORT 5C:2:8
But it is also showing the old failed drive for that Array in Question at BOX 1: BAY 0
This location does not even exist. It almost looks like to me that the Controller is not realixing that old failed drive is missing.
I have scoured the fourms and google and have not found any help, this is my last resort before wiping the array out and restoring the data on that array from a backup.