Failed Recovery - "The end of the file has been reached." 0x00040002+0x00040002
Before I start, I just wanted to quickly say that I have been using Acronis Software for over 10yrs now, and have been generally satisfied with its performance. That would not have been possible without this forum, which I have leaned on many times gaining valuable insight and wisdom from the knowledge shared here. So, I just wanted to say Thank You to all of the Volunteers & Contributors, for all your time and wisdoms over all these years has helped me many times.
Quick Summary:
This issue deals with the failed recovery attempts of a recent backup created with Acronis True Image 2015_Build_6613. The backup is comprised of 2 files, [Entire PC (JASONWIN8)_full_b1_s1_v1.tib] & [Entire PC (JASONWIN8)_full_b1_s1_v2.tib]; and the target of the recovery is the original disk.
The backup validates every time in ATI 2015, across all platforms(windows console/usb rescue media/iso bootable rescue cd); but recovery always fails with the error: [ message="The end of the file has been reached." A possible reason may be poor media quality. Event code: 0x00040002+0x00040002].
The recovery has been attempted many times across all platforms of Acronis True Image 2015 and later with 2016_Build_6571<explained later>. Tried new USB 3.0/2.0 interface cables and several different USB ports on machine.
I have been working with Acronis Support Engineer case# [02752383] for over a week now and tech has remotely connected to my sys. several times for many hours; but have been unable to figure out what is going on. The tech tried with ATI 2015 first and then later installed ATI_2016 on my system. He has been consulting with his resources he says, but to no avail. Last Friday, after exhausting all his resources, he informed me he would be escalating the case up the line. So now I am just waiting for someone to contact to me.
-Support seems to be focused on the finding something wrong with my hardware, running CHKDSK /F /R on both source and the backup target disks(external HDD) multiple times; and the result is always “no errors found”
- sfc /scannow “did not find any integrity violations”
I have included screenshots & logs from both ATI 2015/2016.
Any other info needed I am happy to provide & thanks for your consideration.
I am starting to realize that recovery may not be possible, although I still hold out hope. That is the reason for this post, in hopes maybe a “fresh pair of eyes” may have some more information on my issue.
------------------------------------------------------------------------------
My System: UEFI Windows 10 Pro v. 10.0.10240 x64
Backup Source: GPT Samsung SSD 850 PRO 1TB
Backup Target: Toshiba 1TB HDD, interface USB 3.0 – attached directly to serial port at back of computer.
Created Backup Using Acronis True Image_2015 for PC_Build_6613
Add Backup>Entire PC>Do not Schedule>Incremental>Create only incremental versions after the initial full version>Backup protection>added Password>Validate backup when it is created
Backup Operation begins – runs for 5mins- forgot about a folder I wanted to exclude>canceled Backup>added folder to exclusion list(did not contain hidden or system files>Start Backup>Backup runs for about 1 hour>Validates w/ green checkmark(hover over “Backup is Valid)>Close Acronis PC console>Safely remove external usb HDD>Reboot
This created this Backup sequence composed of 2 .tib files v1 and v2.
Backup is completely viewable in explorer and all files are there.
Open Acronis PC console>Re-attach external usb HDD> >right click Backup>Validate>”The Backup is Valid”>Safely remove external usb HDD
- -Created USB Flash Drive Bootable Media
Tools>Rescue Media Builder>Acronis bootable rescue media>USB flash drive>Proceed
- -Created ISO Bootable Media
Downloaded from “My Account” //dl.acronis.com/s/AcronisTrueImage2015_en-EU.iso
Checksum: fd2b9af0487070f3a62f3c728f99acfc
Performed a Secure Erase on system disk - Samsung SSD 850 PRO>Succesful>Initialize Disk>Reboot
**Disk initialized, space left unallocated
Attempted Recovery system to the same/original disk using ATI 2015 USB Rescue Media in UEFI Mode
BIOS>Boot Menu> [UEFI] USB Acronis bootable rescue media>1. ATI 2015>Recover My Disk>Browse for Backup, Select Backup>Recover whole disk and partitions>
1st attempt: selected everything but ‘MBR and Track 0’
2nd attempt: selected the entire system disk 1
Destination of Disk 1>Samsung ssd 850 pro
**Between myself and Acronis support tech, we tried this procedure over all platforms(console/usb/iso cd), but the results were always the same.
Here is the log from that attempt:
<?xml version="1.0" encoding="UTF-8" ?>
<logs>
<log build="6613" product="True Image" task_name="Recover" uuid="19ECCDD8-04C7-9558-94F9-A164C1ADF0A8" version="18.0">
<event code="0" id="1" level="2" message="Operation "Recover" started." module="100" time="1469031569" />
<event code="1020" id="2" level="2" message="<bold>Recover Backup Archive</bold><endl/><tabpoint value=30><indent value=4>From file:	<indent value=10><textcolor value="navyblue">"E:\Acronis Backups\Entire PC (JASONWIN8)_full_b1_s1_v2.tib"</textcolor></indent><indent value=4><endl/>Recovery of:	<indent value=10><textcolor value="navyblue">Disks</textcolor></indent><indent value=4><endl/></indent><endl/>" module="11" time="1469031569" />
<event code="504" id="3" level="2" message="Pending operation 13 started: 'Recovering partition'." module="1" time="1469031569" />
<event code="2" id="4" level="2" line_tag="0x1D8EAB676A3F695B" message="The end of the file has been reached." module="4" time="1469031653">
<field name="Path" type="TString" />
<field name="$module" type="TULong64">0</field>
<event code="2" id="5" level="2" line_tag="0x4B5D8963CBCE4429" message="The end of the file has been reached." module="4" time="1469031653" />
</event>
<event code="504" id="6" level="2" message="Pending operation 59 started: 'Recovering MBR'." module="1" time="1469031706" />
<event code="0" id="7" level="2" message="Mapped from Disk NtSignature - -1818874834 to Disk NtSignature - -1818874834" module="57" time="1469031707" />
<event code="0" id="8" level="2" message="Mapped from Disk NtSignature - 349175815 to Disk NtSignature - 349175815" module="57" time="1469031707" />
<event code="0" id="9" level="2" message="Mapped from Disk GUID - 484A3F83-7350-4CC0-A10E-B561A53D8C35 NtSignature - -995318281 to Disk GUID - BB729E16-560D-49EF-AD9E-86A63192C6C4 NtSignature - 1388617178" module="57" time="1469031707" />
<event code="0" id="10" level="2" message="Bootability restore operation has started." module="29" time="1469031707" />
<event code="0" id="11" level="2" message="Bootability restore operation has finished." module="29" time="1469031707" />
<event code="252" id="12" level="2" message="Recover operation succeeded." module="100" time="1469031707" />
</log>
</log>
----------------------------------------------------------------------------------------------------------------------------
Using Acronis True Image_2016 for PC Build: 6571
*Recovery also fails, same error msg.
*Unable to mount archive to Internal SSD or in VmWare/VHD
Log below:
log uuid=23297D51-9704-466F-AE67-B119751FC406; product=True Image; version=19.0; build=6571; task_name=Mount image
Start= 7/23/2016 4:57:11 PM
id=1; level=2; module=100; code=0; date/time=7/23/2016 4:57:11 PM
message=Path to image: D:\Acronis Backups\Entire PC (JASONWIN8)_full_b1_s1_v1.tib
id=2; level=2; module=100; code=0; date/time=7/23/2016 4:57:11 PM
message=Drive letter: H; Access mode: Read-only
id=3; level=4; module=100; code=242; date/time=7/23/2016 4:57:22 PM
message=Cannot assign a drive letter to a partition from the backup archive.; line_tag=0xE3D108407D4CA4
Error_Code=AfIAZACkTH1ACNHjAENhbm5vdCBhc3NpZ24gYSBkcml2ZSBsZXR0ZXIgdG8gYSBwYXJ0aXRpb24gZnJvbSB0aGUgYmFja3VwIGFyY2hpdmUuACRtb2R1bGUAQXRydWVpbWdfaG9tZV92c182NTcxACRmaWxlAEFrOlw2NTcxXHByb2R1Y3RzXGltYWdlclxob21lXHdpemFyZHNcd2l6YXJkX21vdW50LmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpXaXphcmRzOjpNb3VudFdpemFyZDo6RG9Nb3VudFBhcnRpdGlvbnMAJGxpbmUATnoDAAAAAAAAAAMABwAWlcrLZ9G9LFJlYWQgZXJyb3IAJG1vZHVsZQBBdHJ1ZWltZ19ob21lX3ZzXzY1NzEAJGZpbGUAQWs6XDY1NzFccmVzaXplclxnZW5lcmljXGZzLmNwcAAkZnVuYwBBcmVzaXplcjo6RlNQcm9jZXNzb3I6OlJlYWQAJGxpbmUATmIAAAAAAAAAACAABwB3SdBEwfzseVRoZSBiYWNrdXAgaXMgY29ycnVwdGVkLCBidXQgeW91IGNhbiBzdGlsbCB0cnkgdG8gcmVjb3ZlciBkYXRhIGZyb20gaXQuACRtb2R1bGUAQXRydWVpbWdfaG9tZV92c182NTcxACRmaWxlAEFrOlw2NTcxXHJlc2l6ZXJcYmFja3VwXHJhbmRvbV9hY2Nlc3MuY3BwACRmdW5jAEFyZXNpemVyOjpSYW5kb21BY2Nlc3NTdHJlYW06OkxvYWRTZXF1ZW50aWFsQ2h1bmsAJGxpbmUATuYCAAAAAAAAAA0ABAAgAeH07OAXZVRoZSBmaWxlIGlzIGNvcnJ1cHRlZC4AJG1vZHVsZQBBdHJ1ZWltZ19ob21lX3ZzXzY1NzEAJGZpbGUAQWs6XDY1NzFcYmFja3VwXGFyY2hpdmVfcmVhZGVyLmNwcAAkZnVuYwBBYmFja3VwbWVkaWE6Ok11bHRpRmlsZUFyY2hpdmVSZWFkZXI6OkRvUmVhZAAkbGluZQBOYQEAAAAAAAAA
id=4; level=4; module=7; code=3; date/time=7/23/2016 4:57:22 PM
message=Read error; line_tag=0x2CBDD167CBCA9516; hide=1
id=5; level=4; module=7; code=32; date/time=7/23/2016 4:57:22 PM
message=The backup is corrupted, but you can still try to recover data from it.; line_tag=0x79ECFCC144D04977; hide=1
id=6; level=4; module=4; code=13; date/time=7/23/2016 4:57:22 PM
message=The file is corrupted.; line_tag=0x6517E0ECF4E10120; hide=1
id=7; level=4; module=100; code=242; date/time=7/23/2016 4:57:22 PM
message=Cannot assign a drive letter to a partition from the backup archive.; line_tag=0xE3D108407D4C7E
Error_Code=AfIAZAB+TH1ACNHjAENhbm5vdCBhc3NpZ24gYSBkcml2ZSBsZXR0ZXIgdG8gYSBwYXJ0aXRpb24gZnJvbSB0aGUgYmFja3VwIGFyY2hpdmUuACRtb2R1bGUAQXRydWVpbWdfaG9tZV92c182NTcxACRmaWxlAEFrOlw2NTcxXHByb2R1Y3RzXGltYWdlclxob21lXHdpemFyZHNcd2l6YXJkX21vdW50LmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpXaXphcmRzOjpNb3VudFdpemFyZDo6TW91bnRQYXJ0aXRpb25zACRsaW5lAE5UAwAAAAAAAAA=
Start= 7/23/2016 4:57:11 PM
Finish= 7/23/2016 4:57:22 PM
Total Time= 00:00:11
Hey thanks for the response...I think your exactly right, that in stopping the backup, then restarting the backup is what is causing the issue. What I can't figure out though, is why did it allow me to do just that...and then why did it/does it validate the backup as being valid. I would have thought if there was a problem with the starting/stopping of the bkup operation, the bkup would have ended up with a neagive(-) sign before the version number in the backup file name or that would not validate and be shown as corrupt?
The biggest problem I'm having though is the fact of validation; while I know it's not 100% just b/c it's valid...I read in these forums from:
- [Bobbo_3C0X1 Acronis MVP Volunteer - “If one way is validating, you're probably fine though. For me, I test my backups by making sure that I can double click on them and that they open in Windows explorer and I can navigate through them. If you can, you're good to go.”]
and my backup does validate and I can click/open in Windows Explorer and Naviagte through it.
Removing the first backup and adding the second backup by itself is and idea I actually attempted. The results were the same. It seems as though the two are permanently linked in Acronis, as when I add the second bkup only, the console still shows the creation timestamp of the first backup?
Are you seeing the reference to the date/time stamp of the cancelled backup if you are booted from the Acronis rescue media?
If yes, then I am not sure how we can help further here in the user forums from the point of view of recovering from these backup files.
The only other thoughts at this time would be to do a basic install of Windows 10 on your OS drive, then try restoring back from the backup image by selecting on a files & folders basis (done using the offline media to avoid Windows locks etc).
On that same thought line, have you tried to restore individual partitions from the backup or does it fail before that can be attempted?
Thanks for your help....I know just reading my whole post must be a bear...it took me some time just to compile all the relevant info....so Thanks.
Are you seeing the reference to the date/time stamp of the cancelled backup if you are booted from the Acronis rescue media?
Yes
If yes, then I am not sure how we can help further here in the user forums from the point of view of recovering from these backup files.
The only other thoughts at this time would be to do a basic install of Windows 10 on your OS drive, then try restoring back from the backup image by selecting on a files & folders basis (done using the offline media to avoid Windows locks etc).
I have been able to successfully restore a few files/folders individually in this manner, but most fail:
- ATI 2015 fails with msg “the file has reached the end of the line”
- ATI 2016 fails with file corrupted msg
On that same thought line, have you tried to restore individual partitions from the backup or does it fail before that can be attempted?
When trying to restore either one of the two partions (EFI sys FAT or C: SSD Windows) individually, the restoration runs for a minute or so, and then fails with the error msg’s listed above.
Log from ATI 2016 UEFI Rescue Bootable iso x64 cd – Validation attempt
<?xml version="1.0" encoding="UTF-8" ?>
<logs>
<log build="6571" product="True Image" task_name="Backup Validation" uuid="6A724BCE-E616-7BF6-D873-0473AECF6546" version="19.0">
<event code="0" id="1" level="2" message="Operation "Backup Validation" started." module="100" time="1469526185" />
<event code="1026" id="2" level="2" message="<bold>Validate Backup Archive</bold><endl/><tabpoint value=30><indent value=4>Location:	<indent value=10><textcolor value="navyblue">"F:\New folder\My backup.tib"</textcolor></indent><indent value=4><endl/></indent><endl/>" module="11" time="1469526185" />
<event code="504" id="3" level="2" message="Pending operation 4 started: 'Validate Backup Archive'." module="1" time="1469526185" />
<event code="13" id="4" level="2" line_tag="0x1D8EAB676A3F695B" message="The file is corrupted." module="4" time="1469526189">
<field name="Path" type="TString" />
<field name="$module" type="TIdentifier">trueimg_home_media_glx_6571</field>
<event code="13" id="5" level="2" line_tag="0x6517E0ECF4E10120" message="The file is corrupted." module="4" time="1469526189">
<field name="$module" type="TIdentifier">trueimg_home_media_glx_6571</field>
</event>
</event>
<event code="252" id="6" level="4" message="Operation has been canceled." module="100" time="1469526255" />
</log>
</logs>
South20, sorry but I don't have any more answers for you for this situation.
One of the issues with validation is that it works by recalculating the CRC checksum data for the backup archive file to confirm that this matches the CRC checksum that is embedded in the file when it was created. While this is a valid test mechanism it does not give any guarantee that the data contained inside the backup archive file is of good integrity should anything in the source data have become corrupted, or if the writing of the data to the backup archive file was disrupted in some way.
This is where a more robust validation technique would be invaluable, i.e. recalculating the checksum for the data stored in the VSS snapshot file and comparing that to the calculated checksum for the archive file. The issue here though is the size of the data involved, i.e. the snapshot has to fit into the free space available on the drives in the system at the time of the backup - this free space may be much less than the total size of data being backed up, and that would mean multiple snapshots that cannot be recreated at any later time due to the nature of modern computer systems where data is changing continuously!
The limiting factor for support and ourselves at this point, is your initial statement of actions, where you stated:
Performed a Secure Erase on system disk - Samsung SSD 850 PRO>Succesful>Initialize Disk>Reboot
This action precludes any further attempt to make a separate new good backup image and the only other redress at this point, assuming that nothing has actually overwritten the SSD in the testing you have done in the interim, is whether you could attempt to recover the contents of the erased SSD. This really depends on whether that is even possible with SSD technology which is basically a memory device, and also the intensity of the Secure Erase method used - the more secure, the less likely the success of recovering the data outside of law enforcement forensic recovery tools!