Two disks dropping out of raid 10

minimort

Distinguished
Sep 29, 2010
1
0
18,510
Hello all, hope someone can help.

I'm newbish to Raid.. but managed to set up a Raid10 with 4x 1 TB Samsung F3's, on a Asus P6X58D Prem. Using Win 7 64 Pro. The Samsungs are new drives and the Raid10 have been working well for over a month. Everything going well until tonight when I got a little update from Windows which included updated drivers for Promise Technology AHCI compatible raid driver. After the obligatory system reboot, my Raid10 array is not accessible. It shows two of the disks as "missing" and I have two non-member disks. Tried system restore (twice) to older points thinking it may have been due to the "updated" drivers. (couldn't find a way to rollback drivers).

The two non-member drives check out fine (could find no errors) but I cannot seem to add them back to the array. I changed their status to "spare" within the intel utility thinking it would rebuild the volume on reboot. No luck. There were no option to rebuild the array on the ctrl-I utility. The intel matrix storage utility gave this report:

System Information

Kit Installed: 8.9.0.1023
Kit Install History: 8.9.0.1023, Uninstall
Shell Version: 8.9.0.1023

OS Name: Microsoft Windows 7 Professional
OS Version: 6.1.7600 Build 7600
System Name: BEN-SUPERPC
System Manufacturer: ASUSTeK Computer INC.
System Model: P6X58D PREMIUM
Processor: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
BIOS Version/Date: American Megatrends Inc. 1002 , 08/29/2010

Language: ENU



Intel(R) Matrix Storage Manager

Intel RAID Controller: Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller
Number of Serial ATA ports: 6

RAID Option ROM Version: 8.0.0.1038
Driver Version: 8.9.0.1023
RAID Plug-In Version: 8.9.0.1023
Language Resource Version of the RAID Plug-In: 8.9.0.1023
Create Volume Wizard Version: 8.9.0.1023
Language Resource Version of the Create Volume Wizard: 8.9.0.1023
Create Volume from Existing Hard Drive Wizard Version: 8.9.0.1023
Language Resource Version of the Create Volume from Existing Hard Drive Wizard: 8.9.0.1023
Modify Volume Wizard Version: 8.9.0.1023
Language Resource Version of the Modify Volume Wizard: 8.9.0.1023
Delete Volume Wizard Version: 8.9.0.1023
Language Resource Version of the Delete Volume Wizard: 8.9.0.1023
ISDI Library Version: 8.9.0.1023
Event Monitor User Notification Tool Version: 8.9.0.1023
Language Resource Version of the Event Monitor User Notification Tool: 8.9.0.1023
Event Monitor Version: 8.9.0.1023

Array_0000
Status: No active migrations
Hard Drive Data Cache Enabled: Yes
Size: 3726 GB
Free Space: 0 GB
Number of Hard Drives: 4
Hard Drive Member 1: SAMSUNG HD103SJ
Hard Drive Member 2: SAMSUNG HD103SJ
Hard Drive Member 3: Missing hard drive
Hard Drive Member 4: Missing hard drive
Number of Volumes: 1
Volume Member 1: Raid10

Raid10
Status: Failed
System Volume: No
Volume Write-Back Cache Enabled: No
RAID Level: RAID 10 (striping and mirroring)
Strip Size: 64 KB
Size: 1863 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Hard Drives: 4
Hard Drive Member 1: SAMSUNG HD103SJ
Hard Drive Member 2: SAMSUNG HD103SJ
Hard Drive Member 3: Missing hard drive
Hard Drive Member 4: Missing hard drive
Parent Array: Array_0000

Hard Drive 0
Usage: Spare
Status: Normal
Device Port: 0
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: SAMSUNG HD103SJ
Serial Number: S2AEJ1BZ507341
Firmware: 1AJ10001
Native Command Queuing Support: Yes
System Hard Drive: No
Size: 931.5 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes

Hard Drive 1
Usage: Spare
Status: Normal
Device Port: 1
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: SAMSUNG HD103SJ
Serial Number: S2AEJ1BZ507337
Firmware: 1AJ10001
Native Command Queuing Support: Yes
System Hard Drive: No
Size: 931.5 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes

Hard Drive 2
Usage: Array member
Status: Normal
Device Port: 2
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: SAMSUNG HD103SJ
Serial Number: S2AEJ1BZ507351
Firmware: 1AJ10001
Native Command Queuing Support: Yes
Hard Drive Data Cache Enabled: Yes
Size: 931.5 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Volumes: 1
Volume Member 1: Raid10
Parent Array: Array_0000

Hard Drive 3
Usage: Array member
Status: Normal
Device Port: 3
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: SAMSUNG HD103SJ
Serial Number: S2AEJ1BZ507339
Firmware: 1AJ10001
Native Command Queuing Support: Yes
Hard Drive Data Cache Enabled: Yes
Size: 931.5 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Volumes: 1
Volume Member 1: Raid10
Parent Array: Array_0000

Hard Drive 4
Status: Missing

Hard Drive 5
Status: Missing

Unused Port 0
Device Port: 5
Device Port Location: Internal

CD/DVD Drive 0
Device Port: 4
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 1
Model: PIONEER BD-RW BDR-205
Serial Number: Data not reported
Firmware: 1.09


Fortunately the os drive is separate so at least I can boot and send out this message :) Anyone with suggestion / ideas as how I can get it to rebuild the volume. And what exactly happen for the two perfectly fine drives to go missing from the array?

Thanks very much in advance.
 

Sc0tt9614

Distinguished
Feb 10, 2011
1
0
18,510
Are you still having this problem? I certainly hope not. For any others experiencing this problem that happen to run across this thread I have some advice. Ensure your hard drives are RAID compatible!! Western Digital RE3 and RE4 drives are RAID capable and they support TLER (Time Limited Error Recovery). What happens with non TLER drives is that the firmware takes to long to detect/recover errors and as a result the RAID controller marks the drive bad even though it really isn't.
 

rand_79

Distinguished
Apr 10, 2009
829
0
19,010
way to go topic architect.

There was a bad intel driver release i believe it was 8.9.

It made my raid 0 drives fall out of array periodically.
rolling back to 8.8 fixed it after reinstalling windows.

for reference i have an abit ip35 motherboard with intel ich9r