run list corrupted true image 2017 "windows" (and acronis backup 11.7 / 12.5 "linux")
Dear people,
I have been trying to get my head around this problem, but nothing I did seem to help so far.
I am getting the same problem with any of the above mentioned Acronis programs to recover disks back to another External Sata drive.
I am getting the run list corripted error and chkdsk isn't giving any errors.
Also S.M.A.R.T. values are okay and the .tib seems to be valid according to the Acronis software.
Any help is appreciated
Cheers


- Anmelden, um Kommentare verfassen zu können

Additionally what build of the product are you using? Installing the latest build might fix the issue.
A KB on this is available: https://kb.acronis.com/content/14260
- Anmelden, um Kommentare verfassen zu können

Hello Steve,
The programs used to recover a whole disk .tib image or all files from the .tib NTFS file- system are:
Acronis Backup 12.5 (Linux) (Ubuntu) (latest trial version from the Acronis site)
Acronis Backup 11.7 (Linux) (Ubuntu) (version ?)
Acronis Backup 11.5 (Linux) (Ubuntu) (version 11.5_43956_en_us)
Acronis Backup 11.5 Rescue media (CD) (version 11.5_43956_en_us)
Full advanced support "all drivers etc" to read my dynamic drives from Windows
Acronis True Image 2017 (Windows) version build 5554
What I did is first DD'ed (zero'd) the whole eSATA drive connected to the eSATA port on my PC after making a double full back-up.
After that I had format the eSATA drive (My Book Studio II) with the Western Digital tool that is designed to put it in either a RAID 0 or RAID 1 configuration. (Note: in both configurations I get the same error from the above Acronis programs.)
The specific detail of the error I got logged from Acronis True Image 2017 is the following (in Dutch)
<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="71099D04-B86F-47FF-BD1B-ECADC7984959" product="Acronis True Image" version="20.0" build="5554" task="7820B366-0DFA-4966-AC03-2246101FF6E6" task_name="MyBook (Full 26-06-2017)" >
<event id="1" level="2" module="100" code="2" time="1501167561" message="Operation MyBook (Full 26-06-2017) started manually." />
<event id="2" level="2" module="316" code="0" time="1501167563" message="Bewerking: Herstellen" />
<event id="3" level="2" module="11" code="1020" time="1501167563" message="<bold>Back-uparchief terugzetten</bold><endl/><tabpoint value=30><indent value=4>Van bestand:	<indent value=10><textcolor value="navyblue">"E:\MyBook (Full 26-06-2017)\MyBook (Full 26-06-2017)_full_b1_s1_v1.tib"</textcolor></indent><indent value=4><endl/>Herstel van:	<indent value=10><textcolor value="navyblue">Schijven</textcolor></indent><indent value=4><endl/></indent><endl/>" />
<event id="4" level="2" module="1" code="504" time="1501167563" message="Geplande bewerking 14 gestart: 'Partitie sector voor sector herstellen'." />
<event id="5" level="2" module="1" code="504" time="1501167563" message="Geplande bewerking 14 gestart: 'Partitie herstellen'." />
<event id="6" level="4" module="1" code="502" time="1501167597" message="Opstartlijst is beschadigd" line_tag="0x65B5EB7011094700" >
<error>AfYBAQAARwkRcOu1ZU9wc3RhcnRsaWpzdCBpcyBiZXNjaGFkaWdkACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzU1NTQAJGZpbGUAQWs6XDU1NTRccHJvY2Vzc29yXGRpc2thZG1cZGFfY29tbWl0LmNwcAAkZnVuYwBBRGFQcm9jZXNzb3I6OkNvbW1pdEltcGw6Ok9uRGFFcnJvcgAkbGluZQBOWQEAAAAAAAAAHAAHAM7cg7QBS9mJT3BzdGFydGxpanN0IGlzIGJlc2NoYWRpZ2QAJG1vZHVsZQBBdGlfZGVtb25fdnNfNTU1NAAkZmlsZQBBazpcNTU1NFxyZXNpemVyXG50ZnNcZnNfbnRmc19jaGVjay5jcHAAJGZ1bmMAQXJlc2l6ZXI6Ok5URlNQcm9jZXNzb3I6OlJlYWRDb250cm9sU3RydWN0dXJlcwAkbGluZQBO7gEAAAAAAAAA</error>
</event>
<event id="7" level="4" module="7" code="28" time="1501167597" message="Opstartlijst is beschadigd" line_tag="0x89D94B01B483DCCE" hide="1" />
<event id="8" level="2" module="29" code="0" time="1501167597" message="Herstelbewerking voor mogelijkheid tot opstarten is gestart." />
<event id="9" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="10" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="11" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="12" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="13" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="14" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="15" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="16" level="2" module="0" code="0" time="1501167598" message="" line_tag="0x0" >
<error>AQ==</error>
</event>
<event id="17" level="2" module="29" code="0" time="1501167598" message="Herstelbewerking voor mogelijkheid tot opstarten is voltooid." />
<event id="18" level="4" module="7" code="28" time="1501167648" message="Opstartlijst is beschadigd" line_tag="0x91BD40306B6C5084" >
<error>ARwABwCEUGxrMEC9kU9wc3RhcnRsaWpzdCBpcyBiZXNjaGFkaWdkACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzU1NTQAJGZpbGUAQWs6XDU1NTRccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpBcmNoaXZlT3BlcmF0aW9uOjpFeGVjdXRlACRsaW5lAE5uAAAAAAAAAAAcAAcAztyDtAFL2YlPcHN0YXJ0bGlqc3QgaXMgYmVzY2hhZGlnZAAkbW9kdWxlAEF0aV9kZW1vbl92c181NTU0ACRmaWxlAEFrOlw1NTU0XHJlc2l6ZXJcbnRmc1xmc19udGZzX2NoZWNrLmNwcAAkZnVuYwBBcmVzaXplcjo6TlRGU1Byb2Nlc3Nvcjo6UmVhZENvbnRyb2xTdHJ1Y3R1cmVzACRsaW5lAE7uAQAAAAAAAAA=</error>
</event>
<event id="19" level="4" module="7" code="28" time="1501167648" message="Opstartlijst is beschadigd" line_tag="0x89D94B01B483DCCE" hide="1" />
<event id="20" level="4" module="316" code="5" time="1501167648" message="De bewerking is voltooid met fouten." line_tag="0x9F2C53C72E8BCE4E" >
<error>AQUAPAFOzosux1Msn0RlIGJld2Vya2luZyBpcyB2b2x0b29pZCBtZXQgZm91dGVuLgAkbW9kdWxlAEF0aV9kZW1vbl92c181NTU0ACRmaWxlAEFrOlw1NTU0XHByb2R1Y3RzXGltYWdlclxkZW1vblxtYWluLmNwcAAkZnVuYwBBbWFpbgAkbGluZQBOWAIAAAAAAAAA</error>
</event>
</log>
- Anmelden, um Kommentare verfassen zu können

