Try&Decide causes CheckDisk to run on reboot

After using Try&Decide I tell True Image 11 to discard any changes, and it reboots the computer. For some reason, this causes the C: drive to be scanned for errors while rebooting (runs CheckDisk). This happens every time. The manual doesn't say anything about this, so I don't think it's normal. Has anyone else had this problem? Thanks

 

Which build of TI 11 are you using and what OS?

Colin

 

I'm using Windows XP SP2 and TIH 11 build 8,022 (retail disk).

 

8,022 must have been a pre-pre-release...

You might try and update to the latest build (8,053/8,054) and see if it works properly for you.

 

I'm on a dial-up connection, so it's hard to download the update (don't know why it has to be so huge). I looked at the list of changes for build #8053, and didn't see any mention of this problem. Has anyone seen this problem with the latest version?

 

Hi Giarc I also use dial-up (sigh) and experience the same problem. What I have done in the past is when I am in the City ( country bunkin here) I go to a friends place who has high speed and login on Acronis site and enter my password and download the latest build using my friends highspeed internet service. I know it is a real pain but what can we do?

 

I don't think build 8022 was a beta version - is this a foreign language version or OEM perhaps?

Anyhow, I assume you have put the SZ on the 'C:' drive. Is your computer a brand name of a Heinz 57 type?

XP does automatically run checkdisk on boot unless disabled, but obviously something is upsetting it.

The reason for asking if this is a brand name computer is in case they've got a utility running in the background.

Colin

 

I am using the boxed retail version that comes with an actual CD. It is NOT a beta version, OEM or foreign language version.

My computer is custom built, not a brand name. There is no background utility causing this problem, it is being caused by True Image. XP only scans the C: drive after I have used Try&Decide and reboot. It never did this until I installed TI and used the Try&Decide feature.

The Secure Zone is on the same hard drive as the C: partition, but it is of course in it's own logical partition completely separate from the C: partition.

Are you using XP? What version of TI are you using? Have you ever seen this problem?

 

I use XP and TI 11 8054.

XP does normally do a background test - if you add /SOS to the end of your /FASTDETECT in boot.ini - you'll see it doing a quick 'disk clean' check.

Although Acronis don't recommend it, put the SZ on the external drive and direct the T&D to play there. See if rebooting with the external drive on, causes the same behaviour.

It might be worthwhile stopping and disabling the T&D in services - and see if the problem persists. If it does, try doing the same with scheduler and scheduler2.

There was an SP2 patch in one of the MS updates for a chkdsk problem - though this was to do with the Windows scheduling.

Colin

 

Thanks bodgy for the reply, however, I think you may have the wrong impression. XP does not run ChkDsk every time I boot the computer, it only does it once after using the Try&Decide feature. When TI reboots the computer, XP will scan the system partition at that time, but if I boot again then it's just fine.

I would really just like to know if others have this problem. Since you are running the latest build of TI 11 on XP, can you tell me if you see this problem after using Try&Decide?

 

No I don't have this problem, but my T&D is now on an external drive after testing with a previous version.

What I'm trying to say, is my copy of XPpro with SP2 runs a quick and silent chkdsk at boot time - normally obscured by the Windows boot screen - if the SOS switch is enabled - you actually see on the screen the quick check, and then the list of drivers being loaded. I'm pretty sure this is standard XP behaviour. It will certainly run chkdsk if it believes the disk has sector problem.

Have you tried stopping an disablingthe T&D service -and see if the problem still happens on reboot?

Colin

 

Sorry, but I really don't understand what you are trying to say or how all this helps me any. I'm sure my "SOS switch" is not the problem. When my computer reboots after using T&D I do not see a "quick and silent chkdsk", I see a big blue screen informing me that Windows is going to scan my C: partition for errors. About 5 or 10 seconds later, the scanning begins.

No, I haven't tried that. As I said, this problem only happens after using T&D. If the T&D service is disabled, then obviously I cannot run the T&D feature. And I'm not going to try and stop the service while my computer is in the try mode and the service is being used.

 

Ah sorry, I'd misread, I thought your problem was - that chkdsk keeps running at boot time, everytime, since you first used the T&D.

Did you have any problems making the Secure Zone?

I'll attempt a T&D tonight when I get in and see if I get a problem.

I'm not saying your SOS switch is the problem - most people don't have it active anyway. I was just suggesting you implement it, because you'd then see that chkdsk does auto run on any boot except hibernation or standby.

 

OK, it would be useful to know the exit code that chkdsk throws, but that'll be far too bothersome.

The problem is caused by a companion piece of software - fsutil. If XP thinks it has been rebooted without shutting down it sets the 'dirty' bit on the hardrive, thus making FSutil run chkdsk.

in a command box type in fsutil dirty query C: see what response you get. Do it before using T&D and then again after T&D, but before rebooting the computer.

A thought has just occured to me, you are aware that T&D doesn't work with programs that require a reboot after install?

A possible workaround - again in a command box type in chkntfs /x c: this forces fsutils and chkdsk to ignore the dirty bit and or the timed countdown for system file checking at boot time.

If you just type chkntfs c: it will tell you if it has auto checking set.

Colin

 

I decided to try Try&Decide, in order to decide if my try would create the ChkDsk problem.

v11 Build 8,053

1. Created a Secure Zone on HDD Disk 1 which also contain the System Partition. Rebooted. The Secure Zone came out of Partition E: on this HDD 1.
2. Activated Try&Decide, installed some programs.
3. Went to task bar icon, right click, undo changes. Rebooted.

ChkDsk did not fire at any point. Got a plain vanilla WinXP MCE OEM.

Maybe it is a problem with that earlier build of True Image. Got my copy of TI by downloading not long ago.

It's like Try&Decide somehow alter the Partions you got, enough to trigger a ChkDsk at boot. A bit weird that a Store Bought TI feature contain such fault. Would be best if someone with the same build could confirm the same ChkDsk trigger.