iPXE discussion forum

Full Version: wimboot and Emulating drive 0x80
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I am having an issue with I think wimboot when a system using a Supermicro X11SSL-F motherboard that is rebooted through IPMI/bmc with the bootdev pxe command. When such a system uses wimboot to try and boot to a windows install the install fails due to the drive emulation detected by wimboot being 0x80 instead of 0x81 or 0x82. This is true if the drive in question directly attached to the motherboard or through a raid card.

The following config works on other motherboards rebooted with a forced pxe boot without issues and will work with the X11SSL-F motherboard if it is booted not using a command such as the following

ipmitool chassis bootdev pxe

simplest working config file:
kernel http://$server/wimboot/wimboot pause=quiet
initrd http://$server/path/bootmgr.exe bootmgr
initrd http://$server/path/bcd bcd
initrd http://$server/path/boot.sdi boot.sdi
initrd http://$server/path/boot.wim boot.wim

Multiple versions of ipxe and wimboot have been tried as well as different pxe and tftp servers. It always has an issue if a forced pxe boot is issued.

I do not think it is an issue with wimboot as much as an issue specific to the motherboard. I am curious if others have seen such behavior and if there is any known way to over ride the drive emulation being detected by or passed to wimboot.
What is the actual issue you are seeing, is it a hang?, if so when? do you get any error messages etc?

You could try building ipxe with debug enabled to get more info about where in the boot process any issue pops up.

small note about bootmgr.exe it should automatically be extracted from the .wim file - so should not be needed as initrd (and on rare occasions I have seen it being an issue due to wrong bootmgr being provided)
The issue is a bios or bmc firmware bug.

Mods please close this ticket.
Reference URL's