Can't Boot with Rescue Media
Hi All,
Recently installed True Image 2020. Being using True Image for many years. From the Rescue Media Builder in the Tools menu I've created a bootable USB. I got into my PC's menu and make sure this USB is the first bootable device. My PC boots up reads the bootable USB (the light is flashing) my monitor displays the windows logo and the little dots going around in a circle just below the windows logo--and that is as far as my machine goes. It just hangs with the windows logo and the dots going around in circle and doesn't progress from there.
Anyone have any suggests as to what the problem might be.
Thanks all.
Also be patient. It may take a few minutes for the application to scan your hardware and network prior to full launch.
Steve Smith wrote:Kieran, welcome to these public User Forums.
Please check what BIOS mode is used by your Windows OS, then ensure that you use the same BIOS mode when booting from the rescue media.
Thanks for your suggestion, Steve. Normally my PC will boot from the HD using UEFI. I made sure the BIOS was set to UEFI for the bootable USB but the problem remains. Should have mentioned my PC is running Windows 10. Thanks again for your suggestion.
Enchantech wrote:Also be patient. It may take a few minutes for the application to scan your hardware and network prior to full launch.
Thanks for your response Enchantech. It is indeed a good point so I just booted up my machine from the USB and left it to try and do its thing for 30 minutes...even after that time the machine is still just displaying the windows logo and the dots going around in a circle.
Do you have any hardware on the PC that requires a special driver that might not be getting picked up by the Media Builder?
Which Builder option did you use - Simple or Advanced?
I agree with Patrick's thought of a possible device driver hanging during the boot. I would also consider running a chkdsk on all partitions of the source drive(s) to check for corruption.
For a tutorial on chkdsk click on the link in my Signature section below entitled Fix Disk Corruption.
Patrick O'Keefe wrote:Do you have any hardware on the PC that requires a special driver that might not be getting picked up by the Media Builder?
Which Builder option did you use - Simple or Advanced?
Hello Patrick, thanks for your response. I have tried both options: simple and advanced and both options give me the same result...on booting from the USB the windows logo is display along with the dots going around in a circle and it hangs at that point. My PC is nothing special with no special drivers. My PC is the standard Dell Inspiron 3647 and the only change that has been made from new is that I upgraded from 8 to 16 gig of memory. I have even used the MVP tool and I get the same result. Thanks again
Hi everyone, thanks very much for your constructive advice. I have pretty much tried all things that have been suggested and still I have the same problem...when trying to boot from the USB the machines displays the windows logo and the dots going around in a circle and then the machine just hangs at that point. My PC is a standard Dell Inspiron 3647 which remains the same as when I purchased it new. Only thing I have done is to upgrade from 8 to 16 gig of memory. I have tried the simple, advanced and the MVP tools to build my USB and all have the same problem. This is very frustrating as I have used earlier version of TI on the very same PC and bootable USB's I've created with the earlier version work fine. Very frustrating indeed.
Anyway, after reading through a lot of the documentation it seems like I have found a solution--I have activated the start up recovery manager and on boot up by pressing F11 I can get into recovery mode. I would really like to have a seperate USB but at least the recovery manager will get me out of trouble if I need to recover my harddisk. The recovery manager seems to be working ok at the moment.
So, I'm wondering...if in the event that my main harddisk crashes and fails to boot my plan would be just to drop in a new hard disk, press F11 on boot up and then recover my main hard disk (which is backed up on an external drive) to the new hard disk. I assume this will work?
Thanks again everybody for you helpful responses. Stay safe.
KP
Kieran, if the ASRM F11 tool works for you, then using the Advanced method of the rescue media builder, create the Linux version of the rescue media which should be the same as used by ASRM and will give you a bootable USB stick for recovery.
Steve Smith wrote:Kieran, if the ASRM F11 tool works for you, then using the Advanced method of the rescue media builder, create the Linux version of the rescue media which should be the same as used by ASRM and will give you a bootable USB stick for recovery.
Thanks Steve. I will give that a go.
Steve Smith wrote:Kieran, if the ASRM F11 tool works for you, then using the Advanced method of the rescue media builder, create the Linux version of the rescue media which should be the same as used by ASRM and will give you a bootable USB stick for recovery.
Hi Steve, just created the Linux rescue media on my USB and I'm very happy to report that my PC now boots from the USB. Really appreciate your suggestion as I now have what I need. Thanks a lot for your input. It is very odd that the Windows version doesn't boot. Take care and stay safe. Kieran.
You could try making a Windows Recovery USB drive from Control Panel/Recovery to see if it can boot. That will tell you if the problem is with Acronis or with WinPE. If you can prove the problem is with Acronis, I should be able to find out why.
You may also want to run a Memtest 86 check on your ram. It is hanging at a point where WinPE is being copied from the USB drive to ram.
Hi Mustang, thanks for your suggestions. I will try and make the recovery USB as you've suggested and see how I go. Following your suggestion I ran Memtest 86. I had no problem creating the bootable USB but when I tried to boot from the USB I ran into the same problem...my PC hangs at the Windows logo with the dots going around and that is as far as it gets. Thanks to Steve's earlier suggestion of the Linux bootable USB I know that works with no problems and I can live with that. But, I am troubled as to why a Windows USB will not boot. As you've suggested I will create the recovery USB from the control panel as see how that goes. Thanks again for your input--really appreciate it.
Could it be as simple as a BIOS setting? Can you turn off Secure Boot? Do you have Legacy CSM on?
Mustang wrote:Could it be as simple as a BIOS setting? Can you turn off Secure Boot? Do you have Legacy CSM on?
If I can get a Linux based bootable USB to work but not a Windows version doesn't that suggest my BIOS setting are ok? Yes, I have turned off secure boot in the BIOS. Can't recall legacy CSM but I'll check. Thanks for your suggestions.
Kieran, just one further check, if you have secure boot then this is a UEFI system so please ensure you match the BIOS boot mode used by your Windows OS with the mode used by any of the rescue media.
Steve Smith wrote:Kieran, just one further check, if you have secure boot then this is a UEFI system so please ensure you match the BIOS boot mode used by your Windows OS with the mode used by any of the rescue media.
Thanks Steve. I will look into that
Hello, Kieran,
if you are actually using a Linux startup media, please test the backup and restore functionality very thoroughly. On my system the backup took four times longer than in online mode and a correct restore did not succeed. When I tried to restore a file from a disk backup, the C partition was erroneously restored even though the selected disk backup was from a different data disk. Fortunately I had specified another device as target disk, otherwise my system partition would have been lost.
So: very, very carefully testing.
In December 2019, January and February 2020 I reported this and other errors and problems with extensive documentation to the Acronis hotline. There is no solution in sight.
A frustrated TI-2020 user