OK, the gxpe.iso I tried previously was downloaded from rom-o-matic a couple of weeks ago but, not from the git-tree.
I'll give it a try and let you know how it goes. Thank you very much for your help, Erin Erin Coffey Operations Engineering (PLE) Process Systems Group 503-627-3904 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Oreman Sent: Friday, May 07, 2010 10:53 AM To: Coffey, Erin Cc: [email protected] Subject: Re: [gPXE] sanboot not supported On Fri, May 7, 2010 at 1:47 PM, <[email protected]> wrote: > Hi Josh: > > That's where I started. > > The image from Rom-0-matic didn't have a driver for my Intel " 8086 109A " > Network adaptor so gpxe didn't see net0. I got the e1000e-only.iso from an > email that Marty sent: > http://etherboot.org/pipermail/gpxe/2010-January/000312.html > > Now I do see net0 from gpxe but, I'm getting the sanboot Error. > > Is there an gpxe.iso that has support for my nic and for iscsi? The e1000e driver was fairly recently merged; you should make sure you're using gpxe.iso from the "top-of-git tree". The driver for your card is called e1000e_82571, if you want to pick it specifically in the drop-down menu, but all-drivers should work too. -- Josh > > Thank you, > > Erin > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Oreman > Sent: Friday, May 07, 2010 10:35 AM > To: Coffey, Erin > Cc: [email protected] > Subject: Re: [gPXE] sanboot not supported > > On Fri, May 7, 2010 at 1:24 PM, <[email protected]> wrote: >> [ . . . ] >> When I remove the w7 HD and boot to the gpxe environment (e1000e-only.iso) >> the initiator recognizes the network (net0) and 'dhcp net0' returns the >> correct mac address and I see the 'ok' message. >> >> The problem I'm having is that my sanboot cmd is failing. I try 'sanboot >> iscsi:192.168.1.100::::iqn.2007-08.100.1.168.192:iscsiboot' but, I get this >> message: >> >> "Could not boot from >> iscsi:192.168.1.100::::iqn.2007-08.100.1.168.192:iscsiboot: Not supported >> (0x3c03e003)" >> >> I'm not sure if my sanboot syntax is wrong or if I have neglected to >> configure the server settings appropriately? I'm new to network >> administration tasks so it's likely that I mis configured something or >> forgot something else entirely. > > That error code results from gPXE not knowing about the SAN boot > protocol you specified (in this case "iscsi"). How did you compile > e1000e-only.iso? It's possible to make a version of gPXE without iSCSI > support but it's not the default. I would try getting gpxe.iso (the > "all drivers" image) from rom-o-matic.net, and see if that works. > > -- Josh > >> >> >> >> Can you take a look at my .conf files below and tell me where I went wrong? >> >> >> >> Thank you very much, >> >> >> >> Erin >> >> >> >> >> >> >> >> This is all I have in my ietd.conf file:, everything else is commented out: >> >> >> >> Target iqn.2007-08.100.1.168.192:iscsiboot >> >> Lun 0 Path=/home/erincof/DPO70804B_LANBO.img, Typef=fileio >> >> >> >> >> >> >> >> This is what I have in my dhcpd.conf file: >> >> >> >> allow booting; >> >> allow bootp; >> >> DHCPDARGS=eth0 >> >> ddns-update-style none; >> >> authoritative; >> >> option domain-name "Lanbo.org"; >> >> option domain-name-servers 192.168.1.100; >> >> INTERFACES="eth0 eth1"; >> >> option space gpxe; >> >> option gpxe-encap-opts code 175 = encapsulate gpxe; >> >> option gpxe.keep-san code 8 = unsigned integer 8; >> >> filename ""; >> >> >> >> host lanbo-server { >> >> hardware Ethernet 00:06:5b:84:53:86; >> >> fixed-address 192.168.1.100; >> >> } >> >> >> >> option root-path >> "iscsi:192.168.1.100::::iqn.2007-08.100.1.168.192:iscsiboot"; >> >> >> >> subnet 192.168.1.0 netmask 255.255.255.0 { >> >> range 192.168.1.201 192.168.1.220; >> >> default-lease-time 86400; >> >> max-lease-time 86400; >> >> option routers 192.168.1.1; >> >> option ip-forwarding off; >> >> option broadcast-address 192.168.1.255; >> >> option subnet-mask 255.255.255.0; >> >> option ntp-servers 192.168.1.100; >> >> option netbios-name-servers 192.168.1.100; >> >> host lanbo-client { >> >> hardware Ethernet 00:d0:c9:ab:ae:6c; >> >> fixed-address 192.168.1.202; >> >> } >> >> } >> >> >> >> >> >> >> >> _______________________________________________ >> gPXE mailing list >> [email protected] >> http://etherboot.org/mailman/listinfo/gpxe >> >> > > > _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
