Skip to main content

MBR Error 1 when deploying image on new Server build

Thread needs solution
Beginner
Posts: 1
Comments: 2

My master image is from a Win7 Pro machine. I did not use SysPrep. The PC has RAID 1, 2 SSD Drives both 128GB each. All win updates are ran. The Windows version is retail but we did not enter in a key so we can enter these Product Keys after the fact...

Pushing image onto exact same hardware....but when I boot after pushing image to the newly built PC, I get the 'MBR Error 1, Press any key to boot from floppy....'

We have been trying to find a soultion for this for awhile now with no luck. SURELY this is possible.

Please help, much appreactaed.

Chris

 

0 Users found this helpful
Forum Hero
Posts: 70
Comments: 8346

Christopher,

When deploying the image, use your bootable recovery media instead of doing this in Windows.  Then, when booting the recovery media, make sure you boot it in the same manner as the OS was originally installed (Legacy or UEFI).  If you have a UEFI OS but boot the recovery media in Legacy mode, it will attempt to restore as a Legacy build and will be unbootable - you can never go back from UEFI to Legacy.  In some cases, you can go from Legacy to UEFI, but your motherboard would need to be conifgured properly and it adds more complication anyway. 

Check how your OS is installed

Use one time boot menu in bios (F12, Esc, Del, or F1 depending on your motherboard) and select the right boot method of your media (legacy or UEFI)... EXAMPLE bios screenshot

Beginner
Posts: 1
Comments: 2

I have my BIOS set to "Other OS" in Secure Boot Mode. Maybe that is the issue? BUT the UEFI BIOS in this version considers Win7 as Legacy. Which I find very strange. The first time I tried to push the image to the newly built PC, it took 5 hrs (A). Then I attempted the Windows DVD boot reovery and that failed. It would not let me install the MBR or fix it. So, I pushed the image out again...this time it took 30 mins (B) and booted perfectly.

What I am trying to figure out is why A took so long Vs. B. If I have to do this image 2x, everytime, its going to be a problem.

The Mainboad we are using is the Asus H971-Plus (says Win10 Ready)

Thoughts?

Beginner
Posts: 1
Comments: 2

My findings show 'UFI Mode' for boot, but when I attempt to switch from 'Other OS' to 'UEFI Boot' I get the MBR Error 2, Please Insert Floppy.

Forum Hero
Posts: 70
Comments: 8346

There are 2 diffent things here...

1 is the mode the OS was installed UEFI or Legacy.  You want to double check if the OS is installed as UEFI or Legacy from within Windows first.

2) On a motherboard that supports both UEFI and Legacy systems, how you boot to your Windows installer, pretty much determines hwo the OS will be installed then.  The same goes for the recovery media in Acronis, how you boot it will determine if the recovery will try to restore as a Legacy/MBR install or a UEFI/GPT install.  After you've verifeid #1, you want to boot the recovery media in the same manner.  Some systems seem to not allow for UEFI DVD booting - you might have better luck creating bootable media on a USB flash drive (less than 32Gb - 2Gb is plenty).  Then use your one-time boot menu and pick the correct boot type - don't leave it to the bios to pick the default boot type based on the bios. 

A deployment can and should work the first time when restoring a full disk image (all paritions) to the exact same hardware.  The only thing that comes to mind about the original time being so long was if you selected to restore sector-by-sector (which is not needed).  In some instances, if drives have dirty bits - it may try to do a sector by sector backup or restore.   Don't think this is the case since you then got it to do the same restore in 30 minutes.  I'm guessing that the first one was the wrong boot method of the media, but I don't really have anyway of verifying that.