Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
appnote:work_around_bios_halting_on_ipxe_exit [2013/01/07 22:53] rulerof First draft |
appnote:work_around_bios_halting_on_ipxe_exit [2013/01/08 08:09] rulerof Edited for accuracy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Work Around BIOS Halting on iPXE Exit ====== | ====== Work Around BIOS Halting on iPXE Exit ====== | ||
| ===== Overview ===== | ===== Overview ===== | ||
| - | Often times, iPXE users will need to exit iPXE and continue with the BIOS boot order for any number of reasons. This is often the case for people who would like to install an OS directly to a SAN device. Unfortunately, many system BIOSes will not continue their boot order after iPXE exits and hands back control of the boot process. | + | Often times, iPXE users will need to exit iPXE and continue with the BIOS boot order for any number of reasons, such as installing an OS directly to a SAN device. Unfortunately, many system BIOSes will not continue with their boot order after iPXE exits and hands back control of the boot process. |
| - | In the majority of these scenarios, one can use the [[cmd:sanboot|sanboot]] command directed at a local disk to achieve the same effect as having the BIOS continue to the next boot device. But when this doesn't work, a more robust option for booting a local drive is to use iPXE to simply chainload a different bootloader more suited to handling local disks. | + | In the majority of these scenarios, one can use the [[cmd:sanboot]] command directed at a local disk to achieve the same effect as having the BIOS continue to the next boot device. But when this doesn't work, a more robust option for booting a local drive is to use iPXE to simply chainload a different bootloader more suited to handling local disks. |
| ===== Using GRUB4DOS ===== | ===== Using GRUB4DOS ===== | ||
| Line 11: | Line 11: | ||
| * [[http://sourceforge.net/projects/grub4dos/files/GRUB4DOS/|Download the GRUB4DOS binaries]] of the latest version((grub4dos 0.4.4 at the time of this writing (January 2013) )) over at SourceForge. | * [[http://sourceforge.net/projects/grub4dos/files/GRUB4DOS/|Download the GRUB4DOS binaries]] of the latest version((grub4dos 0.4.4 at the time of this writing (January 2013) )) over at SourceForge. | ||
| - | * Place the file grub.exe from the archive on an HTTP/FTP/TFTP server so that you can chainload it with iPXE. | + | * Place the file **grub.exe** from the archive on an HTTP/FTP/TFTP server so that you can chainload it with iPXE. |
| ==== Usage ==== | ==== Usage ==== | ||
| Line 19: | Line 19: | ||
| For simplicity, we'll use the command-based approach: | For simplicity, we'll use the command-based approach: | ||
| - | <code> | + | |
| - | chain http://server/grub4dos/grub.exe --config-file="command1;command2;commandN" | + | chain http://server/grub4dos/grub.exe --config-file="command1;command2;commandN" |
| - | </code> | + | |
| ==== Examples ==== | ==== Examples ==== | ||
| - | == Boot Hard Disk 0 == | + | ---- |
| - | <code> | + | == Boot Hard Disk 0 (MBR) == |
| - | chain http://server/grub4dos/grub.exe --config-file="root (hd0,0);chainloader +1" | + | |
| - | </code> | + | chain http://server/grub4dos/grub.exe --config-file="rootnoverify (hd0);chainloader +1" |
| + | |||
| + | == Boot Hard Disk 0, Partition 0 (VBR) == | ||
| + | |||
| + | chain http://server/grub4dos/grub.exe --config-file="root (hd0,0);chainloader +1" | ||
| == Boot CD/DVD 0 == | == Boot CD/DVD 0 == | ||
| - | <code> | + | |
| - | chain http://server/grub4dos/grub.exe --config-file="cdrom --init;map --hook;root (cd0);chainloader (cd0)" | + | chain http://server/grub4dos/grub.exe --config-file="cdrom --init;map --hook;root (cd0);chainloader (cd0)" |
| - | </code> | + | |
| == Find and Load the Windows Boot Manager == | == Find and Load the Windows Boot Manager == | ||
| - | * Notes: This is good for booting Windows when you don't know its disk number. | + | * Notes: This is good for booting Windows when you don't know its disk number. For XP/2003, change **BOOTMGR** to **NTLDR**. |
| - | <code> | + | |
| - | chain http://server/grub4dos/grub.exe --config-file="find --set-root /BOOTMGR;chainloader /BOOTMGR" | + | chain http://server/grub4dos/grub.exe --config-file="find --set-root /BOOTMGR;chainloader /BOOTMGR" |
| - | </code> | + | |
| - | == Find a File, and Boot the Disk it's on == | + | == Find a File, and Boot the Partition it's on == |
| - | * Notes: Unlike the BOOTMGR example, this will load the MBR of the disk, which will then chain your second-stage bootloader. | + | * Notes: Unlike the BOOTMGR example, this will load the VBR of the partition, which will then chain your second-stage bootloader. |
| - | <code> | + | |
| - | chain http://server/grub4dos/grub.exe --config-file="find --set-root /filename;chainloader +1" | + | chain http://server/grub4dos/grub.exe --config-file="find --set-root /filename;chainloader +1" |
| - | </code> | + | |
| + | ---- | ||
| + | |||
| + | ==== Troubleshooting / Other Options ==== | ||
| + | |||
| + | GRUB4DOS includes extensive support for various filesystems and device types, including floppy disks (fd) and memory-mapped disks (rd). The contents of the (rd) device can even be an [[cmd:initrd]] downloaded by iPXE before executing GRUB4DOS. Consult the GRUB4DOS readme file for a comprehensive set of examples. | ||
