RAID 5 - unique situation and question
Posted on 2013-12-07
Hey guys.. time is critical on this one.. any help appreciated.
Without too much explanation, here's what I have:
Dell Perc Raid Controller. 2 drives from a RAID 5 array that are perfectly intact....
The second drive (drive 3 is totally toast) was imaged from the original drive sector by sector with no errors, so it's an exact copy.
In theory, I should be able to use those 2 drives - and I have already been able to do so, but only in a limited fashion - the software I have to rebuild the array only lets me save files, or make an image file, but will not let me clone the array directly onto another drive for booting purposes. The problem is that image creation takes about 14 hours. I just finished a 14 hour stretch and after that was done, the destination disk that contained the image went belly up on me (it was a 3 TB drive). We're talking about a large amount of data, so imaging and reimaging is just too time consuming and this server needs to be up by Monday morning!
I wanted to put the good drives back into the server, but the problem is that the RAID controller sees the perfectly good copy of the failed drive as a drive that doesn't belong to the array. It's a different model and serial number drive than the original, and my guess is that the raid config is sensitive to this.
IS THERE ANY WAY... to trick the raid controller into using this newly copied raid member and allow me to boot this server and perform a backup? Hex editor on the drive to fix a serial number problem possible?
Please don't suggest I image it again. I don't have that many hours left to do that. Suggestions are welcome but please hurry!