I am trying the 15-day trial of True Image 7.0 (build 613) and have found it
rather interesting. I am concerned with some errors that are appearing in
the Window's Event Viewer system log.

Specifically, when using the Explore Image and Unplug Image features, the
following appear in the system log:
Error: The Driver detected a controller error on \Device\HardDisk2\D
Warning: The system failed to flush data to the transaction log. Corruption
may occur.

I was wondering if other True Image users have seen these events, and if so
what action(s) they did to remedy them. I realize these errors refer to a
virtual disk TI creates, but they are disconcerting never the less.

System: 3.0G 875P (Asus P4C800-E mobo). Image of (2) SATA drives in RAID-0
config. Image written to new PATA drive. WinXP Home, SP1.

[ Post a follow-up to this message ]

In message <e9pLc.6141$iK.5436@newsread2.news.atl.earthlink.net>,
nineball <nineballnospam@tiac.net> writes

>I am trying the 15-day trial of True Image 7.0 (build 613) and have found i
t
>rather interesting. I am concerned with some errors that are appearing in
>the Window's Event Viewer system log.

>Specifically, when using the Explore Image and Unplug Image features, the
>following appear in the system log:
>Error: The Driver detected a controller error on \Device\HardDisk2\D
>Warning: The system failed to flush data to the transaction log. Corruption
>may occur.

>I was wondering if other True Image users have seen these events, and if so
>what action(s) they did to remedy them. I realize these errors refer to a
>virtual disk TI creates, but they are disconcerting never the less.

I've just checked it using True Image 7.0 (build 611) and have
encountered the same error message, caused by ftdisk.  MS's web site
says:

"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:

I/O requests issued by the file system to the disk subsystem might not
have been completed successfully."

As you point out, this error is concerned with a virtual read-only
drive, so it's probably not really a problem.
--
Martin Jay

[ Post a follow-up to this message ]

Thanks for the reply Martin. I realized the error messages dealt with a
read-only virtual disk, but I wondered if this was just "normal" operation
using TI with WinXP, or if it was unique to my system. As I have a fairly
basic system - not laden down with 3rd party processes and services - I
suspected the errors might be "normal" using TI. As you have also noted,
apparently they are. Today (July 24), I finally received a reply from
Acronis regarding the errors appearing the system log:

"The above errors sometimes happens for Windows XP OS, as it tries to write
some data during mount/unmount processes, but the virtual disk is in
read-only mode, and those errors are shown. "

I also thank you for researching the errors in Microsoft's Knowledge Base.
Actually, I had already researched them using several sources (including MS
KB) and understood their meaning, but for you to take the time to research
and post your results was truly kind on your part. Thanks again!

nineball

"Martin Jay" <martin@spam-free.org.uk> wrote in message
news:6xfot5B5Lq$AFwGf@onenet.org.uk...
> In message <e9pLc.6141$iK.5436@newsread2.news.atl.earthlink.net>,
> nineball <nineballnospam@tiac.net> writes
> 
it[vbcol=seagreen] 
> 
Corruption[vbcol=seagreen] 
> 
so[vbcol=seagreen] 
>
> I've just checked it using True Image 7.0 (build 611) and have
> encountered the same error message, caused by ftdisk.  MS's web site
> says:
>
> "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:
>
> I/O requests issued by the file system to the disk subsystem might not
> have been completed successfully."
>
> As you point out, this error is concerned with a virtual read-only
> drive, so it's probably not really a problem.
> --
> Martin Jay

[ Post a follow-up to this message ]