Acronis TrueImage Tips - 2020 Version Frustrations

Hopefully this will help some people.
I have been having a frustrating time with Acronis support trying to get issues resolved.
As at 14/07/2020, the 2020 Linux Rescue Media corrupts the NTFS filesystem on my backup drives when writing the backup.
Windows can never successfully repair the backup drive. Windows think it’s repaired it, but a rescan just discovers the same errors.
The backup drive needs to be reformatted to remove the errors.
Sometimes the backup files will not even appear on the backup drive after the backup completes.
The 2020 WinPE Rescue Media does NOT seem to corrupt the backup drive.
Unbelievably you need to keep a record of what version of Acronis (eg. 2019 or 2020) you use to make the backup because it can only be restored with that version of the Rescue Media (or you get the error message “the archive is corrupt”).
The 2020 backup files need a TIBX file extension or they will not restore (they give the error message “this is not last volume of the backup archive”).
Good luck to everyone. Not impressed with the 2020 Rescue Media at the moment. A the support just run you around in circles.


- Se connecter pour poster des commentaires

Hi Steve
First let me say sorry for my delayed response. Do not interpret that as a lack of interest in getting this issue fixed.
Also, thank you for such an exhaustive reply. I do understand that would have taken a long time to construct.
I read through the links you provided and that has explained a few things that I was unaware of, so thank you for that.
You should have no problem recreating my main issue if you wanted to see it happen.
Just use the latest Acronis 2020 Linux Rescue Media and run a DISK to IMAGE backup of a Windows 10 system (64bit in my case) to a backup drive (USB NTFS in my case).
The backup will say it has completed successfully. Reboot the computer and do a Properties/Tools/Check on the backup drive. Scan the backup drive for errors (even if it says there are none).
It will find and repair the errors. Except they are NOT repaired. Scan again and the errors remain. Fix. Scan again and the errors remain. etc etc
I just checked and I do have Fast Startup Enabled in windows.
I was completely unaware of the issues this causes with Acronis so in future I will be sure to:
- restart windows or
- hold the shift key down while shutting down
When I was creating images using the 2020 version it gave me the option to select TIB or TIBX. I chose TIB. It let me select TIB and make the backups.
But the backups give an error saying they are corrupt if you try to restore from them using the 2020 version. If you rename them to TIBX files you can restore from them.
So I am not sure why the product lets you save them as TIB.
On a positive note, I have just had a great email from the managers of the Acronis support section saying they are going to investigate the issue with the corrupted backup drive.
I have a word document with some screenshots showing the corruption that I would like to attach but it's 8MB and the max attachment is 3MB.
Thanks so much for your help. It is very much appreciated.
John
- Se connecter pour poster des commentaires

