acronis true image operation failed (windows 10 x64)
Greetings:
Now, before anything: i am not used to Acronis.
I used Norton's Ghost before, but this one fails at Windows 10 x64.
Thus, I got me a new system, Acronis, and made me a bootable CD that runs Acronis offline so I have an actual FULL copy of my prime partitions.
However: when I try to make a backup, Acronis stops at 1/6th the operation, telling me it cannot read from the HD.
Ran a whole plethora of Disk Scans (Norton Utilities, Tune Up Disk Doctor, Window's own Checkdisk system, and a few more, but none of them can find a single problem.
Ran Acronis Boot CD again, error persists.
Ran Acronis from Windows out, error persists.
Rechecked the HDD with the whole plethora of Disk Scans, nothing found.
I'm thinking, and correct me if I am wrong, that Windows 10 Pro x64 has an encrypted part which cannot be back-upped by Acronis, is this possible?
This idea originates from the fact my HDD is physically OK, the data is OK, but still back up fails, always at the same position.
Sadly, all I get is a sector address, but the program does not tell me which file it fails on, or what folder the fail creates, thus I am lost in the what/where, so...
This was a serious advantage that Ghost had: it always told what file it failed on, if it failed.
Which, before Windows 10, never did...
I do know that Ghost has a problem with something like that, but seeing Acronis is a much newer toy, I can hardly believe that.
Is there a way to overcome this issue?
I REALLY need to make a backup of my new installment, now that Ghost can't handle Windows 10 anymore.
I REALLY hope I did not buy a faulty backup system.... :(
thank you beforehand:
Luke
In addition to Steve's sound advice, if the backup continues to get stuck at the same place, try selecting the option to ignore bad sectors... I don't have my bootable media readily available, but I belive it is an advanced option in the backup task under the backup method (as is also a feature in the Windows version of the backup task)
http://www.acronis.com/en-us/support/documentation/ATI2016/#269.html
Error handling
When the program encountered an error while performing backup, it stops the backup process and displays a message, waiting for a response on how to handle the error. If you set an error handling policy, the program will not stop the backup process, but will simply handle the error according to the set rules and continue working.
You can set the following error handling policy:
- Do not show messages and dialogs while processing (silent mode) - Enable this setting to ignore errors during backup operations. This is useful when you cannot control the backup process.
- Ignore bad sectors - This option is available only for disk and partition backups. It lets you successfully complete a backup even if there are bad sectors on the hard disk.
We recommend that you select this check box when your hard drive is failing, for example:
- Hard drive is making clicking or grinding noises during operation.
- The S.M.A.R.T. system has detected hard drive issues and recommends that you back up the drive as soon as possible.
When you leave this check box cleared, the backup may fail because of possible bad sectors on the drive.
Hail, and thank you.
Downloaded ReadLog.
Scandisk was done with /X/F/R.
Not a clue what BitLocker is?
Once I can I will put up the requested info.
I'm a father of 5 kids, soooo... time can be quite an issue...
Regards:
Luke
Thank you, Sir.
I have not been screwing around on Acronis'settings, since I am not familiar with the program.
I'll go fire it up once I can and have a look.
Regards:
Luke
Right now my system is doing a thourough disk check, having 12 and a bit TB on drives, this took me most of the day, and the night through.
I will get back once this is done. :)
Thank you again:
Regards:
Luke
ReadLog info:
task_name=W10Pro-X64 (C)
Start= 12/07/2016 19:55:55
id=1; level=2; module=100; code=0; date/time=12/07/2016 19:55:55
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2; level=2; module=100; code=2; date/time=12/07/2016 19:55:55
message=Operation W10Pro-X64 (C) started manually.
id=3; level=2; module=100; code=0; date/time=12/07/2016 19:55:55
message=Operation description: Stage Description.
id=4; level=2; module=100; code=0; date/time=12/07/2016 19:56:00
message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=5; level=2; module=316; code=0; date/time=12/07/2016 19:56:00
message=Operation: Backup
id=6; level=2; module=100; code=11; date/time=12/07/2016 19:56:01
message=Priority changed to Low.
id=7; level=2; module=11; code=1008; date/time=12/07/2016 19:56:02
message=Create Backup Archive From: W10Pro-X64 (C:) To file: L:\BACKUP P8Z77-L vx\W10Pro-X64 (C).tib Compression: Normal Exclude: Files matching mask Match criterion:
hiberfil.sys
pagefile.sys
$Recycle.Bin
swapfile.sys
System Volume Information
*.tib
*.tib.metadata
*.~
*.tmp
*.db3-journal
C:\Users\Admin\AppData\Local\Temp
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Local\Temp
C:\Users\Admin\AppData\Local\Microsoft\Windows\INetCache
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Local\Microsoft\Windows\INetCache
C:\Users\Admin\AppData\Local\Google\Chrome\User Data
C:\Users\Admin\AppData\Local\Opera Software
C:\Users\Admin\AppData\Roaming\Opera\Opera
C:\Users\Admin\AppData\Local\Mozilla\Firefox\Profiles
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Local\Google\Chrome\User Data
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Local\Opera Software
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Roaming\Opera\Opera
C:\Users\Administrator.DESKTOP-KNH5JTI\AppData\Local\Mozilla\Firefox\Profiles
C:\Windows\CSC
id=8; level=2; module=1; code=504; date/time=12/07/2016 19:56:02
message=Pending operation 160 started: 'Creating partition image'.
id=9; level=2; module=100; code=0; date/time=12/07/2016 19:57:17
message=Writing full version to file: W10Pro-X64 (C)_full_b1_s1_v1-2.tib
id=10; level=4; module=1; code=510; date/time=12/07/2016 19:58:11
message=Failed to read data from the disk.; line_tag=0x65B5EB7011094665
Error_Code=Af4BAQBlRgkRcOu1ZUZhaWxlZCB0byByZWFkIGRhdGEgZnJvbSB0aGUgZGlzay4AJG1vZHVsZQBOAAAAAAAAAAAAWsQQALOeuHbjBOw/RmFpbGVkIHRvIHJlYWQgdGhlIHNuYXBzaG90LgAkbW9kdWxlAE4AAAAAAAAAAABVARAAr1K4KnvLqgJDUkMgZXJyb3IuACRtb2R1bGUATgAAAAAAAAAAAA==
id=11; level=4; module=16; code=50266; date/time=12/07/2016 19:58:11
message=Failed to read the snapshot.; line_tag=0x3FEC04E376B89EB3; hide=1
id=12; level=4; module=16; code=341; date/time=12/07/2016 19:58:11
message=CRC error.; line_tag=0x2AACB7B2AB852AF; hide=1
id=13; level=4; module=1; code=502; date/time=12/07/2016 19:58:30
message=Read error; line_tag=0x65B5EB7011094700
Error_Code=AfYBAQAARwkRcOu1ZVJlYWQgZXJyb3IAJG1vZHVsZQBOAAAAAAAAAAAAAwAHACRQ7HQs2oHfUmVhZCBlcnJvcgAkbW9kdWxlAE4AAAAAAAAAAABaxBAAs564duME7D9GYWlsZWQgdG8gcmVhZCB0aGUgc25hcHNob3QuACRtb2R1bGUATgAAAAAAAAAAAFUBEACvUrgqe8uqAkNSQyBlcnJvci4AJG1vZHVsZQBOAAAAAAAAAAAA
id=14; level=4; module=7; code=3; date/time=12/07/2016 19:58:30
message=Read error; line_tag=0xDF81DA2C74EC5024; hide=1
id=15; level=4; module=16; code=50266; date/time=12/07/2016 19:58:30
message=Failed to read the snapshot.; line_tag=0x3FEC04E376B89EB3; hide=1
id=16; level=4; module=16; code=341; date/time=12/07/2016 19:58:30
message=CRC error.; line_tag=0x2AACB7B2AB852AF; hide=1
id=17; level=4; module=485; code=35; date/time=12/07/2016 19:58:30
message=File system error is found. Consider checking the disk using Check Disk Utility.; line_tag=0x4D3F22948E29F1E8
Error_Code=ASMA5QHo8SmOlCI/TUZpbGUgc3lzdGVtIGVycm9yIGlzIGZvdW5kLiBDb25zaWRlciBjaGVja2luZyB0aGUgZGlzayB1c2luZyBDaGVjayBEaXNrIFV0aWxpdHkuACRtb2R1bGUATgAAAAAAAAAAAAMABwCDUGxrMEC9kVJlYWQgZXJyb3IAJG1vZHVsZQBOAAAAAAAAAAAAAwAHACRQ7HQs2oHfUmVhZCBlcnJvcgAkbW9kdWxlAE4AAAAAAAAAAABaxBAAs564duME7D9GYWlsZWQgdG8gcmVhZCB0aGUgc25hcHNob3QuACRtb2R1bGUATgAAAAAAAAAAAFUBEACvUrgqe8uqAkNSQyBlcnJvci4AJG1vZHVsZQBOAAAAAAAAAAAA
id=18; level=4; module=7; code=3; date/time=12/07/2016 19:58:30
message=Read error; line_tag=0x91BD40306B6C5083; hide=1
id=19; level=4; module=7; code=3; date/time=12/07/2016 19:58:30
message=Read error; line_tag=0xDF81DA2C74EC5024; hide=1
id=20; level=4; module=16; code=50266; date/time=12/07/2016 19:58:30
message=Failed to read the snapshot.; line_tag=0x3FEC04E376B89EB3; hide=1
id=21; level=4; module=16; code=341; date/time=12/07/2016 19:58:30
message=CRC error.; line_tag=0x2AACB7B2AB852AF; hide=1
id=22; level=4; module=316; code=5; date/time=12/07/2016 19:58:33
message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE51
Error_Code=AQUAPAFRzosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAE4AAAAAAAAAAAA=
Start= 12/07/2016 19:55:55
Finish= 12/07/2016 19:58:33
Total Time= 00:02:38
I'm going to retry to make a new backup, now that the extensive disktest has completed, it did not find any problems, again...
Spinrite and a HDD specific tool.
This one comes from WD (having WD drives).
Most peculiar:
As said, the plethora of HDD scanners/fixers did not find a thing.
Now, just before I was to retry, new updates rolled in for Win10Pro_x64.
Did these, restarted, removed backups through AVGTune Up utilities, did a Perfect Disk defrag (I like CLEAN backups, note), restarted with the offline backup CD, knowing it would again fail at sector 10million and some, but...
'Lo and behold, the backup finished perfectly?
Don't get me wrong, but, this is most peculiar, no?
Not a single hickup, nothing.
I'm SO glad now, I can FIANALLY begin to work...
Anyone with a theory about this?
Mine, currently, is that a previous update botched up a few things, giving a false error (or a string of data that acronis perceived as 'bad'), and the update fixed this.
Not a clue what else it could be as the HDD's hardware is in perfect condition (according to the plethora of tools I ran on it).
Thank you for the assist, gentlemen, I am VERY grateful.
Regards:
Luke.
Luke, thanks for the log file information, this confirms what you said about the problem in your initial post, that there is a disk read issue here.
id=9; message=Writing full version to file: W10Pro-X64 (C)_full_b1_s1_v1-2.tib
id=10; message=Failed to read data from the disk.;
id=11; message=Failed to read the snapshot.;
id=12; message=CRC error.;
id=13; message=Read error;
id=14; message=Read error;
id=15; message=Failed to read the snapshot.;
id=16; message=CRC error.;
id=17; message=File system error is found. Consider checking the disk using Check Disk Utility.;
id=18; message=Read error;
id=19; message=Read error;
id=20; message=Failed to read the snapshot.;
id=21; message=CRC error.;
id=22; message=Operation has completed with errors.;
The most likely source of the above errors is in the volume space used by Microsoft VSS to create / store the snapshot data - hence the errors for reading the snapshot.
When you have this error, open a Windows Command prompt as Administrator, then issue the command:
vssadmin list shadows
This will give you output like mine below and confirm which drive is being used by VSS for snapshot, and which you have a potential disk issue with.
C:\WINDOWS\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {e3cdf014-9f87-457e-a128-7f395f0a522a}
Contained 1 shadow copies at creation time: 08/07/2016 20:03:57
Shadow Copy ID: {c9939b01-a848-4e8d-bf56-135e36c803f4}
Original Volume: (C:)\\?\Volume{427b688c-77d9-11e4-be65-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: DellStudio
Service Machine: DellStudio
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Contents of shadow copy set ID: {2a5f713e-86b2-4eea-a0ac-043fb9c5de4b}
Contained 1 shadow copies at creation time: 13/07/2016 18:44:51
Shadow Copy ID: {4c9cffde-86ad-4043-8413-3abe61e0e39b}
Original Volume: (C:)\\?\Volume{427b688c-77d9-11e4-be65-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: DellStudio
Service Machine: DellStudio
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
Luke, if you have done an offline backup using the rescue media, then VSS is not involved as no Windows OS is active to provide it.
I figured as much, as per the original post, I tried a few offline backups, failing.
Figured to try online, failed as well.
The myriad of tools ran never detected a problem, nothing got fixed, but after the update all suddenly became 'repaired'for some reason.
Hence I figured one of these updates were botched up in some way, and Acronis was not able to read the bad update?
I'm somewhat stunned over this...
I do not believe in Jedi'ism (being passive), as passiveness solves less than nothing, but somehow this error seemingly got passively fixed nonetheless.
*scratches head*
PS: being autistic (Asperger-Savant) I am very analytical, and I have this "need" to understand things, hence I try to get some info on the matter.
I hope, you will not drive me over for this, or boil me into soup, knowing that quite a few people do not like to explain things like this... XD
Regards:
Luke
Was your last Windows update KB3172985? This update fixed some issues with the Windows kernel and Windows Update which uses the VSS service. The following is an excerpt from Microsoft for this update:
Fixed additional issues in .NET, Windows Kernel, Windows Update, authentication, revised daylight saving time, support for PDF files, Bluetooth, Microsoft Edge, Internet Explorer 11, networking, and Wi-Fi connectivity.
It is resonable to assume that filesystem errors would be corrected in this update so my guess is that yes, the update got things back to normal for you.
How bloody marvelous, good sir, that you could confirm my suspicions.
I was so hoping it was not Acronis, and thank God, it ain't.
Thanks to all of you at Acronis I have a great, working backup again.