Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
1,650 Views

Intel Storage Matrix Hanging System

I have the configuration outlined below. 5 x 1Tb drives, RAID 5.

I have the latest bios, Intel drivers. I've been getting random system hangs where the entire server locks up with HD light on solid.

Cannot recover, have to power off and back on again? Can anyone suggest what could cause it to lock up so hard? Windows does not log anything

just an event on the power up saying unexpected system crash...

Thanks in advance...

System Information

Kit Installed: 8.8.0.1009

 

Kit Install History: 8.8.0.1009, Uninstall

 

Shell Version: 8.8.0.1009

OS Name: Microsoft(R) Windows(R) Server 2003, Enterprise Edition

 

OS Version: 5.2.3790 Service Pack 2 Build 3790

 

System Name: WALLSVR

 

System Manufacturer: ASUSTeK Computer INC.

 

System Model: P5Q3 DELUXE

 

Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz

 

BIOS Version/Date: American Megatrends Inc. 1901 , 02/12/2009

Language: ENU

Intel(R) Matrix Storage Manager

Intel RAID Controller: Intel(R) ICH8R/ICH9R/ICH10R SATA RAID Controller

 

Number of Serial ATA ports: 6

 

 

RAID Option ROM Version: 8.0.0.1038

 

Driver Version: 8.8.0.1009

 

RAID Plug-In Version: 8.8.0.1009

 

Language Resource Version of the RAID Plug-In: 8.8.0.1009

 

Create Volume Wizard Version: 8.8.0.1009

 

Language Resource Version of the Create Volume Wizard: 8.8.0.1009

 

Create Volume from Existing Hard Drive Wizard Version: 8.8.0.1009

 

Language Resource Version of the Create Volume from Existing Hard Drive Wizard: 8.8.0.1009

 

Modify Volume Wizard Version: 8.8.0.1009

 

Language Resource Version of the Modify Volume Wizard: 8.8.0.1009

 

Delete Volume Wizard Version: 8.8.0.1009

 

Language Resource Version of the Delete Volume Wizard: 8.8.0.1009

 

ISDI Library Version: 8.8.0.1009

 

Event Monitor User Notification Tool Version: 8.8.0.1009

 

Language Resource Version of the Event Monitor User Notification Tool: 8.8.0.1009

 

Event Monitor Version: 8.8.0.1009

 

 

Array_0000

 

Status: No active migrations

 

Hard Drive Data Cache Enabled: No

 

Size: 3726 GB

 

Free Space: 0 GB

 

Number of Hard Drives: 4

 

Hard Drive Member 1: Hitachi HDS721010KLA330

 

Hard Drive Member 2: Hitachi HDS721010KLA330

 

Hard Drive Member 3: Hitachi HDS721010KLA330

 

Hard Drive Member 4: Hitachi HDS721010KLA330

 

Number of Volumes: 2

 

Volume Member 1: SYSTEM

 

Volume Member 2: Data

 

 

SYSTEM

 

Status: Normal

 

System Volume: Yes

 

Volume Write-Back Cache Enabled: No

 

RAID Level: RAID 5 (striping with parity)

 

Strip Size: 64 KB

 

Size: 250 GB

 

Physical Sector Size: 512 Bytes

 

Logical Sector Size: 512 Bytes

 

Number of Hard Drives: 4

 

Hard Drive Member 1: Hitachi HDS721010KLA330

 

Hard Drive Member 2: Hitachi HDS721010KLA330

 

Hard Drive Member 3: Hitachi HDS721010KLA330

 

Hard Drive Member 4: Hitachi HDS721010KLA330

 

Parent Array: Array_0000

 

 

Data

 

Status: Normal

 

System Volume: Yes

 

Volume Write-Back Cache Enabled: Yes

 

RAID Level: RAID 5 (striping with parity)

 

Strip Size: 64 KB

 

Size: 2544.5 GB

 

Physical Sector Size: 512 Bytes

 

Logical Sector Size: 512 Bytes

 

Number of Hard Drives: 4

 

Hard Drive Member 1: Hitachi HDS721010KLA330

 

Hard Drive Member 2: Hitachi HDS721010KLA330

 

Hard Drive Member 3: Hitachi HDS721010KLA330

 

Hard Drive Member 4: Hitachi HDS721010KLA330

 

Parent Array: Array_0000

 

 

Hard Drive 0

 

Usage: Array member

 

Status: Normal

 

Device Port: 0

 

Device Port Location: Internal

 

Current Serial ATA Transfer Mode: Generation 2

 

