delayed write errors

  • Thread starter Thread starter Ronald van Riet
  • Start date Start date
R

Ronald van Riet

I have run Win200 Professional (SP4) for about two years and a couple of
weeks ago the machine seemed to have slowed down (initially I suspected
Blaster, but this was not found) and now I get error messages about failed
delayed writes. At least one of the files that was mentioned is now corrupt.

utilities like chkdsk and defragment stop unexpectedly before finishing so
something seems to be pretty wrong with the file system.

What would be the best course of action: upgrade to XP? convert the disk
from FAT32 to NTFS (but will PartitionMagic run properly)? get a new disk?
any other ideas?

and yes, I am copying as much of the disk as I can to other computers.....

tx

Ronald
 
Ronald van Riet wrote in
I have run Win200 Professional (SP4) for about two years and a
couple of weeks ago the machine seemed to have slowed down
(initially I suspected Blaster, but this was not found) and now I
get error messages about failed delayed writes. At least one of
the files that was mentioned is now corrupt.

utilities like chkdsk and defragment stop unexpectedly before
finishing so something seems to be pretty wrong with the file
system.

What would be the best course of action: upgrade to XP? convert
the disk from FAT32 to NTFS (but will PartitionMagic run
properly)? get a new disk? any other ideas?

and yes, I am copying as much of the disk as I can to other
computers.....
Click to expand...

Well you can turn off delayed writes...
But it sounds more like a failing HDD. You have tried chkdsk /R I
presume. Suggest after you get the data safe download the
manufacturer's HD dignostics tools for a more thorough test of the
drive.
 
I checked everything according to KB 321733 (and moreover, this fix is
included in SP4 which I have installed).

There are no corresponding entries in the error log, just a series of
warnings.

delayed writes are turned off (that is, according to the 321377 description
of registry entries).

seems to be more like a hardware failure indeed.

Ronald
 
Back
Top