grheard
September 7, 2010, 11:26pm
1
Hello.
I’ve had my new rig up for a little over 1 month and I am plagued by some infrequent yet annoying scenarios.
Every once in a while my machine becomes very sluggish. At the same time I will get the following messages in my event viewer:
Log Name: System
Source: mv91xx
Date: 9/6/2010 10:41:24 AM
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: i7
Description:
The device, \Device\Scsi\mv91xx1, did not respond within the timeout period.
Event Xml:
9
2
0
0x80000000000000
10674
System
i7
\Device\Scsi\mv91xx1
000010000100000000000000090004C001010050000000000000000000000000000000000000000000000000000000000000000007000000
Log Name: System
Source: mv91xx
Date: 9/6/2010 10:41:29 AM
Event ID: 3
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: i7
Description:
Request to physical disk 0 is timed out.
Event Xml:
3
3
0
0x80000000000000
10675
System
i7
0
000004000200300000000000030002A0000000000000000000000000000000000000000000000000030002A0
This is a WD1002FAEX attached to a Marvell 9123 controller on an ASUS Rampage III Extreme motherboard. The Marvell driver is 1036 (latest one at ASUS for this Motherboard). The system is Win7 x64 Pro.
When I use HDTune or the bootable version of Data Lifeguard, they both indicate that the drive is fine.
Is there a firmware or setting in the WD that can prevent this?
Has anyone else been plagued with these ‘stalls’?
spalm
September 9, 2010, 6:40pm
2
Having the exact same issue here! I’m using the asus P6x58d premium board with 2x1tb Black drives. Would love to know the fix for this.
grheard
September 10, 2010, 2:48am
3
More errors starting to crop up…
Log Name: System
Source: mv91xx
Date: 9/9/2010 5:57:09 PM
Event ID: 36
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: i7
Description:
Command [0x28] on physical disk 0 failed. Sense key=0xb, ASC=0x0, ASCQ=0x0.
Event Xml:
36
4
0
0x80000000000000
12711
System
i7
0
28
b
0
0
0000040006003000000000002400026000000000000000000000000000000000000000000000000024000260
Log Name: System
Source: mv91xx
Date: 9/9/2010 6:00:30 PM
Event ID: 36
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: i7
Description:
Command [0xe1] on physical disk 0 failed. Sense key=0xb, ASC=0x0, ASCQ=0x0.
Event Xml:
36
4
0
0x80000000000000
12722
System
i7
0
e1
b
0
0
0000040006003000000000002400026000000000000000000000000000000000000000000000000024000260
These errors along with those I stated above occurred 10 times in a period of 4 minutes earlier this evening.
I’m not feeling too good about this drive.
grheard
September 23, 2010, 6:05pm
4
Since my last post, I have changed SATA cables and moved the drive from the Marvell 9123 (SATA III) to one of the ICH10R (SATA II) ports. This morning I was greeted with this:
Log Name: System
Source: atapi
Date: 9/23/2010 11:10:08 AM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: i7
Description:
The driver detected a controller error on \Device\Ide\IdePort2.
Event Xml:
11
2
0
0x80000000000000
15412
System
i7
\Device\Ide\IdePort2
0000100001000000000000000B0004C002000000850100C00000000000000000000000000000000002000000000000000000000004100000
Anyone else think its time for WD to replace this drive?
Did the RMA(replacing) the drive work ? I’m having the same problem
grheard
November 23, 2010, 5:14pm
8
Yes. I have since bought a second drive without incidence.
Hello,
I am having similar problems with WD1002FAEX-00Z3A0 hard drive. The revision of the drive is 05.01D05.
I have ASUS P7P55D-E Deluxe motherboard with Marvell PCIe SATA 6Gb/s controller.
I see these errors in the event log: The device, \Device\Scsi\mv91xx1, did not respond within the timeout period.
I am wondering if this is a common problem with that revision and if replacing the drive is the only solution.
Should I expect to get an answer from WD employee here or there is other method to contact WD support?
@grheard : Could you please tell me what is the revision of the new drive you received? Thanks in advance.