|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
October 19th 11, 04:45 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
Delayed Write Failed - could I have lost data?
Last night I was copying files from a Windows XP laptop to a USB
external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive? 
|
| Ads |
|
#3
October 19th 11, 06:13 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
What the messages basically meant were that your laptop had been attempting
to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#4
October 19th 11, 06:46 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
|
|
#5
October 19th 11, 06:58 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
The data was in the write cache, it wasn't flushed to the disk so it was
lost when the computer was rebooted. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 John On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#6
October 19th 11, 07:15 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
John John MVP wrote
The data was in the write cache, You dont know that the data he deliberately copied to the USB drive was in the write cache. Its very unlikely that it still was given that he tried to safely remove the hard drive and had the system say that it couldnt do that. That should have flushed the write cache to the drive. Its much more likely that what got lost was what the system was attempting to write to the USB drive at the time the system was hibernated, different data entirely. it wasn't flushed to the disk so it was lost when the computer was rebooted. You dont know that that was the data that he attempted to write to the USB drive. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#7
October 19th 11, 07:48 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
On 10/19/2011 3:15 PM, Rod Speed wrote:
John John MVP wrote The data was in the write cache, You dont know that the data he deliberately copied to the USB drive was in the write cache. It's in the error message... "Delayed Write Failed". Delayed writing is write-behind caching. Its very unlikely that it still was given that he tried to safely remove the hard drive and had the system say that it couldnt do that. That should have flushed the write cache to the drive. Its much more likely that what got lost was what the system was attempting to write to the USB drive at the time the system was hibernated, different data entirely. it wasn't flushed to the disk so it was lost when the computer was rebooted. You dont know that that was the data that he attempted to write to the USB drive. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#8
October 19th 11, 07:55 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
Here is an example of what can happen. I use FreeCommander and may be
copying with 2 windows open. One window with the files I want to copy and the other with USB drive open that I am copying to. After I am done copying if I do not change the drive in USB window some other drive I can not get the USB drive to shutdown because it is being accessed. You did not say how you were copying but if some program is accessing the USB drive you can not remove it because it is not stopped. -- Bill Brought to you from Anchorage, Alaska. wrote: Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive.
|
|
#9
October 19th 11, 08:07 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
John John MVP wrote
Rod Speed wrote John John MVP wrote The data was in the write cache, You dont know that the data he deliberately copied to the USB drive was in the write cache. It's in the error message... "Delayed Write Failed". Nope. Delayed writing is write-behind caching. Yes, but you dont know that its the data he cares about. Its very unlikely that it still was given that he tried to safely remove the hard drive and had the system say that it couldnt do that. That should have flushed the write cache to the drive. Its much more likely that what got lost was what the system was attempting to write to the USB drive at the time the system was hibernated, different data entirely. it wasn't flushed to the disk so it was lost when the computer was rebooted. You dont know that that was the data that he attempted to write to the USB drive. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#10
October 19th 11, 08:11 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
On 10/19/2011 3:55 PM, Bill Bradshaw wrote:
Here is an example of what can happen. I use FreeCommander and may be copying with 2 windows open. One window with the files I want to copy and the other with USB drive open that I am copying to. After I am done copying if I do not change the drive in USB window some other drive I can not get the USB drive to shutdown because it is being accessed. You did not say how you were copying but if some program is accessing the USB drive you can not remove it because it is not stopped. Another notorious one is System Restore which can put a handle that seems to last forever on USB drives, System Restore should be disabled on these drives, or rather I should say that System Restore should only be enabled on the Windows volume and be disabled on all other drives. John
|
|
#11
October 19th 11, 08:19 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
On 10/19/2011 4:07 PM, Rod Speed wrote:
John John MVP wrote Rod Speed wrote John John MVP wrote The data was in the write cache, You dont know that the data he deliberately copied to the USB drive was in the write cache. It's in the error message... "Delayed Write Failed". Nope. Delayed writing is write-behind caching. Yes, but you dont know that its the data he cares about. The OP is the one who knows or should know if data is missing. The error clearly states that the error was on his USB drive (e  But, yes, it could be another process that was trying to write to the disk after the user's data was successfully flushed to the disk. Its very unlikely that it still was given that he tried to safely remove the hard drive and had the system say that it couldnt do that. That should have flushed the write cache to the drive. Its much more likely that what got lost was what the system was attempting to write to the USB drive at the time the system was hibernated, different data entirely. it wasn't flushed to the disk so it was lost when the computer was rebooted. You dont know that that was the data that he attempted to write to the USB drive. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#12
October 19th 11, 10:38 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
John John MVP wrote
Rod Speed wrote John John MVP wrote Rod Speed wrote John John MVP wrote The data was in the write cache, You dont know that the data he deliberately copied to the USB drive was in the write cache. It's in the error message... "Delayed Write Failed". Nope. Delayed writing is write-behind caching. Yes, but you dont know that its the data he cares about. The OP is the one who knows or should know if data is missing. Yes, and its unlikely to have any missing given the detail he spelt out. The error clearly states that the error was on his USB drive (e But, yes, it could be another process that was trying to write to the disk after the user's data was successfully flushed to the disk. And thats much more likely given the detail he spelt out. The first attempt to safely remove the drive should have seen the write cache flushed to the drive. Its very unlikely that it still was given that he tried to safely remove the hard drive and had the system say that it couldnt do that. That should have flushed the write cache to the drive. Its much more likely that what got lost was what the system was attempting to write to the USB drive at the time the system was hibernated, different data entirely. it wasn't flushed to the disk so it was lost when the computer was rebooted. You dont know that that was the data that he attempted to write to the USB drive. These may be helpful: http://www.storagereview.com/guide/cacheWrite.html http://support.microsoft.com/kb/818788 http://technet.microsoft.com/en-us/s...rnals/bb897438 On 10/19/2011 2:13 PM, Tim Meddick wrote: What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. The MFT was fixed by running chkdsk, and the data was probably some inconsequential file written by a background process that enumerates removable media (e.g. Window's Media Player). But I think you got off lightly, the file system could have been damaged beyond repair on the portable drive, and all data on it lost permanently. You should always wait until Windows says that you may safely remove a drive - else, if Windows will allow it, configure the device for quick removal by check-marking the appropriate box in it's Device Manager "Properties" for that drive. == Cheers, Tim Meddick, Peckham, London. :-) wrote in message ... Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive?
|
|
#13
October 19th 11, 11:29 PM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
|
|
#14
October 20th 11, 03:26 AM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
Short answer: You lost data and you will lose more
data until you find out what is wrong and correct that problem. Arno In comp.sys.ibm.pc.hardware.storage wrote: Last night I was copying files from a Windows XP laptop to a USB external hard drive. Then when I tried to safely remove the hard drive, I got an error saying "Generic volume cannot be stopped". I've seen this error before and it goes away if I restart Windows, but this time I didn't want to restart, so I just put my laptop into hibernation, and when I brought it out of hibernation, I was able to safely remove the drive. Then later I copied more files to the USB drive, and when I tried to safely remove it again, I got the "Generic volume cannot be stopped" error again. So I put the laptop into hibernation again, but when I brought the laptop out of hibernation, Windows displayed a dialog box saying: "Delayed Write Failed - Windows was unable to save all the data for the file e:\$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." My USB drive is drive E, and the $Mft apparently stands for master file table. That error seems to say that data was definitely lost, but when I ran a chkdsk on the drive, I got the following output: C:\Documents and Settings\Administratorchkdsk e: /f /v /r The type of the file system is NTFS. Volume label is Elements. CHKDSK is verifying files (stage 1 of 5)... File verification completed. CHKDSK is verifying indexes (stage 2 of 5)... Index verification completed. Cleaning up minor inconsistencies on the drive. CHKDSK is verifying security descriptors (stage 3 of 5)... Cleaning up 12 unused index entries from index $SII of file 9. Cleaning up 12 unused index entries from index $SDH of file 9. Cleaning up 12 unused security descriptors. Fixing mirror copy of the security descriptors data stream. Security descriptor verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 625131831 KB total disk space. 577839972 KB in 1884 files. 1024 KB in 437 indexes. 0 KB in bad sectors. 87383 KB in use by the system. 65536 KB occupied by the log file. 47203452 KB available on disk. 4096 bytes in each allocation unit. 156282957 total allocation units on disk. 11800863 allocation units available on disk. That chkdsk output seems to indicate the drive only had minor inconsistencies and problems with security descriptors. It doesn't say anything about data errors. Is it possible that I still lost data on the drive? -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
|
|
#15
October 20th 11, 09:37 AM
posted to comp.sys.ibm.pc.hardware.storage,alt.comp.hardware,microsoft.public.windowsxp.general
|
|||
|
|||
|
Delayed Write Failed - could I have lost data?
On Oct 19, 10:13*am, "Tim Meddick" wrote:
What the messages basically meant were that your laptop had been attempting to save data to the portable drive, but that in your trying to "out smart" the warning that the "drive could NOT be safely *removed at this time" (or similar), there was corruption of that data that was being written to the drive - *at that time*. I thought that hibernation would force anything in the write buffer to get written to the drive. Seems like it should - isn't hibernation pretty much like the power off state, so all buffers should get flushed just before entering hibernation. Also, what if I wasn't trying to "out smart" the warning? I frequently close the lid on my laptop just before going to bed (and my laptop is configured to hibernate Windows if the lid is closed). So what if I had moved some files to the USB drive late at night and then closed the lid? I might see the "delayed write error" when I bring it out of hibernation the next day - that should not happen. This data corruption was limited to the file that was being written at the time the PC lost power due to the end of the hibernate sequence. *And also, the MFT would have lost it's validity due to the fact it could not be updated after the loss. I'm curious how large the Windows write buffer is - just wondering if any possible corruption could be limited to a partial file, or multiple files if the buffer is large enough. Fortunately I know the last several files I moved over to the drive - most of them are files I downloaded off the internet, so I can redownload those just in case. But the last file I moved over was a text file I had been editing, and it appears to be OK... unless the corruption has manifested itself in truncating the end of the file - I don't quite remember what was at the end of the file.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
