Why the very basic operation takes so much effort?
Restore from the Windows GUI didn't work, because after reboot the whatever starts after rebooting showed an error in backup_worker.cpp, line 167.
I created a rescue flash drive, it did not find the USB drive with the back up. Tried WinPE rescue media, same result. Created a Linux rescue media again. After a lot of experiments I found that TI Rescue Media sees the external USB drive only if it is connected to a specific USB port.
Finally, restoring time. I choose the image. Now before the last step of choosing the destination TI shows a spinning clock icon for 20 minutes.
Overall... 2 hours of wasted time before it even started restoring the disk.
Why did you make it so difficult to do? I have never had anything even remotely that difficult in Clonezilla. It's just a few times "press enter" and it starts working. Why you can't do it as easy? Btw, restore is faster with Clonezilla.
The issue is I have to waste several hours to perform a very basic task that should work right from the scratch.
With regard to the USB drive, ATI was crashing with an assert here:
c:/bs_hudson/workspace/1168/home/backup_worker.cpp(167)
c:/bs_hudson/workspace/1168/home/backup_worker.cpp(167)
The above is a line from the internal diagnostic data used only by the Acronis developers and does not refer to any local C: drive location, so is not helpful in this context.
I found that TI Rescue Media sees the external USB drive only if it is connected to a specific USB port.
Is there any obvious difference between the various USB ports? USB 2 vs. USB 3? Front panel vs. rear?
Can the recovery medium see any device plugged into that port or is it only the one device it does not see?
Not sure about the crash with WinPE... what version of ADK was used to build it and did you build WinPE or WinRE rescue media?
I'd grab the latest 1903 ADK and the 1903 ADK win pe add on (for Windows 10) and install those ... works for Windows 7 to present, but uses Windows 10 drivers and will support the majority of hardware "out of the box".
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
The linux rescue media is probably not finding the USB 3.1 controller on the system and you may be finding that it is working on a USB 3.0 or USB 2.x port instead? Driver support in Linux rescue media is usually the biggest issue people run into with more modern USB controllers, storage controllers and NIC's.
Using current Windows 10 ADK solves driver issues for most people, but there are still some odd-ball drivers out there that even Windows 10 can't natively support. If the default ADK needs drivers, you can supply them at build time though, they just need to be extracted and in .inf format (can't be .exe or .zip when adding them in).
Patrick O'Keefe wrote:I found that TI Rescue Media sees the external USB drive only if it is connected to a specific USB port.
Is there any obvious difference between the various USB ports? USB 2 vs. USB 3? Front panel vs. rear?
No. Just two equivalent ports on the side of the laptop. Absolutely same USB version.
Bobbo_3C0X1 wrote:Not sure about the crash with WinPE...
It's not WinPE.
The gist of the topic was my frustration over the amount of effort one needs to perform a very basic operation. Here you are suggesting installing ADK. I am not sure how wasting even more time on installing ADK, reading manuals and experimenting with drivers makes things better. I swapped the USB ports, it worked, then I just switched to Macrium. Technically I shouldn't be aware of existence of ADK at all to get things done.
I agree. It's way too difficult to make a rescue disk. Acronis needs to examine how Veeam Agent creates a rescue disk. That is what I use to rescue my PC's. I use Acronis for mainly Cloud Backup. Acronis never has been able to restore UEFI partitions in the correct order.