Re: gPXE chainloading hangs at "gPXE initialising devices..."

Good day Christian,

Does your e-mail on September 3rd at 15:34 mean that Marty's gpxelinux.0
suggestion is working perfectly for you?  Your e-mail made it appear so.
If you are having difficulties SAN-booting, it can be useful to try the
following steps:
- Attach to the SAN from another computer (or working OS, at least) to
verify that the SAN is functional at the target name you have specified
in your DHCP configuration
- Obtain a gPXE Command-Line Interface (CLI) by pressing Control-B when
gPXE prompts you, then attempt the SAN-boot from the CLI with:

gPXE>sanboot iscsi:ip.ad.dr.ess::::iqn.2009-01.someIdentifier.foo

- Note any error codes gPXE might yield and include them in any future
e-mail in regards to this issue

However, your scenario is a bit confusing...  Your boot appears to
resemble:

PXE (Intel) -> gpxelinux.0 [which is: gPXE (undionly.kkpxe) -> PXELINUX
(pxelinux.0)] -> SAN

But the DHCP root-path option is used by gPXE, not PXELINUX.  If you
wish to SAN-boot from PXELINUX, or a menu system provided by PXELINUX,
you will likely need to use the sanboot.c32 module included with the
Syslinux boot-loader suite.  Your PXELINUX config-file might resemble
the following:

LABEL mysanboot
  COM32 sanboot.c32
  APPEND iscsi:ip.ad.dr.ess::::iqn.2009-01.someIdentifier.foo

I hope this helps, if you are still having trouble.

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july