Model: Hitachi HDS721010KLA330

 

Serial Number: GTA040PAKJ34EF

 

Firmware: GKAOAB0A

 

Native Command Queuing Support: Yes

 

Hard Drive Data Cache Enabled: No

 

Size: 931.5 GB

 

Physical Sector Size: 512 Bytes

 

Logical Sector Size: 512 Bytes

 

Number of Volumes: 2

 

Volume Member 1: SYSTEM

 

Volume Member 2: Data

 

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: Hitachi HDS721010KLA330

 

Serial Number: GTE005PAKN2P3L

 

Firmware: GKAOAB0A

 

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: Hitachi HDS721010KLA330

 

Serial Number: GTE005PAKN2AHL

 

Firmware: GKAOAB0A

 

Native Command Queuing Support: Yes

 

Hard Drive Data Cache Enabled: No

 

Size: 931.5 GB

 

Physical Sector Size: 512 Bytes

 

Logical Sector Size: 512 Bytes

 

Number of Volumes: 2

 

Volume Member 1: SYSTEM

 

Volume Member 2: Data

 

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: Hitachi HDS721010KLA330

 

Serial Number: GTA040PAKJBHHF

XXXWHITESPACEX...

0 Kudos
8 Replies
idata
Community Manager
50 Views

Here's what I found and it was the only thing that worked for me.

I used nLite software to create a bootable disk with the updated drivers integrated into the setup disk.

That way one doesn't have to use the F6 during installation.

dave

idata
Community Manager
50 Views

The system is up and running, that's not the issue. Built no problem...

System stability is the issue... I've heard rumours it could be an underpowered PSU.

It's on a 500W now, I've run some calculations using online PSU calcs, they seem to come out with 400Wish requirements...

I wonder if ugrading the PSU would solve this?

idata
Community Manager
50 Views

wass wondering if you ever figured out what was causing the crashes?

idata
Community Manager
50 Views

I am having this EXACT problem - system will be going along just fine and then I will loose connectivity (to it via the network, cannot ping the PC, console is locked, and the only thing i can do it reset it.

Has anyone a better idea what may be causing this? I am using the latest storage manager. (8.9.1023)

idata
Community Manager
50 Views

I have had the exact same problems and corrected it by enabling the hard drive data cache (not the write back cache) but the "Hard Drive Data Cache Enabled" set to yes. once this is done the other issues will go away but you have to reset this every time you reboot and I haven't found a way around that - which is why I am searching now.

idata
Community Manager
50 Views

I have had the exact same problems and corrected it by enabling the hard drive data cache (not the write back cache) but the "Hard Drive Data Cache Enabled" set to yes. once this is done the other issues will go away but you have to reset this every time you reboot and I haven't found a way around that - which is why I am searching now. - Do this in the Matrix console under Arrays -> Array_0000 (or which ever array you are working with) not under volume which is the Write back cache (which can gain you performance but be sure you know the ins and outs)

idata
Community Manager
50 Views

I have the Hard Drive Data Cache enabled at the array and I still experience system hanges. Any other ideas?

Thanks,

George

idata
Community Manager
50 Views

This issue has been driving me nutz lately, and I believe I've finally got the work around, or at least a good part of it. I agree that it appears to be with the cache settings. If you notice in your report, under hard drive 3, that the cache is enabled on this one, and only this one:

"Hard Drive Data Cache Enabled: Yes"

This happened to me after I replaced a drive. Obviously, since it is part of a RAID volume, you can't change the individual drive setting, either from within the Intel Matrix Storage Console (IMSM) or from Device Manager (at least, not under mine - Vista), and it also appears that the default setting for "new" drives is that cache is enabled, regardless of the settings for the existing RAID volume and drives. The solution that has worked (so far!) was to right click the volume under IMSC, and Disable Volume Write-Back Cache. This was followed with toggling and ultimately disabling the cache features via Device Manager. While doing this, you may wish to monitor the settings for each Port under the RAID Hard Drives section of your IMSM to ensure that all drives are set the same.

My RAID 10 hasn't had a problem since. I should note that my next try at it will be to enable all the cache features and see where that takes me, but for now, I'm happy that my RAID is back up and running without intermittently reporting a hard drive failure. After the passage of time to ensure that this is a fix, I'll try enable the various cache settings.

I should note also that I never experienced these problems prior to installing version 8.9 of IMSM, and have read that version 8.8 fixes this issue for some. 8.9 was installed during a system rebuild (Vista 64/D975XBX2) a few weeks ago, and I've been plagued with the problem until this "fix".

Reply