Acronis TI 2021 hangs after selecting destination backups
Hello. I've made boot image from Acronis True Image 2021, Linux-based image. I booted computer with this image, selected "backup disks", select partitions to backup ( on m2 ssd), select destination backup - another SATA drive, and, after that, Acronis just hangs - only mouse can move, but when i click on "next" or some other buttons - the program does not respond at all...
I tried: to change destination drive ( USB, SATA drive), name of backup file, partitions which i want to backup ( i tried to backup just standard 450 MB system partition used MS as boot partition), chaged type of Acronis image from Linux-based to Windows-based.
What the cause of the problem ?
The reason is ATI 2021 is unable to work with SSD
I don't know if this is the same for all SSDs, but I have the same problem.
Use ATI 2020 - it works fine.
VVS wrote:The reason is ATI 2021 is unable to work with SSD
I don't know if this is the same for all SSDs, but I have the same problem.
Use ATI 2020 - it works fine.
Sorry that is just plain wrong, I have 2021 backing up SSD's on two machines and have been doing this for moths with no issues related tot he SSD.
The only reason why a SSD might be a problem is if additional or special device drivers are needed but these should already be installed if the SSD can be seen & accessed within Windows using Explorer or other apps.
Otherwise, an SSD is just another disk drive and the type should be irrelevant to ATI.
If using rescue media then device drivers, RAID support, NVMe comes into play!
OEM versions of ATI are normally restricted in function to require a disk drive of the same make as the vendor of the OEM application, i.e. Seagate, Crucial, WD, PNY etc.
Same problem here. It hangs at the same point as topicstarter. After minutes of waiting I have to switch the power off, because the computer freezes completely. Version 2020 does not have this problem.
thomasjk wrote:VVS wrote:The reason is ATI 2021 is unable to work with SSD
I don't know if this is the same for all SSDs, but I have the same problem.
Use ATI 2020 - it works fine.Sorry that is just plain wrong, I have 2021 backing up SSD's on two machines and have been doing this for moths with no issues related tot he SSD.
1. Restore does not work, backup works fine.
2. I am not suggesting that it does not work on all types of SSD.
It doesn't work on my SSD.
Steve Smith wrote:The only reason why a SSD might be a problem is if additional or special device drivers are needed but these should already be installed if the SSD can be seen & accessed within Windows using Explorer or other apps.
Otherwise, an SSD is just another disk drive and the type should be irrelevant to ATI.
If using rescue media then device drivers, RAID support, NVMe comes into play!
OEM versions of ATI are normally restricted in function to require a disk drive of the same make as the vendor of the OEM application, i.e. Seagate, Crucial, WD, PNY etc.
I do not have an OEM version.
I boot from a UEFI USB with an unpacked ISO image.
ATI 2020 version works, ATI 2021 version does not work.
Technical support ticket issued on September 6th.
By October 15th, I proved to technical support that there was a bug in the program.
Since then, I have been waiting for this error to be fixed.
I clarify:
Backup works fine in a Windows environment.
Partitions restore requires a reboot and works in an environment (under control) of its own operating system (BusyBox).
This BusyBox does not work in my hardware configuration.
It does not accept commands being entered.
Why are you wanting to use the Linux based rescue media (other than that it is an available option)?
Acronis started a move away from Linux media back with ATI 2018 when the new 'Simple' method of creating WinPE media from the Windows Recovery Environment became the default for rescue media. WinPE media will have greater compatibility with all the hardware components of the majority of Windows PC systems.
Steve Smith wrote:Why are you wanting to use the Linux based rescue media (other than that it is an available option)?
1. I used unpacked AcronisTrueImage2021_32010.iso
2. I had ATI 2021 installed under Windows.
When doing partitions restore, it hung after reboot.
As far as I know, it reloads into this BusyBox.
ATI 2020 does not have this problem in any situation - after restarting Windows or when booting from an unpacked .ISO
Starting any disk recovery from within Windows triggers a restart which then boots from a temporary copy of Linux (BusyBox) OS, this has always been the case and includes if the Acronis Startup Recovery Manager feature (F11 on boot) is used.
Acronis will update the version of BusyBox with each new version of ATI but it is still the poor cousin of the WinPE media in terms of flexibility and compatibility.
Steve Smith wrote:Starting any disk recovery from within Windows triggers a restart which then boots from a temporary copy of Linux (BusyBox) OS, this has always been the case and includes if the Acronis Startup Recovery Manager feature (F11 on boot) is used.
I know it.
But in ATI 2020 it works, and in ATI 2021 it doesn't.
Hi community,
I have the same problem, I'm really surprised that there
is no solution or workaround available until now.
Am I wrong?
Regards,
Tom.
Tom, sorry but too little information. See the previous posts / discussion in this topic.
Which type of rescue media are you using?
What type of drives are involved?
What type of PC, what BIOS boot mode being used?
Is RAID involved?
Have you opened a Support Case direct with Acronis to report this issue?
Hi Steve,
I can't find any helpful solution in the previous posts of this thread.
And no, I don't opened a further Support Case concerning this issue,
because VVS (#7) already did this - obviously without success until now.
Some details of my scenario:
Laptop Intel 10thGen iCore, uEFI, NVMe-SSD (AHCI),
ext. Samsung T5 1TB SSD (USB-3.1 Gen.2),
AcronisTrueImage2021_34340.iso @ SanDisk UltraFit USB 3.0 32GB
(prepared using rufus -> UEFI).
The attempt to create a full backup from NVMe-SSD on the ext. T5-SSD got stuck after choosing the target-device and click on "Next" (s. initial post), only the mouse can be moved.
Any ideas?
AcronisTrueImage2021_34340.iso @ SanDisk UltraFit USB 3.0 32GB
(prepared using rufus -> UEFI).
Tom, this is at the heart of this topic dialogue. The .iso media is based on a small Linux distro (BusyBox) which has limited support for some modern hardware configurations.
Please try creating the WindowsPE version of media using the 'Simple' method of the Acronis Rescue Media Builder tool (assuming that you have ATI 2021 installed).
KB 65508: Acronis True Image 2021: how to create bootable media
Steve, can you explain why it worked in ATI 2020 and not in ATI 2021? Something must have changed that it is no longer working for us.
Steve Smith wrote:Tom, this is at the heart of this topic dialogue. The .iso media is based on a small Linux distro (BusyBox) which has limited support for some modern hardware configurations.
Surprisingly, for ATI2020 my hardware was not modern, but for ATI2021 it suddenly became modern. :)
Same here with Acronis Cyber Protect 15 iso. 12.5 still works great. 2020 also works fine 2021 not.
All the .ISO media is using a Linux distro that has obviously been updated with the latest versions of Acronis TI & CP.
This is not going to be fixed by users telling the other users here in these forums! You need to open Support Cases direct with Acronis to report this issue and get this to their developers to fix!
That's Customer Experience on the Highest Level!
All posters,
It seems that these third party apps like Rufus, Netbootin, etc. in most cases introduce bugs in builds of boot media. This is a knows issue where more than one disk is installed and the boot media is USB based.
In light of this fact I would suggest that if you have not used the Acronis Media Creator found in the Tools section of TI to build your media. The option of building the Linux based ISO version of TI is available using that tool and supported. Other methods of building media except for the MVP Media Builder tool are not supported and may not work as expected.
Enchantech wrote:All posters,
It seems that these third party apps like Rufus, Netbootin, etc. in most cases introduce bugs in builds of boot media. This is a knows issue where more than one disk is installed and the boot media is USB based.
In light of this fact I would suggest that if you have not used the Acronis Media Creator found in the Tools section of TI to build your media. The option of building the Linux based ISO version of TI is available using that tool and supported. Other methods of building media except for the MVP Media Builder tool are not supported and may not work as expected.
I downloaded the ISO image from here - https://dl.acronis.com/s/AcronisTrueImage2021_34340.iso
Does this image suit you?
VVS, this is not about downloading the .ISO image but how that is then converted when being used as bootable media on a USB stick.
Bob's point was that you don't need to download the .ISO and use a third-party tool to create this type of media, which can then introduce issues! Use the Advanced method of the Acronis Rescue Media Builder tool and select Linux as the type of media, then this can create the media directly on USB or DVD without using Rufus etc.
If you don't have ATI installed then you won't have access to the Acronis tools such as the rescue media builder, so your method would have to be used.
Steve Smith, no need to tell me about the different ways to create bootable DVD/USB - I know all of them and have tested everything.
As you have already written many times (and I agree with you), the problem is not in the boot method, but in the fact that BusyBox is used, not WinPE.