Skip to main content

Cloned working disk, now neither will boot

Thread needs solution
Posts: 1
Comments: 1

I have 3 Optiplex 5050s here, one I cloned the default disk to SSD, both of which boot fine (and are UEFI, I think).  The other was fully operational, BIOS is set to legacy boot - I'd guess this implies it's an MBR setup disk?  The third, I have a .tib file to restore to, but having done this, it wouldn't boot, either in UEFI or legacy mode.  The data (including win 10 install) that was supposed to be written was all there though - guess it just needs to be "made bootable" somehow.

Eventually I just put all 3 disks into one machine, and booted to windows on the SSD (default Dell install), and in TI2018 cloned the working disk (1Tb Barracuda) to the one that wouldn't boot (1 Tb WD Blue).  As part of this it told me the target disk would be converted to GPT to make it bootable (seemed reasonable since it wasn't).  Cloning went seemingly without incident, but on returning the "working" disk to the one set to legacy boot, it won't.  Doesn't see it as UEFI either.  The newly cloned one behaves the same.

How can I best undo this?  Or better get the .tib file image that should be bootable to be so? 

0 Users found this helpful
Posts: 110
Comments: 28578

Simon, welcome to these public User Forums.

Please see forum topic: [IMPORTANT] CLONING - How NOT to do this - which was written after dealing with many issues arising from cloning mishaps!

How can I best undo this?  Or better get the .tib file image that should be bootable to be so? 

Do you have a full disk backup for each computer with a problem here?

Do you have a working Acronis Rescue Media boot CD or USB stick?

The above will be prerequisites for recovering from this situation.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media - which is an important factor here given your statements about having a mix of both UEFI and Legacy BIOS/MBR systems involved.

If your Legacy OS disk drive has been converted from MBR to GPT then this is due to any clone or restore action being performed on a UEFI system.  If that Legacy boot computer supports UEFI, then you could try changing the BIOS Boot Priority device to be the 'Windows Boot Manager' instead of being the disk drive for a Legacy boot