event id 50 (ftdisk) - the write operation failed...

[GO]

I've just seen several "Lost Delayed-Write Data" errors in the event viewer
followed by a related Application Popup error (see below). I've seen this
happen once before and it was indicative of a failing hard drive, although
I'm not sure if this is the case this time around as I am unable to
determine what drive is actually being specified by
"device\HarddiskVolume9". I've run chkdsk on all my drives with no signs of
any problems and I came across mention of a tool call dmdiag.exe in another
old thread. I've tried the tool and it doesn't seem to yield anything of
importance. In the drive letter and device name section it only lists
volumes 1 through 7 and one volume 10. Within the devices section there is
mention of a Volume9 but not sure what it's referencing (an old mapped
drive?)

Event Viewer info:

Event Type: Warning
Event Source: Ftdisk
Event Category: None
Event ID: 50
Date: 10/17/05
Time: 4:51:09 PM
User: N/A
Description:
{Lost Delayed-Write Data} The system was attempting to transfer file data
from buffers to \Device\HarddiskVolume9. The write operation failed, and
only some of the data may have been written to the file.
Data:
0000: 00 00 04 00 01 00 5e 00 ......^.
0008: 00 00 00 00 32 00 04 80 ....2..€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0e 00 00 c0 ...À

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 10/17/05
Time: 4:51:09 PM
User: N/A
Description:
Application popup: Windows - Delayed Write Failed : Windows was unable to
save all the data for the file \Device\HarddiskVolume9\$Mft. The data has
been lost. This error may be caused by a failure of your computer hardware
or network connection. Please try to save this file elsewhere.



Can anyone shed any light on this?


TIA,

Greg

 

[Dan Seur]

This is most often simply an internal system buffer deadlock, or
overrun, that clears a cache before the actual disk write has occurred.
Consider this particularly if your system has been unusually busy
lately. If you Google for "Lost Delayed-Write Data" you'll find several
handy essays on this error condition, including pointers to a few MS
KB#s and a hotfix or two. It's more likely, I think, that an umanageable
software queueing problem is at fault here than a hard drive glitch.

 

[GO]

Hi Dan,

Thanks for the info! I think I may have found what the culprit is. I've
been playing around with Acronis' True Image program which allows you to
mount images as hard drives. I also just came across a lot of disk errors
(see below). It mentions the error is on Harddisk3, which I'm assuming
doesn't really exist as I only have two phyiscal hard drives (harddisk0 and
harddisk1?). At least I hope that's the case. Not sure why they've creeped
in today as the machine has been idle all up until now.

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 10/17/05
Time: 5:00:46 PM
User: N/A
Description:
The driver detected a controller error on \Device\Harddisk3\DR15.


Thanks again,

Greg