lamp

gPXE chaining / DHCP / TFTP / TGT / iSCSI to boot Windows 7 Diskless!

Published 14 November 09 02:58 PM | Frederick.Chapleau

By default the LUN number is 0, when you insert in the dhcp server

iscsi:ServerAddress.x.com::::iqn.2009-11.com.x:test

The problem is that TGT is by default assigning 0 to the controller of the iSCSI drive, and the LUN number for the device itself is 1.

So you must assign the value 1 to the definition.

iscsi:ServerAddress.x.com:::1:iqn.2009-11.com.x:test

… if you don’t assign it, you will get error “ 0x1d704039 ", or PXENV_STATUS_TFTP_CANNOT_READ_FROM_CONNECTION.

 

-f.

BTW, here is my configs…

dhcpd.conf

#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
allow booting;
allow bootp;

option space gpxe;
option gpxe.bus-id code 177 = string;
option gpxe-encap-opts code 175 = encapsulate gpxe;
option gpxe.keep-san code 8 = unsigned integer 8;

subnet 10.0.0.0 netmask 255.255.255.0 {
        range 10.0.0.200 10.0.0.220;
        authoritative;
        next-server 10.0.0.1;
        if not exists gpxe.bus-id {
                filename "gpxe.kpxe";
        } else {
                filename "";
                option root-path "iscsi:10.0.0.1:::1:iqn.2009-11.com.x:test";
                option gpxe.keep-san 1;
        }
}
ddns-update-style ad-hoc;
option time-servers 10.0.0.10;
option domain-name "x.com";
option routers 10.0.0.1;
option ntp-servers 10.0.0.1;
option domain-name-servers 10.0.0.1;
option subnet-mask 255.255.255.0;

targets.conf

<target iqn.2009-11.com.x:test>
        backing-store /san/disk1
</target>

Filed under:

Comments

# justDIY said on December 10, 2009 11:25 AM:

Hello Frederick !

Thank you for the detailed information and shared config file.  I was following the Win2008 how-to on etherboot website, but wasn't making any progress.  The critical part seems to be your bus-id 'script' that allows pxe to first load gpxe and then allows gpxe to attach to the san.  

I have win7 installer running, but I'm experiencing terrible performance, like 0.3MB/sec transfer rate to the iscsi target.    If I attach to the target using an existing win7 install, iscsi performance is about 40-60MB/sec (gigabit network being used in both cases).  Any suggestions what to check?

Leave a Comment

(required) 
(required) 
(optional)
(required) 

Protected by FormShield
Refresh
Listen
Please enter the characters shown on the image


Code: