Differences

This shows you the differences between two versions of the page.

--- cmd:sanboot [2017/04/12 15:12]
mcb30
+++ cmd:sanboot [2021/01/25 17:53]
mcb30
@@ Line 66: / Line 66: @@
 If you wish to attach to multiple independent SAN drives, then you must use the ''[[:cmd:sanhook]]'' command to attach each non-boot drive individually.
-On a UEFI platform, some older operating systems (e.g. RHEL6) will install the bootloader with a non-default filename.  You can use either the ''%%--filename%%'' option or the ''[[:cfg:san-filename]]'' setting to specify the correct bootloader filename.  For example:
+On a UEFI platform, some older operating systems (e.g. RHEL6) will install the bootloader with a non-default filename.  You can use the ''%%--filename%%'' option (or the ''[[:cfg:san-filename]]'' setting) to specify the correct bootloader filename.  For example:
+    # For RHEL6
     sanboot --filename \EFI\redhat\grub.efi \
             iscsi:192.168.0.2::::iqn.2010-04.org.ipxe.chipmunk:rhel6
+    # For Debian
+    sanboot --filename \EFI\debian\grubx64.efi \
+            iscsi:192.168.0.2::::iqn.2010-04.org.ipxe.chipmunk:debian10
 For the sake of backwards compatibility, you can use the ''[[:cfg:keep-san]]'' setting to prevent iPXE from detaching a SAN drive, and you can use the ''[[:cfg: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 ''[[:cmd:sanhook]]'' command.