John, thanks for your update. I do not normally use any of the ATI 2020 Linux rescue media due to having laptops that have NVMe M.2 SSD drives using RAID mode which are unsupported by the Linux media as I understand. (I haven't checked / confirmed if that has changed recently but my WinPE rescue media works without issue with the laptop).
The issue of saving Disk backups as .tib is known but will always create a .tibx format file because that is now the default for this type of backup image, so renaming from .tib to .tibx will resolve any 'corrupt' issues. I will need to check with the ATI 2021 Beta rescue media to see if that still allows .tib to be selected for a disk backup?
I would suggest sending your Word document to the Acronis team on email for the corruption issue. Have you retried the backup without either Fast Start being enabled or else after doing a full shutdown of Windows?
- Se connecter pour poster des commentaires

Yes. I tried again doing a restart of windows and booting straight into the Linux Rescue Media. The backup drive still gets corrupted.
I have had a ticket open with Acronis support for around 2 weeks. They have the word document containing the screenshots and chkdsk results.
Thank you for your assistance.
Regards
John
- Se connecter pour poster des commentaires

John, I created a new ATI 2020 #25700 Linux rescue media USB stick this afternoon and booted my main HP Omen Windows 10 64-bit laptop from this with a spare 1TB external drive used as my backup drive. The backup of my main Samsung 970 Evo Plus 500GB NVMe M.2 SSD drive was completed successfully and I cannot see any issues with either the backup drive or the new .tibx backup file that was created on it. All looks good in both the standalone and Windows 10 Explorer environments with no indication of any corruption at all.
The good news from my perspective is that the Linux media had no issues in seeing the NVMe M.2 drive for the backup.
- Se connecter pour poster des commentaires

Hi Steve,
Thanks again for investing so much time into this. Did you plug the external drive into a Windows computer and do a Properties/Tools/Check on the drive? Even if it says there is no reason to scan the drive, if I scan it I find the errors.
Please see the attached Word document.
I have tried this on a couple of laptops and an Intel NUC. I have tried SSD and spindle backup drives.
As per previous correrspondence the WinPE 2020 works fine. As does Linux 2019.
I don't scan my backup drives for errors normally. I only became aware of the issue when the backup completed successfully and the backup file was not on the backup drive. I checked the backup drive for errors and the backup appeared after the errors were "corrected". But there are still more errors on the backup drive. Windows cannot fully repair the backup drive.To get rid of the error completely you have to reformat the drive. It's not the drive. I can do this on any number of backup drives - SSD or spindle - same errors.
I look forward to your thoughts,
Thanks
John
Fichier attaché | Taille |
---|---|
545764-188002.docx | 2.1 Mo |
- Se connecter pour poster des commentaires

John, the drive was reformatted prior to making the backup using the ATI 2020 Linux media (booted in UEFI boot mode) as previously had 2 partitions on the drive.
Going into the drive Properties > Tools > Checking the drive shows no errors, nor does the Event Viewer report - this after the backup was created on the drive.
- Se connecter pour poster des commentaires

Wow. I am absolutely amazed because I cannot get anything but a corrupt drive.
I have previously made sure my Acronis TrueImage is up to date before making the Linux Rescue media. I have made the rescue media on different brands of USB pen drives.
I have recreated this on the simplest setup you can imagine. Intel NUC with one SATA SSD with a fresh copy of windows 10 64bit installed that has never been attached to the internet. Then full backup to external drive. Tried SSD and spindle backup drives.
Perhaps I will not select FULL and see what happens.
- Se connecter pour poster des commentaires

I just made a fresh Linux Rescue 2020 media. I have tried CSM boot and UEFI boot. Backup drive still get corrupted. I tried not selecting the "FULL" backup mode in the Options. I used Generate to generate the name. Still corrupts the backup drive.
My Acronis TrueImage is 2020 build 25700 on Win10 64bit.
I run the 64bit version of TrueImage from the Linux boot media. Do you?
When the Backup Complete message appears, I click on the X at the window corners to exit out of Acronis. Is that what you do?
Thanks
John
- Se connecter pour poster des commentaires

John, I am just doing the normal steps here.
Booted my Win 10 laptop in UEFI mode from the USB 2.0 Linux rescue media (2GB stick).
Created the Full backup image as a disk backup (.tibx) to the external 1TB HDD drive.
Closed the ATI 2020 Window which triggers a restart of the computer and pulled out the 2GB stick when I saw the BIOS panel.
Booted normally into Win 10 and confirmed that the .tibx file was good by exploring the contents using double-click in Explorer.
Later, opened the Properties > Tools and did the Check and no errors found.
Is there any common factor in how you are doing the above for your various different PC's you have tested on? Eg: are you using the same USB dock or adapter to connect the external drive?
Personally, this was the first time I have used the ATI Linux media in over a year as all my normal media is created using the MVP Custom PE builder tool which gives me a much more comprehensive set of offline tools to use, including a web browser, file manager, screen capture etc.
The only time I have resorted to the ATI Linux media was for an ancient IBM Thinkpad T42 which has a non-PAE processor for which I changed the Linux media startup parameters to use 'forcepae' so that I could do backups and restores of that laptop.
- Se connecter pour poster des commentaires