Ok, thanks for the further information but we are missing a key answer here.
What product did you use to make the backup image file that you are trying to restore here?
The product used to restore the backup image should be the same as that which was used to create the image.
The log file provided comes from ATIH 2017 build 5554 which is very old - the current / latest build is 8058 for this product.
Was this recovery attempt started from within Windows and if so, did it require a system reboot?
What type of backup is this, i.e. disk & partitions backup or a files & folders one? What exactly was on the drive that was backed up? Windows OS, Linux OS, Data?
- Anmelden, um Kommentare verfassen zu können
In reply to Ok, thanks for the further… by truwrikodrorow…

If I remember correctly I used the Acronis Backup 11.5 universal restore (build 43956) CD to make the full disk .tib file, because I remember it including a .xml. file and a folder which I can't remember the name from.
The ATIH 2017 log was created from a restore job made within Windows and it didn't asked to be restarted, maybe because it isn't a system disk but rather an additional Drive with data files like installation files, movies, music etc..
It is a Disk & Partitions backup .tib (Full disk backup with EFI) and only contained a NTFS file system with the DATA described above.
The reason why I tried all those versions is that I can't seem to figure out what I missed because in the past it just worked with the Acronis Universal restore CD (build 43956) when wanting to restore the whole .tib file as a disk & partition restore.
- Anmelden, um Kommentare verfassen zu können

Thanks for the further information.
KB 1689: Backup archive compatibility across different product versions shows as follows:
Acronis Backup (Advanced) 11.5 (Acronis Backup & Recovery 11.5) | Acronis Backup (Advanced) 11.5, Acronis Backup & Recovery 11.5 Acronis Backup & Recovery 11 Acronis Backup & Recovery 10 Acronis True Image Echo Acronis True Image 9.1 Acronis True Image 8.0 Corporate Editions |
I do not use ABR so have no experience in restoring backups created with the same.
- Anmelden, um Kommentare verfassen zu können
In reply to Additionally what build of… by truwrikodrorow…

Thanks Enchantech,
I am thinking about using the same Universal Restore CD again and if that is not working again I will download the latest Acronis Backup 12.5 Application for linux or windows and make a Restore Media to see if that will work.
- Anmelden, um Kommentare verfassen zu können
In reply to Thanks for the further… by truwrikodrorow…

Thanks Steve,
According to the list it would be compatible, but then again I will have to give in another go it first blanking the whole eSATA drive and try it again with the Universal Restore CD.
I will keep the thread updated.
Cheers.
- Anmelden, um Kommentare verfassen zu können

No luck with the Universal Restore CD 11.5 with build 43956.
I get the same "run list corrupted" error.
Can it be that it means the MFT inside the .tib I want to restore is itself corrupted?
- Anmelden, um Kommentare verfassen zu können

I might have found the culprit.
It seems to be a corrupt MFT inside the .tib file and not on the destination Drive.
I will update this thread when I have successfully recovered all the data.
Cheers
- Anmelden, um Kommentare verfassen zu können

Problem Found.
It was a corrupt NTFS filesystem record inside the .tib from the Data I made a backup from.
I mounted it with Acronis backup Advanced 11.5 with read rights and performed a chkdsk.
Though I had a older backup, with the same Data on it I canceled the chkdsk and didn't bother to fix it, but if anybody comes across this problem, this is the way to fix it!
Cheers people.
PS. Before to attempt in fixing it, make sure you made a copy from your .tib file you want to fix!
- Anmelden, um Kommentare verfassen zu können

R L, thanks for your feedback and solution - this may well help another user with similar issues!
- Anmelden, um Kommentare verfassen zu können