• 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.

Corrupt WindowsXP, Destroyed RAID.

T

ThrawnFile

Weaksauce
Joined
Feb 7, 2005
Messages
70
Well, I've tried damn near everything I can think of to retrieve data from a pair of 74gb raptors in RAID 0, sadly though I can SEE the files, and "save" them to an external drive, none of the files are readable. MP3s don't play, Photos cannot be opened, Text documents are blank. The file system says that they take up space, as in megabyes, but there is no information contained. Is there something that I am missing, or a service that I can employ to save this data?

Summary of what I have attempted.

Used a boot cd (BartPE) with runtime software's get data back software. The program sees everthing and I saved my data to a 37gb usb drive. If I need to load RAID drivers for this to work correctly, then I am at a loss there as well. Each time I try to install them I get a "NVRAID.SYS" missing and it aborts bootup.

Would a data recovery company even be able to save this?
 
A pro data recovery company would probably be able to analyze the magnetic history of the disks and determine when the corruption occurred, but you are looking at $1000+. You may want to get a no obligation quote from Seagate DRS and see what your prosepcts are. This corruption is pretty severe, do you have any idea what caused it for the benefit of others? A review of [thread=761272]Corruption 101[/thread] will help you get started in identifying the source of the corruption.

Try booting to a PATA drive and using the RAID array as a data volume and see if you can get a read on it in Windows, if this is avaialbale to you.

This is just another example on the value of backups, and once again, RAID-1 would have fared no better than RAID-0 in this situation. His drives didn't fail, yet he is still experiencing data loss. Take heed folks, don't let this happen to you. I have stuck the backup poll for a reason. I will gladly help when I can with data recovery when something like this happens, but I shouldn't have to. You should simply have to replace/rebuild and restore from backup.

Once again, please no RAID-0 bashing, as it is a non-factor in this situation, beyond added driver complexity - DL
 
File Scavenger supposably can handle this...though its worked everytime for me...I've never
had to try to rescue data from a raid 0 array.
 
couple of Q's off the bat:

1. can you be a bit more verbose about what happend?
2. you have the nvraid drivers intergrated into your BartPE, don't you?
 
Well if memory serves, I downloaded some stupid game (mojomaster, an AXE promo). About halfway through play, or maybe because as I installed it spybot snd popped up with a registry change confirm that I hit accept (and to remember this action, it clicked as I ok'ed) it froze. System reboot, everything is good till windows explorer loads. I get a message that lass has been updated and there is a file mismatch. Or something to that degree. Hit ok, reboot. Hit ok, reboot, ect. I finally try safe mode, same thing. I try safe mode with command promt. Same thing. I try debug mode (prolly my biggest mistake) and now it hangs on boot, saying some sysfile is gone.

I boot from OEM install cd, cannot recognize f: (c: drive). I go to the trouble of making a BartPE boot CD with runtime software's GetDataBack NTFS and Raid Reconstructor on it (too bad I can't image the drive(s) as I don't have a spare 150gb drive laying around.) no nVraid drivers, or nVchipset drivers integrated (dont know how) so I can't network. Though both pieces of software mentioned above see the dives individually and as one...?

I was reading through the helpfile for GDB ntfs, sometimes if you select the wrong partition in the recovery process it will allow you to save the files (in original size and format) but they are only fragments. And since I'm dealing with two drives this is damn hard to troubleshoot. So now I'm currently running another scan on the logical part of the drive(s) and it is hanging on some cycle errors, It may take days for this scan to complete... But if it works and saves me cash I'll leave it as long as possible.

Memtest showed no errors, and my system idenifies all hard drives. No clicking or whirring.

Shuttle SN25P, BIOS Y
AMD Athlon 4000+ stock speed
1gb OCZ platinum memory (2-2-2-5)
2x WD 74gb raptors RAID 0
Plextor SATA DVD burner.
GeForce 6800GT stock speed.
 
Update: I managed to image the dives (without RAID drivers in BartPE) and GDB still gives me corrupt files. When I ran the recovery program it reported 4 differient partitions (3x145gb and one 74gb). Doesn't matter which part. I run through the scanner. It seems that my un-trained efforts are unable to bear fruit, well fruit that isn't rotten.

I called Seagate and they quoted 1000-2000 for the de-striping process. I suppose that if I really want my data back, I'm gonna have to forgo an upgrade to my ram-video for awhile. Does anyone know if they garuntee that the data they recover is readable, cause I'll be damned if I'm going to pay that much for the same result that I recieved.

RAID 0 is cool, but only if you know what the hell you are doing. Since I didn't, I'm sure that the configuration is fubar somehow.
 
Not even RAID-1 or RAID-5 would have prevented this disaster. Once again, RAID does not protect against corruption, viruses, operating system problems, user errors, or any hardware problems not related to the physical disks. A handful of DVDs or tapes would have made recovering from this disaster a snap, A second physical disk in the system with an indendent file system may have saved the day as well.

I apologize in advance to the OP, and I am not specifically making fun of him or his situation, just using this as an opportunity to make a point. We love to bash RAID-0 because it's not "reliable," yet the most recent occurences of data loss on RAID-0 arrays that have been posted here have not been the fault of the disks! Instead, we have the increased system complexity biting us and making disaster recovery difficult. Once again, this ncreased complexity is a weakness of all RAID levels.

I've said it before, and I'll say it again. RAID is an uptime tool, not a backup tool. It does not protect data from disaster. It does not protect data from your own error. It does not protect data from your operating system or a program munching it. RAID does not protect data. Period. Backups protect data. The backup poll has been stuck for a reason.
 
You must log in or register to reply here.
Back
Top