Bare Metal Restore fails to boot

[K3llz]

Problem: Windows 7 machine boot loops at Windows logo after bare metal recovery

Hello all,

Dell Optiplex 3020, running newest version of VEB. Used recovery media created on this machine. Replaced HDD (500GB with a 1TB) and booted with recovery media. Restored image from network share. Restore went OK. Rebooted and Windows reboots at Windows logo and loops like this. Booted into recovery environment and ran startup repair with no success.

Anyone have any idea how to fix this?

[Dima P.]

Hi,

Was it a restore to dissimilar hardware? Can you collect the recovery log that was placed to your backup repository and share it with me? Thanks.

[K3llz]

Was it a restore to dissimilar hardware?

It was identical hardware, same computer, just swapped into a different HDD (same brand HDD in fact).

Can you collect the recovery log that was placed to your backup repository and share it with me?

Not sure where those would be located. The machine no longer boots and we are not using a Veeam repository, but rather each machine backs up to it's own folder on a file server.

[Dima P.]

Recovery logs should be placed in the same folder where backup file resides.

[K3llz]

Recovery logs should be placed in the same folder where backup file resides.

My apologies.

[removed]

Uploaded the zip of the logs above.

Thank you

[Dima P.]

Robert,

Thanks for the logs. QA asked to perform one more Bare Metal Restore with the same options you used before but this time before recovery from the boot screen go to Tools > Load Drivers and uncheck ‘Inject drivers…’ checkbox. Let me know how it goes (if it fails please share the new portion of the recovery logs). Cheers!

[K3llz]

Thanks for the logs. QA asked to perform one more Bare Metal Restore with the same options you used before but this time before recovery from the boot screen go to Tools > Load Drivers and uncheck ‘Inject drivers…’ checkbox. Let me know how it goes (if it fails please share the new portion of the recovery logs). Cheers!

Dmitry,

Your solution worked. The machine booted just fine. Windows had to install some drivers on first boot, including a WDC ATA device (HDD).

Is it always advisable to uncheck inject drivers even when restoring to bare metal?

Is there a way to track down which driver caused this problem?

Thank you for all your help. 10/10 would recommend Veeam.
-Robert

[joseb552]

Hello,

I didn't want to start a new thread for this same issue. I'm attempting to perform a bare metal restore from one machine to a new machine with dissimilar hardware. Is this possible with Veeam? I am stuck in the same boot-loop as k3llz and have tried unchecking the "inject drivers" option with no change in outcome.

I'm attempting to go from:

Dell Optiplex 980 with 160 GB drive

to:

Optiplex 7010 with 1 TB drive.

Any advice?

[Dima P.]

Jose,

unchecking the "inject drivers"

Just to double check, did you uncheck this option prior to performing the bare metal recovery? Thanks.

[joseb552]

Correct, unchecking that option was the first thing I did after booting the recovery media.

[Dima P.]

Hi Jose,

Thanks for the update. If it’s possible, please open a case from another VEB's Control Panel - we need the recovery logs to be checked. Please do not forget to include the case ID in the thread.

[joseb552]

Hi Dima,

I've opened the case with ID: 01754972

Thanks

[Risa]

Same problem
case #01788846

[OrangeWing]

Same Problem
Case 01857978

In this case, two HP workstations... got a new one (dis-similar hardware obviously) and will not boot up after restore.

[Dima P.]

Hi guys,

If you still have the described issues, kindly, continue to work with our support team and do not forget to update the thread with the resolution. Thanks!

[Gerald]

Had the same problem restoring Windows 10 on an ASUS Q87T Motherboard - Bluescreen after restore unless the driver insertion was disabled first.
I think having the option "do weird things to my windows" on by default is a questionable choice.

This should rather be optional (easier to find when restoring) and off by default. Acronis does it this way in True Image.

[Dima P.]

Hi Gerald,

Was Recovery Media created on the same machine? Thanks.

[Gerald]

Sorry for taking some time to answer this. The recovery media was created on the same machine from within Windows 10 just minutes before I started the restore (the Windows installation and hardware was fine, I just wanted to go back to a backup from the week before).
Regarding the OS: I'm not sure if the Windows Creators Update had already been installed on this machine at the time, and I have not yet had opportunity to try if bare metal restore works without manually disabling this feature in the new Veeam Agent 2.0 RTM version.

[vClintWyckoff]

Gerald-
Hey so I have an ASUS X99 M WS MB in my current machine here with an Intel i7 6800k processor in my desktop. When I ran Windows updates the first time it pulled down the correct software and drivers for Intel Turbo Boost software as well as the chipset drivers. Admittedly, I have not yet tried doing a restore of my physical machine with the RTM build. I am wondering here if some how a necessary driver did not get included within your recovery media? Have you tried re-creating the recovery media?

[patrickwilson82]

I'm having the same issue. The VM boots back into recovery mode after it says that the Bare Metal Recovery was successfully restored. Do I need to open a case? If so, how do I do that?

[ron21]

Hello everyone. i am new on Veeam platform and tried on few machine as reputation was sound when i did google search.
Yesterday one of my PC Win 10 Ent started messing up... i want to recover it to my few days earlier state using Veeam backup on my NAS drive.
But recovery USB fails to boot as it throws BLue screen with message: Not enough memory to create RAM DISK??
means i need more than 8GB on system as that's all i have!

my back up is good on NAS drive but needs means to recover it.
Please any solution?
Regards

Ron

[ron21]

Thanks for the logs. QA asked to perform one more Bare Metal Restore with the same options you used before but this time before recovery from the boot screen go to Tools > Load Drivers and uncheck ‘Inject drivers…’ checkbox. Let me know how it goes (if it fails please share the new portion of the recovery logs). Cheers!

Thanks mate, you are life saver! your words worked spot on...

Regards

Ron

[Dima P.]

Ron,

Good to hear that you resolved this issue so quickly. If any questions arise do not hesitate asking!

[jlegrow]

Hello,

Having the same issue. Trying to do a restore to dissimilar hardware.

1. I installed Veeam Endpoint on the old PC and did a backup of the Windows 7 PC to external disk.

2. I installed Veeam Endpoint on the new PC and created the restore CD on that PC and checked the box to "include drivers"

3. Booted the new PC using the restore media and tried to restore the backup of the old PC.

4. The restore completed but the PC goes into a boot loop on startup.

5. When using safe mode boot option I can see that windows fails at loading "CLASSPNP.SYS". Indicates a driver issue.


Am I doing something wrong here??

[Dima P.]

Hello Jamie,

Have you tried to disable the drivers injection as described above (Tools > Load Drivers)? Thanks!