Deployed image boots up with boot/bcd error and BSOD
-
Server
- FOG Version: 1.3.0-RC-11 SVN Revision: 5956
- OS: Ubuntu
Client
- Service Version:
- OS:
Description
I created a universal Windows 7 image for HP computers and I’m running into an issue when deploying an image to an HP Z440 Workstation where post image, it boots up with boot/bcd error and BSOD 7B code that says to chkdisk /f. I tried booting up two different harddrives and same issue. Unable to boot into USB Windows 7 disk to repair it. Any suggestions?
-
More info is needed here.
How / where did you create this reference image?
Did you sysprep the image before you captured it with FOG?
Did you include the proper drivers for the target hardware?
-
Also, if possible, please post your BSOD screen?
-
Hi George and Tom,
Thank you for your messages. I used MDT 2013 Update 2 to create the reference image for Windows 7 Professional 64bit. I placed the drivers locally in c:\drivers and using dpinst.bat in the unattend.xml file. I grabbed the drivers from HP site and used the Softpaqs software to grab the latest versions. It works fine in HP G1, G3, Z420 but I’m running into issues with the Z440. When I first captured the image, I accidentally chose Single partition and it hanged at resizing file system and said /dev/sda2 No reg file found. I powered off the VM, changed the Image to Multiple partition single size (non-resizable), then sys prepped and captured the image. Tested it on the models above and it was fine. I thought it had to do something with the boot files being on wrong partition so I ran the bootrec and rebuilt it. I’ll try again tomorrow and will let you know how it goes.
-
@holydonut Is this a UEFI Windows 7 layout?
-
I used VMware for reference image and it’s set to legacy boot
-
@holydonut Might I make a bold suggestion to update to the latest RC before re-capturing?
-
@Tom-Elliott said in Deployed image boots up with boot/bcd error and BSOD:
latest RC
still a n00b with Fog since I just started learning with imaging this past week and this seems easy to do but I could give that a try. is this a good guide? https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
-
@holydonut Not only is it “good” it’s the one I would’ve directed you to :).
-
@Tom-Elliott great thanks! updated to the latest RC so I’ll let you know how the deployment goes tomorrow
-
@holydonut Sorry I had to leave last night, I would agree to update to the latest release to ensure this issue hasn’t already been addressed.
I don’t use HP hardware so I can’t give driver pack guidance for those, but make sure your drivers are in inf format and not the .exe softpaqs.
I do a similar process of building the reference image in a vm client using mdt. I don’t have any issues with Win7 deployments this way.
Since you are capturing a bios (legacy) mode image, make sure your target computer is also in bios mode. You can’t capture a bios image and deploy it to a uefi system.
-
BSOD 7B means boot device not accessible IIRC.
Did you sysprep (with generalize switch) before capturing?
If not, what might be happening is it is loading (assuming here) AHCI drivers. If say, your HP Z440 is set by default to use RAID, it will give this BSOD and be unable to continue.
-
@george1421 no problem, after updating to latest RC it still has same boot bcd error. Softpaq exe’s were already extracted and now I’m troubleshooting to see if its a driver issue now. Target computer has UEFI and legacy enabled, not sure if this matters since when I deploy a different image to it, it is fine.
-
@holydonut said in Deployed image boots up with boot/bcd error and BSOD:
Target computer has UEFI and legacy enabled
What is its primary mode? I know some will boot either mode based on the boot media.
-
@Quazz yes it was sysprepped with generalize option
-
@holydonut I’d take a look at the BIOS then and take a look at the boot settings, there’s likely something going on there that’s causing this.
-
@george1421 I’m guessing legacy boot is default for network boot?
http://imgur.com/a/eJa4v -
@holydonut You often have to explicitedly enable the UEFI network stack before you can use it as a boot option.
Try disabling UEFI and see if that works.
-
@Quazz no luck
-
How about, removing drivers from the picture entirely first?
I’m assuming you’re using something like the drivers through postdownloadscripts? Sorry I’m not reading too far through this all.
If you have just the base image, no drivers, and test, do things appear to work smoothly? This will tell you immediately if it’s a driver issue or not.
Is it also possible the image as it was uploaded was uploaded improperly? (I don’t know if you already tried recapturing).