P
powerwalk
Every time I backup to my Seagate FreeAgent USB external drive, I get the
following System error message in the Event Viewer. The same message appears
when I mount and unmount an image in read only mode using Acronis True Image
11. I receive the same message when backing up my almost new laptop with
identical specs.
XP Pro, 2 Gigs RAM, Drive is 91% free. I haven't experienced any problems
with the computers or External Drive for six months but the message does
sound ominous.
Source: Ftdisk Event ID 57 Category: Disk
The system failed to flush data to the transaction log. Corruption may occur.
Microsoft TechNet has the following Explanation and suggests running Chkdsk.
I have run chkdsk, but i fails to solve the problem
Explanation
NTFS could not write data to the transaction log. This could affect the
ability of NTFS to stop or roll back the operations for which the transaction
data could not be written. NTFS could not write data because of one or more
of the following reasons:
1. I/O requests issued by the file system to the disk subsystem might not
have been completed successfully.
Any thoughts on the above will be appreciated. Thanks
following System error message in the Event Viewer. The same message appears
when I mount and unmount an image in read only mode using Acronis True Image
11. I receive the same message when backing up my almost new laptop with
identical specs.
XP Pro, 2 Gigs RAM, Drive is 91% free. I haven't experienced any problems
with the computers or External Drive for six months but the message does
sound ominous.
Source: Ftdisk Event ID 57 Category: Disk
The system failed to flush data to the transaction log. Corruption may occur.
Microsoft TechNet has the following Explanation and suggests running Chkdsk.
I have run chkdsk, but i fails to solve the problem
Explanation
NTFS could not write data to the transaction log. This could affect the
ability of NTFS to stop or roll back the operations for which the transaction
data could not be written. NTFS could not write data because of one or more
of the following reasons:
1. I/O requests issued by the file system to the disk subsystem might not
have been completed successfully.
Any thoughts on the above will be appreciated. Thanks