Salta al contenuto principale

unable to boot replacement disk after a restore

Thread needs solution

I backed up a failing 250gb laptop drive and then restored that backup to new 250gb identical drive.  System does not boot. I booted the win10x64 repair cd and did a startup repair.  The repair failed.  I then brought up the command prompt from that repair cd and ran

bootrec.exe /rebuildbcd  this failed

bootrec.exe /fixmbr this ran ok

bootrec.exe /fixboot this ran ok

System does not boot.  How do I clone the drive to my desktop system and then use that to build a new disk that can boot?

0 Users found this helpful

Joseph, does your laptop still boot from the original 'failing' disk, and if so, what does it show as the boot device in the laptop BIOS settings?  Is this shown as Windows Boot Manager (for UEFI) or as the disk drive (for Legacy)?

How have you performed the restore of your backup image to the new drive?
Did you remove the old drive, replace it by the new drive, then boot from the Acronis Rescue media on the laptop to perform the restore / recovery?
If you did this, did you boot the rescue media in the same BIOS mode as used by Windows 10 on the original disk drive?

It is a laptop drive being used on an old "open air" HP Z-400 motherboard so it is legacy. USB boot is a DVD drive not flash.

 

I originally tried booting 2012 "+ pack" media builder with the old and new disk and was unable to select the destination as it was grayed out for some reason.

I then booted the 2018 rescue cd.  Tthe destination was not grayed out but the clone failed "unable to lock dynamic drive" and the suggestion to use a Linux based recovery.  I was not sure that that was so I then put the laptop drive into a USB adapter and used my Areaa51 with 2018 acronis to make a backup of the drive.  I got the entire drive as when I did a restore I observed through the disk manager that there were 3 partitions just like on the original drive.

I had problems with the original drive as it was out of replacement sectors and the acronis backup failed with the message that sector xxxxx (don't remember now) was bad and there were no additional free sectors.   I managed to find the bad sectors using winhex and guessing and deleted the files that contained the bad sectors.  This allowed acronis to finally finish the backup as it no longer attempted to read the files that had the bad sectors in them.  The bad sectors where in memory.dmp (a really huge file) and in windows.old so they were not important.

I have no idea why 2012 grayed out the new disk nor why the 2018 said I had a dynamic drive and suggested Linux.

 

Any help is appreciated

[edit]  I have a site license for acronis but if I put on the open air z400 I suspect it may pick up the bad sectors during the install so I need to use my other PCs or boot a recover disk.

Windows 10 tends to enable Fast Start which can give the locked / dynamic disk type issues when the computer is not shutdown fully before attempting recovery / restore actions.  This is because the computer is actually in a hybrid sleep (akin to hibernation) state instead.

If the original computer is definitely Legacy / MBR then please ensure that not migration to GPT is taking place if doing the restore on another computer that may be UEFI booted.

Finally, check that the restored drive shows with an Active boot partition.

Finally got the replacement to work.  Not sure what went wrong originally, possibly that fast start as I have read about that before.

I tried that 2018 media builder CD again but this time the source disk was good as I had deleted the files that had the bad sector.  (Alternately, the fast start was not causing the problem)  In addition to removing the files that had the bad sectors I had also deleted those .sys files in the root.  Possibly that removed the fast start capability.  In any event I no longer got that strange message about dynamic disks and was able to clone the drive and it booted just fine.

 

I assume my 2012 acronis grayed out the destination drive as it was not compatible with win 10.  The other thing I noticed was the media builder took a really long time to boot.  It showed the windows logo for at least 5-8 minutes before the loader came up. I was thinking it had booted to windows instead of acronis and almost reset the system.

 

I have a site license for disk sentinel but that system was not configured for it as that laptop disk was very new and I didn't think it would have problems so soon.  

Glad to hear the drive is now working for you.  Deleting the hiberfil.sys would remove the fast start means of resuming if active.  The ATI 2018 rescue media will use WinPE for boot instead of the older Linux kernel OS used for older versions, but this does take longer to boot.  WinPE does have better device support for newer hardware.