Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
appnote:work_around_bios_halting_on_ipxe_exit [2013/01/08 06:44] rulerof Cleaner formatting, added Troubleshooting section |
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 25: | Line 25: | ||
| ==== Examples ==== | ==== Examples ==== | ||
| ---- | ---- | ||
| - | == Boot Hard Disk 0 == | + | == Boot Hard Disk 0 (MBR) == |
| + | |||
| + | 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" | chain http://server/grub4dos/grub.exe --config-file="root (hd0,0);chainloader +1" | ||
| Line 38: | Line 42: | ||
| 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" | ||
| - | == 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. |
| 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" | ||
