ItsChad
asked on
Raid Controller Failed. Now disks lost config
Greetings,
I have a server where the raid controller died. I was out and had a technician who decided to fix it. Anyways, he put the new card in and called me and said the drive says unconf bad. I told him to set it to unconf good and he should be able to rebuild. Apparently all the drives said bad....
Anyways, where I sit now is that my Array is Offline. When I go into the Intel Raid Bios it says that I need to replace missing PD. When I look at the DG Missing row, I have all the available rows listed to choose from. How do I know what drive goes to what place in the array?
Is there a way to find this?
What can I do to get my data back? I have a backup but its a week old.
I appreciate your help.
I have a server where the raid controller died. I was out and had a technician who decided to fix it. Anyways, he put the new card in and called me and said the drive says unconf bad. I told him to set it to unconf good and he should be able to rebuild. Apparently all the drives said bad....
Anyways, where I sit now is that my Array is Offline. When I go into the Intel Raid Bios it says that I need to replace missing PD. When I look at the DG Missing row, I have all the available rows listed to choose from. How do I know what drive goes to what place in the array?
Is there a way to find this?
What can I do to get my data back? I have a backup but its a week old.
I appreciate your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"2. Don't use any software raid recovery tool. they only work on software raid and specific OS."
This is so very, very, wrong.
I've recovered data on just about any operating system, file system, and RAID controller you can possibly imagine on software RAID recovery tools. So has just about every other professional. Now your statement would be correct if we were discussing recovering file systems. But finding the boundary of metadata, and determining the layout is pretty much the same, regardless of windows, linux, unix. The only mainstream exception is ZFS.
Also "software raid recovery tool"? What other kind of raid recovery tool is there, unless you are discussing a custom ASIC. Even
This is so very, very, wrong.
I've recovered data on just about any operating system, file system, and RAID controller you can possibly imagine on software RAID recovery tools. So has just about every other professional. Now your statement would be correct if we were discussing recovering file systems. But finding the boundary of metadata, and determining the layout is pretty much the same, regardless of windows, linux, unix. The only mainstream exception is ZFS.
Also "software raid recovery tool"? What other kind of raid recovery tool is there, unless you are discussing a custom ASIC. Even
points should be split between #35501692 and #35508493. Either product can be used to reconstruct the RAID.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
2. Don't use any software raid recovery tool. they only work on software raid and specific OS.