Event 11, disk

What is Event 11, disk? How can I fix it?

- <System>
<Provider Name="Disk" />

<EventID Qualifiers="49156">11</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2010-02-19T15:38:16.563686400Z" />

<EventRecordID>2979182</EventRecordID>

<Channel>System</Channel>

<Computer>Laura-PC</Computer>

<Security />

</System>


- <EventData>
<Data>\Device\Harddisk2\DR2</Data>

<Binary>0E00800001000000000000000B0004C003010000000000000000000000082D000000000000000000189138010000 0000FFFFFFFF0600000058000000000000000000061208000010000000003C0000000000000000000000C0A7010880FAFFFF 0000000000000000B003B70580FAFFFF00000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000</Binary>

</EventData>


</Event>

Event ID 11 Source Disk

Check with a hard drive diagnostic tools.

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

theog said:

Check with a hard drive diagnostic tools.

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Ok. The HD that's giving the error is an external drive. Manufacturer is Western Digital. It is formatted NTFS but it does not have an OS on it. So which utility should I download?

lak611 said:

theog said:

Check with a hard drive diagnostic tools.

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Ok. The HD that's giving the error is an external drive. Manufacturer is Western Digital. It is formatted NTFS but it does not have an OS on it. So which utility should I download?

I always use the DOS utility.

What is a cable test write sector error?

lak611 said:

What is a cable test write sector error?

You need to replace the cable.

SMART status passes on both drives using Western Digital Data Lifeguard Diagnostics. Running Windows disk check on external drive now.

Thanks for your help. :) I did not find anything wrong with the disk using the Western Digital utility, but when I ran CHKDSK, Windows found free space that was wrongly marked as allocated. All is good now.