• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Areca 1880 Raid 6 Rebuild - Data lost?

B

Bigzaj

Weaksauce
Joined
Aug 18, 2010
Messages
96
I recently upgraded my motherboard and ended up putting my Raid 6 array on a HP SAS Expander. Long story short the SAS Expander turned out to be bad, but I would like to walk through the sequence of events to see if I am hosed or not:

Areca 1880i - 8x2TB Raid 6 array:
(1) - Drive "failed"
(2) - Replaced drive and initiated rebuild
(3) - Rebuild failed at 16%
(4) - Replaced drive again and initiated rebuild
(5) - Rebuild failed at 7%
(6) - Proceeded with RESCUE, reboot, SIGNAT
(7) - Proceeded with LeVeL2ReScUe, reboot, SIGNAT
(8) - Upon reboot Windows attempted to run checkdisk on the drive, made it 80% of "reindexing" files and then failed
(9) - Finally pulled HP SAS Expander out, now in rebuild about 11 hours in and at 10% with no errors

The issue is now Windows says the drive needs to be formatted before it can be used. Previously it would let me access the data. Is the data lost or does the array need to rebuild and initialize for windows to see the drive and data properly? I really want to recover this data and I am hoping that it is still on the drives (only ever replaced 2 drives so the data should be intact somewhere). Any advice on how to proceed once the rebuild finishes to attempt to recover the data?
 
I think things are hosed. If the array ever went to a failed/offline state then when recovering it you really need to be careful on which disk it used by the order in which it failed. If it craped out during an fsck that is a good way to seriously *fuxor* the file-system


I would give a linux distro a try to see if the drive can e mounted (in read-only) for accessing your data to see if you can get stuff off. I have been able to mount something from linux before when windows just prompted me to format it but a lot of the data wasn't accessible.

The full event history from the areca controller would be helpful to get a better idea of what went on. It could have recovered with the wrong disk and you might have been ok had the fsck not happened. Inconsistent raid state fsck's are known to really hose file-systems as I have seen it a lot before on machines @ work.
 
You must log in or register to reply here.
Back
Top