New
#1
"Disk error" invisible except to event viewer, when imaging hard drive
My Windows 7 configuration is relatively bullet proof (ha ha, nervous laughter).
My OS and programs are on C, which I image using RDriveImage every month after Patch Tuesday.
My data is on software-mirrored D/F drives.
So as long as I don't have a catastrophic event affecting my computer, a routine "drive failure" should be recoverable, with the worst-case being I'd be out a month of updates, but with a good recent image of the OS drive.
Anyway, I was recently looking at my event viewer and I have "Disk errors" that occur whenever I run a full image of C.
The complete error text is:
There were two errors in February (none before that), three in March, four each in May and July. In April and June I did incremental images, so the "bad" area wasn't imaged, so no error.Log Name: System
Source: Disk
Date: 7/13/2012 3:38:44 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
The driver detected a controller error on \Device\Harddisk3\DR3.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-07-13T19:38:44.199218700Z" />
<EventRecordID>136049</EventRecordID>
<Channel>System</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk3\DR3</Data>
<Binary>0E01800001000000000000000B0004C003010000000000000000000000082D0000000000000000000D563C000000 0000FFFFFFFF0600000058000000000000000000061208000010000000003C0000000000000000000000405E7A0780FAFFFF 00000000000000001066250A80FAFFFF00000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
With all the above as background, what's the safest way for me to isolate and/or repair the area(s) of the disk with the errors?
The errors are always logged within 1-2 seconds of each other, so I suspect it's just one bad area.
And I have never, ever, seen signs of a disk error. No BSOD, no clicking noises, no impaired performance, even for a moment.