Sign in with
Sign up | Sign in
Your question
Solved

Raid 1 + Intel Matrix Storage Manager not accesible

Last response: in Storage
Share
October 7, 2010 4:24:00 AM

Tom's Hardware,

I've some some searching tonight, but I haven't been able to find the exact answer to my problem. Here's the issue:

Problem - Raid 1 Volume inaccessible. Volume managed by Intel Matrix Storage Manager (motherboard). There are two WD 1.5TB drives in the array. The array is for storing work / media and is not required to boot the PC. When viewing the advanced view for Matrix Storage Manager, one drive in the array is marked as 'Failed' with a red 'X' over it, while the other drive is marked as 'Normal'.

I can mark the 'Failed' drive as 'Normal' and execute a 'Rebuild', but the rebuild fails after a minute and remarks the first drive as failed. I'm confused why my raid volume is inaccessible rather than degraded, since 1 volume is still marked as OK. If I mark the failed drive as Normal, the volume becomes 'degraded', but I can only view folders in the volume. Reading anything other than directory structure on the volume in degraded state fails (like trying to open a picture or word file). I've had a drive drop out of the array before, but I was able to mark it as normal and rebuild just fine. Any help or pointers are appreciated.

Here is the Matrix Storage Manager - Advanced view report below...
-----------------------------------------------------
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: ULT-PC
System Manufacturer: ASUSTeK Computer INC.
System Model: P6T DELUXE V2
Processor: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
BIOS Version/Date: American Megatrends Inc. 0504 , 05/19/2009

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: 2794.5 GB
Free Space: 0 GB
Number of Hard Drives: 2
Hard Drive Member 1: WDC WD15EADS-00R6B0
Hard Drive Member 2: WDC WD15EADS-00R6B0
Number of Volumes: 1
Volume Member 1: R1Ports:02

R1Ports:02
Status: Failed
System Volume: No
Volume Write-Back Cache Enabled: No
RAID Level: RAID 1 (mirroring)
Size: 1397.2 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Hard Drives: 2
Hard Drive Member 1: WDC WD15EADS-00R6B0
Hard Drive Member 2: WDC WD15EADS-00R6B0
Parent Array: Array_0000

Hard Drive 0
Usage: Array member
Status: Failed
Device Port: 0
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: WDC WD15EADS-00R6B0
Serial Number: WD-WCAVY0041255
Firmware: 01.00A01
Native Command Queuing Support: Yes
Hard Drive Data Cache Enabled: Yes
Size: 1397.2 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Volumes: 1
Volume Member 1: R1Ports:02
Parent Array: Array_0000

Hard Drive 1
Usage: Non-RAID hard drive
Status: Normal
Device Port: 1
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: WDC WD15EADS-00P8B0
Serial Number: WD-WMAVU0461365
Firmware: 01.00A01
Native Command Queuing Support: Yes
System Hard Drive: No
Size: 1397.2 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: WDC WD15EADS-00R6B0
Serial Number: WD-WCAVY0028516
Firmware: 01.00A01
Native Command Queuing Support: Yes
Hard Drive Data Cache Enabled: Yes
Size: 1397.2 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes
Number of Volumes: 1
Volume Member 1: R1Ports:02
Parent Array: Array_0000

Hard Drive 3
Usage: Non-RAID hard drive
Status: Normal
Device Port: 5
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 2
Model: OCZ-AGILITY
Serial Number: QZP3JGHQF61Q4ARY81I5
Firmware: 1.4
Native Command Queuing Support: Yes
System Hard Drive: Yes
Size: 119.2 GB
Physical Sector Size: 512 Bytes
Logical Sector Size: 512 Bytes

Unused Port 0
Device Port: 4
Device Port Location: Internal

CD/DVD Drive 0
Device Port: 3
Device Port Location: Internal
Current Serial ATA Transfer Mode: Generation 1
Model: HL-DT-ST BDDVDRW CH10LS20
Serial Number: K9EA5P24550
Firmware: 1.00
-----------------------------------------------------

More about : raid intel matrix storage manager accesible

Best solution

a b G Storage
October 7, 2010 11:03:31 PM

An observation: WD only recommends its RE-X series of HDDs for RAID, not green, blue, or black. WD has "fixed" its non-RAID HDDs' TDLR - you can google that sometime.

Your problem: This may sound weird but with the machine and IMMC running, pull the SATA data cable from each HDD in the affected volume. Wait a couple of minutes and re-attach the SATA data cables. Now in IMSM, and mark the failed HDD as normal. See if that allows the volume to rebuild. I think it will.

It is possible that you have a bad HDD, but I believe this is a problem with Intel's RAID chipsets - the ones with the R following the chipset, e.g., ICH9R, ICH10R.

My two (three counting the replacement - see below) RE-2s in RAID1 have been giving me fits for about six weeks. WD has even replaced one under warranty (RMAed on the WD website - very painless, even a discounted UPS sticker). I did not want to go through the headache of a clean install with all the programs and settings to reload. I tried everything, replacing the "bad" HDD with a fresh one and trying the rebuild in Intel Rapid Storage Technology (the new version of Intel Matrix Storage Manager), breaking the volume in the BIOS (don't do that unless you want to learn some new programs for recovering RAID volumes), and finally the solution I offered above. It has been about a week since I've had a "Failed" HDD.

My issues are on the DFI-DK-X48-T2RSB+, with one RAID1 volume partitioned into two primary partitions: one for XP and one for My Documents (shown in my information); the other HDDs are JBOD. I'm running two RAID1 volumes (XP and W7) on my other system, the DFI-UT-X48-T3RS, and I have not ever had any issues with the board - and it helped me save my affected volume on the other board where I learned about recovering RAID volumes! On my next clean install, I won't be using RAID - when it works, it is great. But when it doesn't, it is a PITA. I have come to believe frequent backups are a better solution.
Share
October 8, 2010 12:05:38 AM

treefrog07,

Thank you for taking the time to respond to my post. Here's what I did:

1) Opened IMSM
2) Removed the SATA cables from the 2 raid member drives.
3) Waited several minutes
4) Reconnected the SATA cables from step (2)
At this point, the volume was inaccessible
Port 0 was bad, port 2 was normal
5) Marked 0 as normal
6) Executed rebuild on raid 1 volume
7) Raid volume rebuild failed shortly after

I noticed you said 'with IMMC' running - was that the matrix storage manager or something else? If it was something else, I did your solution wrong. I have a spare 1.5TB drive, should I tried swapping it in for port0?
m
0
l
Related resources
October 20, 2010 11:37:53 PM

I used a third hard drive of the same size to rebuild the array 'as a spare', which ended up fixing the problem.
m
0
l
October 20, 2010 11:38:04 PM

Best answer selected by Ultimaswc3.
m
0
l
a b G Storage
October 22, 2010 5:36:14 PM

Sorry for the late response - between work and other obligations, I couldn't get back here. You solved it! You followed the steps as I intended.

Hold on to the "Bad" HDD. When you have time, or are just curious:
-- Add the "Bad" HHD back to your system (with the power cord disconnected from the system),
-- Connect the power and SATA cables.
-- Disconnect one of the functioning HDDs in the volume, only the SATA cable.
-- Reconnect the power cord.
-- Power-on the system.
-- Boot into Windows
-- Open Intel Matrix Management Console.
-- See if IMMC will rebuild the volume to the "Bad" HDD.
If it does so, you have a "backup" volume on the disconnected HDD. If it does not, or if it "breaks" the RAID volume, the "Bad" HDD may really be bad. Download, install, and run WD's Data Lifeguard Utility to check it. If it fails, RMA it to WD.
m
0
l
!