RAID5 Intel rapid storage failure - help please!

LxMxFxD4

Senior member
Oct 6, 2007
359
0
0
I have a 4 drive RAID5 array of 2TB hitachi drives using the onboard ICH10R onboard controller. A recent sequence of events has caused this to go into failure. This sequence is as follows.

I recently changed around video cards which caused my system bios to somehow restore default settings. The default settings is to boot to ACHI instead of RAID. As luck would have it I booted into windows in ACHI mode. I got a few "You must format disk E:\ to use it" (the raid array disk) and cancelled the notifications. Knowing what the issue was I rebooted, went into my bios and set storage to RAID.

Upon reboot the RAID array tells me "RAID FAILURE" but shows me all 4 disks. All 4 disks are showing up but 2 of the 4 are showing as RAID MEMBER and the other 2 are showing as NON-MEMBER DISK. Bad news.

I have my OS on an SSD which is also a non-member (of the raid) disk which is on this controller.

So i'm now in windows and Intel software is again telling me array failure. No bueno. It also shows me the same deal: 2 non-member, 2 member disks.

At this point im stressed. Under windows storage management, windows is seeing 2 basic disks the of 5.5GB (the size of my array) and 1 "UNFORMATTED" disk of 5.5GB. At this point I haven't done any SMART testing or anything, im just freaked and wanting to get this post out to ask if anyone knows how to proceed.

RAID5 allows for 1 disk failure but not 2. Again, everything was good and reading fine prior to the boot into windows in ACHI mode. But i'm sweatin it. I do backups of hte important stuff but they are monthly and there stuff on there going back 17 days :(

I don't even know what or how to evaluate these disks individually without breaking up the raid.

Any help appreciated!

EDIT: Just rebooted and S.M.A.R.T status is showing accessible and "OK" for all 4 disks. Is it possible that when I booted into windows in ACHI somehow windows formatted 2 of my 4 disks? Is there a way to find out?
 
Last edited:

Emulex

Diamond Member
Jan 28, 2001
9,759
1
71
you have a raid-5 hole :)

ichr9 on consumer drives ifs good for raid-0 only. raid-1 on a good day.
 

LxMxFxD4

Senior member
Oct 6, 2007
359
0
0
you have a raid-5 hole :)

ichr9 on consumer drives ifs good for raid-0 only. raid-1 on a good day.

I've been running it for 6 years, never had a problem until today! Are there any solutions that anyone can think of though?
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
you have a raid-5 hole :)

ichr9 on consumer drives ifs good for raid-0 only. raid-1 on a good day.

this is not the RAID5 hole. The RAID5 hole is a flaw in RAID536 design that causes silent data corruption and is why standard RAID536 shouldn't be ever used (use a non standard implementation like RAIDz which doesn't have that).

mobo integrated raid only gives good speed with RAID0 and RAID1, but it is unsafe with ANY RAID at all.

What he has is the issue where all mobo based RAID stupidly stores their settings in CMOS. So if CMOS is reset for any reason it will lose it and decided you have a bunch of degraded drives...

There is a way to restore it, but you must make no mistakes. Reboot and go into RAID setup menu in the RAID BIOS. In it you want to "delete array" on each of the 4 degraded drives. Then you are to create a new array.

YOU MUST!:
1. Add the drives in the same order they were originally added.
2. Set the exact same stripe size.
3. Say NO! when it asks you to initialize (I believe it calls it initialize, it might use some other term, but it will ask you) the array because if you say yes it WILL delete all data on it.

If you do that then it would have reconstructed the array without losing data.

After doing it for the 3rd or 4th time I broke up my mobo RAID and have never ever used mobo based RAID ever again. Because mobo RAID is utter crappy disaster that shouldn't be used.
That was my very first RAID too... years ago, RAID5.


hey, pretty cool tools if they work. It appears that they can automatically detect some of the data you must remember for the manual reconstruction.
 
Last edited: