Jump to content











Photo
- - - - -

Help with MDT/PE Multiboot setup


  • Please log in to reply
5 replies to this topic

#1 stephenp1983

stephenp1983
  • Members
  • 5 posts
  •  
    United States

Posted 08 June 2012 - 09:03 PM

I am trying to setup a usb stick with two bootable ISO, and a menu option that lets me select which to boot from. One iso is a win7pe project iso, and the other is a Microsoft Litetouch Deployment MDT boot iso. I am using a grub4dos bootloader and menu.lst to do this.

The win7pe iso works as it should, and I am able to boot to the MDT iso and select the OS from the task sequence. The problem seems to be during the first part of the windows setup task. MDT fails with a “setup was unable to create a new system partition…” error. If I just create a bootable usb with the MDT or PE Iso seperately (no grub4dos menu) I am able to complete the MDT OS install without any issues.

My thought is this has something to do with how the MDT task is setup to image to disk 0 partition 1 or with how grub4dos works. I am open to dropping grub4dos I just need a way to have a menu option that allows me to select one of the two iso's and complete the task. Below is the content of the grub4dos menu.lst file. Any help would be very much appreciated.


default 1
color NORMAL HIGHLIGHT HELPTEXT HEADING
splashimage=/fis.xpm.gz
foreground=FFFFFF
background=000000

title --- Directly Bootable ISOs ---
root

# Modify the following entry if it does not boot
title Boot Menu-v1.9.iso
find --set-root --ignore-floppies --ignore-cd /mdtx86/menux86.iso
map --heads=0 --sectors-per-track=0 /mdtx86/menux86.iso (hd32)
map --hook
chainloader (hd32)

# Modify the following entry if it does not boot
title Boot Menu-x64-7.iso
find --set-root --ignore-floppies --ignore-cd /mdtx64/menux64.iso
map --heads=0 --sectors-per-track=0 /mdtx64/menux64.iso (hd32)
map --hook
chainloader (hd32)

# Modify the following entry if it does not boot
title Boot Win7PEDMU.ISO
find --set-root --ignore-floppies --ignore-cd /dmu/Win7PEDMU.ISO
map --heads=0 --sectors-per-track=0 /dmu/Win7PEDMU.ISO (hd32)
map --hook
chainloader (hd32)

#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 6954 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 08 June 2012 - 09:31 PM

before the map --hook line, try adding

map (hd0) (hd1)
map (hd1) (hd0)
  • stephenp1983 and mlottgie like this

#3 stephenp1983

stephenp1983
  • Members
  • 5 posts
  •  
    United States

Posted 09 June 2012 - 03:08 AM

Thanks I'll give it a shot and let you know if that works.

#4 stephenp1983

stephenp1983
  • Members
  • 5 posts
  •  
    United States

Posted 12 June 2012 - 02:49 PM

Steve, thank you very much for the help. This solved the issue, and the whole process is working completely. I really appreciate it.

#5 steve6375

steve6375

    Platinum Member

  • Developer
  • 6954 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 12 June 2012 - 02:50 PM

Been there myself, done that, got the T-shirt! :loleverybody:

#6 mlottgie

mlottgie
  • Members
  • 1 posts
  •  
    United States

Posted 14 June 2012 - 12:06 PM

It's been a couple of years since I was attempting this myself. But, it came up again recently. Thank you SO MUCH for this solution. Now I finally have a USB stick that can boot to install Centos, Windows XP and 7, and also run my other utilities such as gparted and clonezilla.

Note this alternative fix from Microsoft when using MDT. This is from the Connect website for MS Solution Accelerators. I have not tried it myself:

The error is coming from Windows Setup itself, not from MDT. While we have seen other reports like this, it's not something we've been able to reproduce. Because of issues like this, we have decided to move away from using SETUP.EXE for installing OSes; this change will be present in the next version of MDT which is due in beta within the next couple of months.

As a workaround in the short term, you can import Windows 7 without the setup files (just import the install.wim or your custom WIM, but no setup files can exist on the deployment share). When MDT 2012 finds that there are no setup files available, it will fall back to using ImageX to do the OS installation.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users