error in RAID 0 array

Natima · 25 Jul 2009 at 18:44

Upon booting up my PC after playing with some CPU settings in the bios and suffering a BSOD, one of my HDD's showed an error.
But everything seems fine.
I'm a little scared to reboot now.
Anyone got a clue what this means?

Natima · 25 Jul 2009 at 18:56

rebooted... everything still seems fine.
Intel Serial ATA BIOS still showing RAID status as 'Normal' in green letters, and one drive as 'Error Occured (0)' in red letters.

Natima · 26 Jul 2009 at 02:38

Nobody? Do I need to start urgently backing up or what?

miniyazz · 26 Jul 2009 at 10:34

lol sounds fine

but urgently back up anyway, it's raid0!

Natima · 26 Jul 2009 at 11:06

Shall I just "mark as normal" in Intel Storage Matrix Utility and call it a day then?
I'll backup when I have the cash to buy an extra hard drive! :S

EDIT:
Check Disk Log:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
134400 file records processed. File verification completed.
235 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
177182 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
134400 file SDs/SIDs processed. Cleaning up 393 unused index entries from index $SII of file 0x9.
Cleaning up 393 unused index entries from index $SDH of file 0x9.
Cleaning up 393 unused security descriptors.
Security descriptor verification completed.
21392 data files processed. CHKDSK is verifying Usn Journal...
34375952 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000000e at offset 0x2aaf66c000 for 0x10000 bytes.
Read failure with status 0xc000000e at offset 0x2aaf679000 for 0x1000 bytes.
Windows replaced bad clusters in file 93355
of name \Users\Nat\Desktop\Data\Old HDD\STONEH~1\HOLDME~1.MP4.
134384 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
219327967 free clusters processed. Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

1250151423 KB total disk space.
372503460 KB in 112101 files.
63476 KB in 21393 indexes.
4 KB in bad sectors.
272611 KB in use by the system.
65536 KB occupied by the log file.
877311872 KB available on disk.

4096 bytes in each allocation unit.
312537855 total allocation units on disk.
219327968 allocation units available on disk.

Internal Info:
00 0d 02 00 81 09 02 00 5b be 03 00 00 00 00 00 ........[.......
35 05 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 5...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

SpiderX · 26 Jul 2009 at 11:36

that red dot does not look good. one of your drive may be dying...
i would back up what you can then do a disk diagnostic on each drive

Natima · 26 Jul 2009 at 11:54

Is there a way of shifting the RAID 0 over to one drive?
Unfortunatly my UD5 has issues with AHCI mode too... Need to RMA it.

This drive is only a few weeks old... if that.
Barely used. Never reformatted.

Natima · 27 Jul 2009 at 22:28

Anyone?

Do you guys think my drive is dying or what?
I'm not too scared - and I only got this error after a failed overclock.

DragonQ · 27 Jul 2009 at 22:35

We had a red error during the RAID boot screen on a PC at work in February (it was a RAID 0 array with two 10,000 RPM drives). About 2 weeks after it first appeared, the drive died. The same machine has the same error on a different drive now so we're expecting that to die any time soon as well. Considering this has happened on the same machine, we're thinking it might be the controller but in any case, I strongly suggest you backup your data.

Oh, and the error message you've quoted above looks the same as the one we got/get.