Six weeks worth of data lost on RAID 1

Forums › Desktop computing › Six weeks worth of data lost on RAID 1

Tricksdrummer

25 posts

Geek

#68447 22-Sep-2010 09:18

Greetings!

I have an unsual problem, well more than one but this is my main problem currently.

I have 2 SATA Seagate Barracuda 7200.10 250GB drives in RAID 1.
On friday (yes Friday, the day that everything goes wrong) the pc restarted(due to windows update im told) and came up with a RAID error and wanted to "rebuild". After that not working i unplugged 1 of the drives and after bringing up a RAID error it booted fine, BUT any files that were modified after sometime mid July are simply not there, and running a "un-delete" program doesn't find anything either.
If i try booting off the other drive by itself it wont boot at all, just brings up a RAID error and wont continue.

"As we speak" i'm performing a good ole winxp error check (CHKDSK?) on the drive via a USB external drive enclosure, and it's chugging along half way through "phase 4".

Anybody heard of anything like this before?
Any ideas?

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#383036 22-Sep-2010 09:34

When was the last restart? Back in mid July? Perhaps the controller had a fault since then and you only found out during the reboot.

Now, might not help at all, but it's a valid reminder that RAID *is not* a backup.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Damo-K

67 posts

Master Geek

#383047 22-Sep-2010 09:52

I'm not familiar with windows raid but generally speaking, it is possible one of the disks was marked as bad (for whatever reason), dropped out of the pool and remained out of sync. In the meantime all your new files may be on the other drive(s).

Which drive are you disk-checking now? What did the raid error say exactly? Have you checked the contents of the other drive to see whether the newer files are there?

If the drive comes back clean, an often overlooked factor for a drive being falsely marked as bad is certain drives don't play nice in a RAID (I'm thinking specifically of the WD10EADS but there are others) - what brand/model of drives are you using?