Delayed Write Failed when copying data to USB drive

Dear all

I have a problem with backup up some files on USB drive on a WXP SP2 machine. Basically what I am trying to do is copying a 95GB .BKF file from a SATA HDD onto a USB HDD (external connected through USB 2.0). The process is being initated by robocopy with the use of a script.

Problem is that sometimes transfer suceeds but most of the times it fails and gives this error:



Event Type: Warning
Event Source: Ntfs
Event Category: None
Event ID: 50
Date: 21/08/08
Time: 15:09:04
User: N/A
Computer: CALL-LOGGING
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file . 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 52 00 ......R.
0008: 00 00 00 00 32 00 04 80 ....2..?
0010: 00 00 00 00 9a 00 00 c0 ....?..
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 9a 00 00 c0 ?..



I tried replacing RAM, updating BIOS, changing USB cable, changing USB port, tweaking with cache sizes, increasing virtual memory ....all this in vain.

Your help is greatly appreciated!

 

Try this

http://support.microsoft.com/kb/330174

 

I still havent found solution to this problem. I am now using Karen's replicator to perform the data transfer and eliminated the USB drive. In fact now I am trying to it from SATA1 HDD-to-SATA2 HDD and still problem persists....checked both drives and no errors!

any help?

 

I tried everything to solve this problem and still no luck. I guess this thread could be closed.

 

Try these:

Some common reasons for a delayed-write failure are:

* 1. Problems with a device driver, especially a SCSI or RAID device driver. Some RAID device drivers are known to issue spurious "Delayed Write Failed" errors in XP Service Pack 2. Most manufacturers have been alerted to this, so check to make sure the disk drivers are up-to-date.

* 2. Cabling problems. A faulty or broken cable -- especially for an external USB or Firewire enclosure—can generate this error. It can also happen if the cable is too long, or if it is hooked up through a hub that isn't up to spec. Another possible culprit is if you have a UDMA drive that requires an 80-pin cable, and you are using a 40-pin cable.

* 3. SCSI termination errors. This has become less likely with the advent of self-terminating SCSI hardware, but it shouldn't be counted out.

* 4. Media errors. This is the worst possible scenario -- essentially, drive failure. If you can garner statistics on the drive via SMART (such as SMART & Simple (http://www.beyondlogic.org/solutions/smart/smart.html), you may be able to determine if there's a mechanical failure in the offing. Gibson Research's SpinRite tool (http://grc.com/) is also useful for assessing media errors, but be warned: It may take a long time to do a thorough test.

* 5. BIOS settings on the computer are forcing faster UDMA modes than the drive controller can handle. This is unlikely, especially with newer hardware (which can support UDMA far more flexibly), but it can usually be fixed with a BIOS upgrade, or by resetting the BIOS entries for the hard drives to auto-detect settings. Devices set to UDMA Mode 6 that produce this error, for instance, might need to be set to Mode 5.

* 6. Controller issues. I've observed that USB controllers that contend strongly with other hardware can produce this error. In systems that have both "long" and "short" PCI slots (i.e., 64-bit and 32-bit), try moving the USB controller to the long slot. Older PCI cards will not fit in such a slot.

* 7. Memory parity issues. If the problem appears after installing new memory, the memory in question may be faulty or not of the correct type for the motherboard in question. (This may go hand-in-hand with other problems such as random lockups, too.)

* 8. The LargeSystemCache Registry tweak and ATI video adapters. One peculiar set of circumstances that has been observed on multiple machines with ATI video adapters and more than 512MB of memory involves the LargeSystemCache Registry setting, a DWORD entry found in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management. This setting governs the amount of memory set aside by the system for certain kernel processes. If it's set to 1 (which allegedly improves performance on systems with more than 512MB of memory), it can cause data corruption on some systems, and produce the "Delayed Write Failed" error. Try resetting it to 0 if it's been set.

First on google...

 

I created a script with robocopy and NTBACKUP and now this is happening!! Trnafser is being done IDE-disk-to-IDE-disk

Can someone advise what might the problem be?


Event Type: Warning
Event Source: Ftdisk
Event Category: None
Event ID: 50
Date: 20-10-2008
Time: 5:02:30 AM
User: N/A
Computer: SERVER-A
Description:
{Lost Delayed-Write Data} The system was attempting to transfer file data from buffers to \Device\HarddiskVolume3. 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: 9a 00 00 c0 ?..