This is an old revision of the document!
sanboot [--drive <drive>] [--no-describe] [--keep] [<uri>]
sanboot iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:storage
sanboot http://boot.ipxe.org/freedos/fdfullcd.iso
sanboot --drive 0x80
sanhook --drive 0x81 ${root-path} sanboot --no-describe iscsi:10.0.4.1:::1:iqn.2010-04.org.ipxe.dolphin:liveinstall
Boot from the specified SAN drive. If no SAN drive is explicitly specified then the default SAN drive (0x80
) will be used. If a SAN target URI is specified then it will be automatically attached as the specified SAN drive.
The SAN drive will be described via an appropriate mechanism (such as an iBFT for an iSCSI drive) unless the --no-describe
option is specified.
Failure | Booting was unsuccessful |
---|
It is generally impossible for this command to return successfully, since if the boot is successful then control will not return to iPXE.
The Master Boot Record (MBR) code present on most SAN targets will be unable to boot unless the target is attached as the default SAN drive (0x80
).
If you wish to attach to multiple SAN targets, each target must be attached as a different SAN drive.
You can optionally specify a SAN target URI that will be automatically attached as the specified SAN drive before booting is attempted. This drive will be automatically detached if booting then fails, unless the --keep
option is specified.
For the sake of backwards compatibility, you can use the keep-san
setting to prevent iPXE from detaching a SAN drive, and you can use the skip-san-boot
setting to prevent iPXE from booting from a SAN drive. The combination of both of these settings provides functionality which is approximately equivalent to the sanhook
command.
You can use the sanboot
command to boot from a local disk drive without exiting iPXE. This can be useful if BIOS bugs prevent you from being able to cleanly exit iPXE. For example:
# Boot from local hard disk sanboot --no-describe --drive 0x80