Delayed Write Failed on USB disks

  • Thread starter Thread starter Martijn Saly
  • Start date Start date
M

Martijn Saly

Hi all,

I have several USB disks, all different makes and models. I use them on
different Windows XP computers. The disks are working nicely, even when
using them all of them simultaneously.

Now when I leave them connected, put my pc in hibernation, unplug them and
resume from hibernation, Windows might come up with an error saying "Delayed
Write Failed" and refers to G:\$MFT (where G: is one of my USB disks).

Because this happens on all computers I've come across so far, and with all
USB disks I've had, logic dictates that hardware is not at fault. So I have
2 questions about this error:

1) Why does Windows delay writes when Windows knows it shouldn't do that??
2) Most importantly, when will Microsoft fix this?
 
The more important question is why are YOU using hibernate incorrectly!

Hibernate returns the computer "exactly" to the condition it was in when you
implemented hibernation.

YOU have removed the USB drives. YOU have made it so the computer is NOT in
the exact condition it was in when hibernation occurred.

Suggest you modify your actions.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Richard said:
The more important question is why are YOU using hibernate incorrectly!

Hibernate returns the computer "exactly" to the condition it was in when you
implemented hibernation.

YOU have removed the USB drives. YOU have made it so the computer is NOT in
the exact condition it was in when hibernation occurred.

Suggest you modify your actions.
Click to expand...

Sorry, but it is the same as disconnecting the USB disk at the moment of
hibernating. Upon resuming I do hear the "device disconnect" sound as
expected, so Windows knows the device has been disconnected. So rather than
bothing the user with a cryptic error, it could say something clearer.

Anyway, I still think the most important matter is that Windows simply
should NEVER delay writes to a disk that can potentially be disconnected at
any given moment.

Moreover, this problem can also occur without ever using hibernation. Just
write a large lump of data to a USB disk and when the action appears to have
completed, disconnect the disk (this is how a n00b user will think). Then
you might get either the "delayed write failed" error, or the written files
are just corrupted, which is much worse.
 
If you have the USB device optimized for performance you are, in fact,
enabling "delayed writes. You must then use the supplied "disconnect"
utility in the system notification area to shut down the USB device. This
will flush all delayed writes to the USB device before it allows you to turn
off the device.

Go to device manager and change this setting if you want the device to
operate differently. If neither of the two options fit you, change your
habits.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Richard said:
If you have the USB device optimized for performance you are, in fact,
enabling "delayed writes. You must then use the supplied "disconnect"
utility in the system notification area to shut down the USB device. This
will flush all delayed writes to the USB device before it allows you to turn
off the device.

Go to device manager and change this setting if you want the device to
operate differently. If neither of the two options fit you, change your
habits.
Click to expand...

It's set to be optimized for fast removal. This disables the write cache.
And should disable delayed writes. This should NEVER result in
corrupt/incomplete files or delayed write fails, according to logic.

Now answer this simple question: why are writes being delayed anyway?
 
Because writes that are in progress are not flushed to the USB device upon
the initiation of hibernation. Now, you disconnect the USB device while the
computer is hibernated. Where do you expect the writes to go when you again
turn on your computer. You have removed the target drive.

Again, YOU are the problem! This is the case with 90% of all computer
problems. They are user initiated. I have been fighting clients for years
because they refuse to change their ways. But hey, it's good money!

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Richard Urban said:
Because writes that are in progress are not flushed to the USB device upon
the initiation of hibernation. Now, you disconnect the USB device while
the computer is hibernated. Where do you expect the writes to go when you
again turn on your computer. You have removed the target drive.

Again, YOU are the problem! This is the case with 90% of all computer
problems. They are user initiated. I have been fighting clients for years
because they refuse to change their ways. But hey, it's good money!

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)
Click to expand...

I have the same "delayed write" error but it happens on return from
hibernation when the USB HDD is _still_ connected. The caddy LED indicates
disk activity for a long time, then the error message appears and the drive
letter disappears from Explorer - even though the "safe disconnect" icon
shows, and if I click it it tells me that the device is "working properly".

Also the HDD is not recognised if already connected on startup but it is
recognised every time when plugging into the running PC. I have SP2 fully
updated etc. Tried double head USB lead in case of power problems, no
difference. USB drive is optimised for quick disconnect. Power saving in
USB roots disabled.

This is not convenient for the way I would prefer to work so suggestions
appreciated..
 
Back
Top