BOOTMGR is missing



  • Hi All,

    I am having a problem deploying a Windows 7 Enterprise resize-able image. The image captures fine both using the 100mb double partition and as a single partition configuration using the resize-able and non-resize-able options.

    I can deploy the image fine if I use the non-resize-able option but if I try to deploy the captured resize-able image i get the “BOOTMGR is missing” error. I can boot into a PE environment and run “bcdboot d:\Windows” to fix it which works fine but that is obviously a work around for now. I don’t understand why this is happening.

    I have searched the forums and the only advice I saw was to be sure to chkdsk and defrag the image prior to capture which I do. I also use the /generalize option when sysprepping the image but I also tried running the Fogprep.exe just in case.

    Any ideas what I am doing wrong?




  • Moderator

    @kinjo said in BOOTMGR is missing:

    also having this issue

    Please start a new thread with your issues and details. There has been 4 years since this issue was initially reported, your environment may be different.



  • also having this issue



  • I haven’t tried the steps above but there isn’t some sort of error caused by deleting the system partition? Bootice run under windows so how is the system partition deleted which gparted then bootice run to mark the partition active?



  • Hello all :)

    Ok, let’s go:

    You need to RESIZE the partition, to do that:

    DELETE the first partition, i/e “SYSTEM”, then resize (use the space before the main partition), and SAVE the changes;
    Use BOOTICE to mark the partition active;
    bcdboot and bcdedit to create the bcd rep. and set the flag on the partition;

    Example:

    Disk: 100GB
    Target system: Windows 7
    Schema:

    P1 -> System, boot
    Size -> 100MB

    P2 -> Windows 7
    Size -> 98GB

    After resize, you got:

    P1 - > Windows 7
    Size -> 100GB

    Then, bootice, mark as active, bcdboot and bootsect (create bcd repository / set the boot flag on partition).

    Example: If you got 1 partition, aka “C:”, to the bcdboot command:

    bcdboot.exe C:\Windows /s C: /l en-us

    Then

    bootsect.exe /nt60 C:

    and DONE ;)



  • I’m having this same issue. Ubuntu 12.10 and Fog 0.32. Uploading from and deploying to Windows 7. There are two partitions: SYSTEM and C:. Using Single Partition (Resizable) -> 20GB. The image deploys, but the BOOTMGR is on SYSTEM instead of C:, where it was. I started using Multiple Partitions, but the file size was over 170GB, and it’s not resizable. How, using the Single Partition setting for Windows 7, can I assure that C: is bootable and SYSTEM is not?

    @Alvaro Campoy Neto, post: 11485, member: 3686 said:

    Hello all:

    To get a very good image, you need to put ‘all-in-one’, in ONE partition. To do that, you will need:

    1-) A REAL GOOD partition tool, like gparted or EASEUS partition manager ( to resize the partition, and get rid of the boot partition);
    2-) BOOTICE, a tool that allow you to activate the partition that you resize;
    3-) bcdboot and bootsect (cmd line tools), both from Win7 or from NT 6x Fast Installer;

    All tools here you got via google.com or, search for HBCD (The tool for the PROS, you really want to look for a edition or remix, like Proteus)

    Got not enough time now, will write a tutorial explain it (for all 2008 and 2012 Win family)

    Is this necessary, or just to “get a very good image?” I read somewhere that with Windows 7 (and it’s SYSTEM partition), you could use Single Partition and (as long as you set it as Windows 7) it will work.

    Thanks.



  • @Alvaro Campoy Neto, post: 11485, member: 3686 said:

    Hello all:

    To get a very good image, you need to put ‘all-in-one’, in ONE partition. To do that, you will need:

    1-) A REAL GOOD partition tool, like gparted or EASEUS partition manager ( to resize the partition, and get rid of the boot partition);
    2-) BOOTICE, a tool that allow you to activate the partition that you resize;
    3-) bcdboot and bootsect (cmd line tools), both from Win7 or from NT 6x Fast Installer;

    All tools here you got via google.com or, search for HBCD (The tool for the PROS, you really want to look for a edition or remix, like Proteus)

    Got not enough time now, will write a tutorial explain it (for all 2008 and 2012 Win family)

    Thanks for your help;
    i have already checked partitions with GParted, they seems to be ok but i dont understand you explain in ONE partition so you dont make the 100mb partition of Windows 7 ?
    Thanks again



  • Hello all:

    To get a very good image, you need to put ‘all-in-one’, in ONE partition. To do that, you will need:

    1-) A REAL GOOD partition tool, like gparted or EASEUS partition manager ( to resize the partition, and get rid of the boot partition);
    2-) BOOTICE, a tool that allow you to activate the partition that you resize;
    3-) bcdboot and bootsect (cmd line tools), both from Win7 or from NT 6x Fast Installer;

    All tools here you got via google.com or, search for HBCD (The tool for the PROS, you really want to look for a edition or remix, like Proteus)

    Got not enough time now, will write a tutorial explain it (for all 2008 and 2012 Win family)



  • Hi, i have the same problems.
    I have a brand new fog 0.32 on ubuntu, i captured a Windows 7 x64 from my VMWare workstation (sysprepped and with the 100mb partition) but still no luck…
    i set the image to single disk multiple partitions, but when the host boot i have a "BOOTMGR IS MISSING"
    i try to restore a new VM with this image and for the VM, it works.
    I dont understand what i’m doing wrong… i tried a lot of kernel but no luck… (for information i tried on a fujistu P3510 and Lenovo M71e, X220, X230)

    Help me :)



  • I wanted to update my post in case others where having the same issue. I have not figured out the problem with capturing/deploying a resizeable image on Win7 but I did get a decent work around in place. Basically I used Stephen Perkins post idea of just adding a command to my unattend.xml to extend the OS partition during sysprep since I was able to capture and deploy a non-resizeable image with no problem.



  • Got the same issue here, but only on the newer CoreI7 machines I am imaging, not the older ones… Any ideas?



  • I have more info on this. I was able to hold down <shift> and <page up> to scroll up in the buffer to see what the error message was when it bombs on the “blue” imaging screen. There are two messages, actually, here they are in order:

    Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only.

    chmod: cannot access `/images//images/080027d6bb31’: No such file or directory

    It sounds to me like there might be a problem in the fog imaging script but I am not sure where to look…

    EDIT: Whoop! This is the message when I try to capture a single partition image. I was trying to recapture the image using 1 partition instead of two.

    EDIT2: Upon further testing I found that the first warning was caused by an .iso file I still had mounted in the virtual cdrom and didn’t appear to be causing any problem really. I did find that by poking around in the fog script that line 624 appeared to have an extra /images/ in front of $tmpBackupPath so modifying it got rid of the second error. Now I appear to be getting an error from partimage that is indicating that the file system type is listed as -unknown- and is therefore not supported.



  • Up, i have the same issue.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.