Open a COMMAND window (start, run, CMD) and this command.
CHKDSK D: /F
If it asks to run it at boot time, answer yes and reboot.
I'm using a Seagate 200gb drive attached through SATA for backing up files and a number of installed apps(not containing any OS). The drive is a number of years old and I have never had any problems with it until now.
All of a sudden(after no significant changes to the drive or setup) a few days ago I started getting this error popping up from the start menu.
Delayed Write Failed. Windows was unable to save all data for the file D:/$mft
D:/$mft is displayed at first and if anything is attempted to be accessed afterwards it shows that file instead. Also it sometimes shows D:/. But not at first. I shouldn't have anything being accessed on the drive either. The apps on the drive are all standalone and should only be accessed when I load them. I have looked all around the net for a solution but this seems to be slightly different.
Different because whenever I restart I do not normally get the error on startup and can access the drive fine for quite a while. I can sometimes go hours without getting the error(tho I have gotten the error directly on startup, restarting once more fixes it). It seems to happen randomly, copying files to the drive or deleting files seems to have nothing to do with the timing of the error. My Via RAID Tool will also say the drive is disconnected each time. Now after restarting a number of times since the problem started I have realized that if I leave the computer on for anywhere from 20min to 2 hours+ after getting the error I can get another message from the Via RAID Tool saying the drive was plugged back in and I have no problem accessing it again(tho this does not happen very often). The drive is connected to one of the 2 raid SATA port on my MB. My main drive is in the other raid port(tho they are not set in any array).
I find it strange that if this is a real problem with the hardware, pins or anything similar, that it would not happen at all times. Also the fact that it somehow begins working again just as randomly as the error occurs is beyond me.
Can anyone think of some option having to do with the drive that may need to be changed? Or any possible solution to this? It did not start happening after I started doing anything in specific (such as using it for application installations, going low on space or hardware changes). The drive has had terabytes of data juggled on and off of it over the years at quite a stressful rate I would think, could it just be dieing?
Any help would be greatly appreciated.
K8V-SE Deluxe MB
GeForce 6800 Ultra 256
74GB Raptor WD SATA (internal main drive)
200GB SG SATA (internal 2nd)
250GB WD USB (external 3rd)