Chkdsk and Acronis
Hello everyone,
I use TIH 2011 on win7 64 bit prof and i have the following problem:
One Backup Job in Acronis starts a batch (before Command in the Joboptions) and in this batch chkdsk for drive C: will be started and that's it.
My Problem is now that when i run this batch by doubleclicking on it - chkdsk finisches and there is no problem. If the same batch gets started from Acronis it showed me 2 times in a row that there are some errors and "volumebit" was damaged. The third time it showed no errors.
What is behind this? Which over processes could be using my harddrive or are there real problems with the NTFS Filesystem?
Hi GroverH,
maybe i should clarify. You can start chkdsk from batch with this:
chkdsk c:
You will not need to restart (i think you mixed this up with chkntfs).
This command is not my problem. My problem is when i create an acronis job and in the options of this Acronis-Job in the "before/after command" (my version is german so forgive poor translation) i type in this batch file (with the chkdsk) then chkdsk runs but say that another process is running and that this might be influencing the result. And then the result usually shows that "there were errors" which doesn't show when i just run the batch without acronis. So is Acronis somehow interfering chkdsk? Or what does this mean?
Most likely Acronis is interfering with chkdsk.
So that you know, from a backup perspective, running chkdsk without the /r option is not very useful. That option will require a lock on the disk. If I were you, I wouldn't put chkdsk in a batch before a backup. I would run backups much more often than I would run chkdsk. That is only me.
What actions are you expecting "ChkDsk C:" to perform?
Running "chkdsk c:" without any parameters is telling chkdsk to run in scan mode only and running scan mode does not fix any file errors or disk errors.
1: If you want chkdsk to scan for errors but not fix the errors. then the command is
chkdsk c:
2: If you want chkdsk to find and fix file errors, then the fommand is
chkdsk c: /f
3: If you want chkdsk to find and fix disk errors (file errors also fixed), then the command is
chkdsk c: /R
When checking the system disk for disk errors, Windows will only do this as part of a startup. This is not an limitation of TrueImage but a limitation of Windows wanting complete control of the disk before fixing any errors.
---------------------------------------------
If you want TrueImage to run any of these batch files, here are examples.
If you create a batch file with a cmd extension, you can place a link to that cmd file inside the TrueImage "Pre/post post command option. From inside the post command, you need to use the browse function and browse to the actual cmd file such as c:\chkdsk-test.cmd
Here are 3 examples of what the contents of the c:\chkdsk-test.cmd file might be using either of these 3 scenarios:
Example 1: Batch file contents ---chkdsk scan mode only-----------------
@echo off
echo.
echo Chkdsk has been instructed to start
echo ..Wait a minute or so for the scan only to complete. after command window closes,
echo...scan results can be found 'c:\chkdisk-scan-results.txt
echo.
chkdsk C: >c:\chkdisk-scan-results.txt
@exit
(Note: Command window willl open and will automatically close after scan only is complete. Results of scan found in the c:\chkdsk-scan-results.txt file.)
Example 2: Batch file contents ---check/fix file errors -----------
@echo off
echo.
chkdsk C: /f
@exit(note command window will open and user will need respond to prompt grantting or refusing permission to chkdisk to run and fix the file errors on next bootup. Command window will close and the Acronis backup will complete. However, until the user reboots after backup, no chkdsk will run and no file errors fixed until after the reboot.)
Example 3: Batch file contents check/fix disk (& file) errors---------------
@echo off
echo.
chkdsk C: /R
@exit(note command window will open and user will need respond to prompt grantting or refusing permission to chkdisk to run and fix the disk errors on next bootup. Command window will close and the Acronis backup will complete. However, until the user reboots after backup, no chkdsk will run and no errors fixed until after the reboot.
A listing of available commands about chhdsk can be found from a command prommpt
c:
chkdsk /?
For testing, the results will be the same whether you execute the cmd file from within TrueImge or from a desktop or command prompt.
Hi PatL and Grover,
Pat L you were right - its acronis it is propably locking some space on the disk (maybe securezone). So my solution was that chkdsk will run in a .cmd file before Acronis.
For The talk about /r: well it will not "Save" the backup, but i feel much more secure if chkdsk runs daily and checks for Filesystem errors. I needed to reinstall my machine because a Filesystem Error silently started to "poison" all my Images - since you will not notice it it will destroy all your images and after a year you can start over fresh.
P.S. Personally I want to know first what's going on and then maybe using /f or even /r. Truth is most the time: chkdsk wont save you for the long haul...