Skip to main content

Backup Drive Won't Boot

Thread needs solution

I performed a full backup on a hard drive yesterday. When I rebooted the computer it would not boot. This computer could possibly have some copy protection software installed. I noticed during the backup while monitoring the source drive with task manager there were writes being made to the source disk.
Is this correct?
Why would Acronis write to the source disk?
Has something changed between ATI 2019 and ATI 2020?

I didn't have this problem with ATI 2019 but this source hard drive has a new version of software so I can't say for sure. I restored my backup to the source drive and the system booted.

0 Users found this helpful

How did you perform the disk backup for this issue?
Was this from within Windows?

If so, then yes, there will be some data being written to the source disk during the backup process. 

Some data is written by the Microsoft VSS snapshot process.
Some data is written by ATI as log data, also CBT (Changed Block Tracking) may be being updated, along with updates to the Acronis database etc.

In addition, there are background Windows services & processes performing writes.

I do not believe that there are any significant changes in the above respect between ATI 2020 and earlier versions.

Not sure what you mean by "This computer could possibly have some copy protection software installed." - if this is the case, then surely this would apply at any time a backup is performed by any software or of any drive?

Final question, what do you mean by "When I rebooted the computer it would not boot." - what was the symptoms of it failing to boot?  What errors were given?

Not sure what you mean by "This computer could possibly have some copy protection software installed." - if this is the case, then surely this would apply at any time a backup is performed by any software or of any drive?

I think he's stating that he believes the backup process somehow overwrote the bootloader.  During a backup, this should not be the case.  However, if starting a clone from Windows, and if a reboot is required, this is possible with the Acronis bootloader taking over to boot into the Linux rescue environment.  I don't think this occurred here though since this was a backup.

Final question, what do you mean by "When I rebooted the computer it would not boot." - what was the symptoms of it failing to boot?  What errors were given?

Agreed, need more info to go on.  I wonder if the boot order somehow got out of place in the bios and just needed to be set back to priority for the main drive (bios issue, not Acronis / Windows OS if the bios changes the order for some reason or if a thumb drive or DVD has priority and is not actually bootable).  

I have had my bios suddenly not find my drive at times too!  It's not related to Acronis though.  If the boot partition (system partition - usually, but could be on the C: drive or some other drive depending on how the OS installed it... use an admin command prompt and "bcdedit" to see where the bootloader actually lives) is moved, corrupted, etc. this can happen. 

And this month, we have yet another buggy Windows 10 update that is wreaking havoc on certain systems - one of the symptoms is an unbootable OS :(

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb4524147-update-may-cause-boot-and-printing-issues/ 

It's definitely not a BIOS issue. I remove the source disk from the system. Connect the source disk to my laptop via USB3 to SATA converter. Create a Full Disk/Partition Backup from within Windows. Return the Source Disk to the system. Unable to find boot disk is the error. Disk is detected in BIOS.

I think Steve answered my question. Those writes could have triggered the protection software. 

Technogod - just to be sure, you also checked the boot order after removing the source and returning it?  Each time you restart the bios, it checks for hardware and may not put the boot order in the same priority as expected with these slight tweaks. 

"Unable to find boot disk is the error" is usually what I see if the boot order is not correct, or if there is no bootable disk so I would definitely check the bootorder first, and after doing a cold boot (log press power button 10seconds after swapping the recovered drive back in" to make sure the bios updates at the next power up.

What is the protection software you are using?  I'm not sure why it would block 2020 and not 2019 - could you whitelist it in the protection software and then try to recover and see if it works then?

Unfortunately I don't have access to the whitelist or the BIOS. Since it boots after restoring my backup it's definitely not the BIOS. I do not know whether 2019 works or not. I have no systems with the previous version of software to test it except one. I'm hopefully going to be at that location on Friday. I'll perform a Full Backup with ATI 2020 and see if I get the same result. If not, the problem is the new software. If the result is the same. The problem is ATI 2020.

Things went from bad to worse. Backup showed all four partitions. Restore only restored two partitions. Determined problem was caused by ATI 2020 .tibx format. My previous backup used .tib format because there was an existing Full Backup of the same system. I have reverted back to ATI 2019. I'm really worried about reliability of ATI 2020. I used Norton Ghost to backup the system before Acronis let me down for the 9,999,999,999th time. I must be a glutton for punishment.