I have an older R900 with a Perc 6/i controller with six 500gb SAS (Seagate ST9500430SS) drives configured in a RAID 5 array. Recently Drive 0 failed so I replaced it with an identical drive. The replacement drive showed up and after I inserted it I got the E1810 Fault error on the LCD display so I assumed that it was also defective. I exchanged it with the seller and inserted a 2nd replacement. Same E1810 error. I booted into the controller utility and it showed that the drive is missing so I naturally assumed that I'm a victim of bad luck and received two faulty drives. The vendor sent me a 3rd drive and it also shows the E1810 Fault error.
I cut my losses with that vendor and assumed they were selling junk drives so I bought a brand new drive from another vendor. Popped the drive in, E1810 Fault error.
What is going on here? I have never seen this behavior before. Could the slot somehow be bad? If so, can I keep all of my data and move the disk from slot 0 to slot 7? I need to find a solution fast because the array is not configured with a hot spare. Another failed disk means all of my data is gone. Any suggestions other than wiping the config and starting over?
can I keep all of my data and move the disk from slot 0 to slot 7?
The drive does not have to be put into the same slot as the old drive. Yes, you can put the replacement drive in another slot.
Do I have to boot into the controller BIOS to assign it to the array?
A rebuild may start automatically when the drive is inserted. If a rebuild does not start automatically then you will need to assign it as a hot spare to initiate a rebuild.
I moved the drive from slot 0 to slot 6 and now i'm having big problems. it is now saying that the drive in slot 4 is faulty and now vSphere client isn't responding. Any thoughts?
I moved the drive from slot 0 to slot 6 and now i'm having big problems. it is now saying that the drive in slot 4 is faulty
It sounds like you had another drive failure before the rebuild completed. This is a data loss scenario. If you want to try to recover the virtual disk you should review the controller/TTY log. I wouldn't do anything until that log is reviewed.