Warning: "Encountered an NTFS volume with a logfile that has not been flushed (536)" when taking a Ghost image.
|Article:TECH109633|||||Created: 2007-01-22|||||Updated: 2013-11-06|||||Article URL http://www.symantec.com/docs/TECH109633|
The warning "Error 1969 encountered an NTFS volume that has not been flushed" or "Encountered an NTFS volume with a logfile that has not been flushed (536)" appears when taking an image with Ghost.
"Error 1969 encountered an NTFS volume that has not been flushed"
"Encountered an NTFS volume with a logfile that has not been flushed (536)"
"NTFS Problem Detected (1969) Ghost has detected problems with an NTFS volume. We recommend that you quit Ghost and correct the problem by rebooting NT and running chkdsk. Alternately, you may also continue normally."
Hard drives that contain a boot utility and Extended Industry Standard Architecture (EISA) partitions can cause Ghost to see the partitions as unrecognizable. An improper system shutdown can cause this issue. This has most recently been seen when using Ghost on Windows 8 systems.
Reboot the client machine properly. The next time Ghost is used to access the drive the error should be resolved. If not running the check disk utility and allowing the drive to be scanned will also often resolve this issue. see symantec.com/docs/TECH109636 for more information on resolving NTFS errors using check disk.
After trying the above suggestions it has been reported that when using Ghost version 18.104.22.16870 to create a Windows 8 image from a PE 4.0 environment that these errors may continue. Symantec is aware of and is looking into this situation. As a work around you can select OK and then Continue to create your image. If scripting the execution of Ghost64.exe the use of the "-NTIC" & "-NTIL" command line options to prevent the warning from coming up. Another work around is to turn off the Fast Startup option under Control Panel > Hardware and Sounds > Power Options > System Settings > Shutdown Settings.
Symantec Corporation has acknowledged that the above-mentioned issue with Windows 8 is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Article URL http://www.symantec.com/docs/TECH109633