Re: [Etherboot-discuss] WinPE boot failure
Brought to you by:
marty_connor,
stefanhajnoczi
From: Itay G. <ita...@gm...> - 2008-01-29 17:03:26
|
Hi Striper, Well, I checked the intergirty of the file which was good. I tried today the same configuration: dhcp, tftp on a built in PXE of a simple nic. It loaded pxeboot.n12 and later asked for bootmgr.exe! Conculsion: the problem is in gPXE. Itay dhcp configuration: " allow booting; allow bootp; ddns-update-style none; ddns-updates off; shared-network "my_network" { subnet 11.4.3.0 netmask 255.255.255.0 { #option dhcp-client-identifier = option dhcp-client-identifier; option subnet-mask 255.255.255.0; option domain-name "lab.mtl.com"; option domain-name-servers 10.0.0.1; default-lease-time 28800; max-lease-time 86400; } } host sw130-et { next-server 11.4.3.129; #option root-path "/tftpboot"; filename "pxelinux.0"; fixed-address 11.4.3.131; hardware ethernet 00:02:c9:00:21:39; } " On Jan 24, 2008 7:01 PM, striper <str...@gm...> wrote: > On Jan 24, 2008 10:37 AM, Itay Gazit <ita...@gm...> wrote: > > > > Striper, > > > > Thanks for the detailed information. > > > > Well, I still didn't succeed booting winpe. > > Bummer, we'll have to keep fishing. > > > I will try focus my problem: > > PXE succefully loads winpe.0 which is pxeboot.n12. > > The problem I have that after it loaded pxeboot.n12 it should ask for a > file > > called "/bootmgr.exe" or "Boot/bootmgr.exe" or " bootmgr.exe" > (something > > with bootmgr.exe). I don't know why but myne is asking for a file called > "/" > > ??? > > The fact that it is asking for a / forward slash is a problem. > > > I tried everything with the tftp mapping and I even tried it on windows, > no > > change it always ask for a file called "/". > > You said "I even tried it on windows". I think that means that you > tried running your tftpd on Windows. > > The / forward slash makes me very suspicious. The MSFT code would > never use a / forward slash because the MSFT code thinks it is talking > to a Windows tftpd; it would always use \ backslash as a path > separator. > > I suspect that your dhcpd is still passing something that has a / in it. > > > Maybe it's something related to a configuration to gPXE? Did you try > booting > > winpe 2.0 with gPXE? > > No, I have not yet tried booing WinPE using gPXE. I am currently > traveling and will not be able to try gPXE until next week. > > You said that you tried it on Windows, and I assumed that you were > talking about tftpd. If you are trying it in a pure Windows > environment, with a Windows dhcpd + tftpd, and if you are *positive* > that you are using no / forward slash characters in your the service > config on your Windows dhcpd, then that would point the finger at > gPXE. > > Let's do the following: > > * confirm your dhcpd settings. Please post to mailing list > > * restart your dhcpd to ensure that it is running with your > configuration: > # service dhcpd restart > .OR. > restart the service on Windows > > * confirm the integrity of your pxeboot.n12 file. md5sum hash on my > system is: > [striper@plumisland] md5sum pxeboot.n12 > 57113b2babb9ac4025506ca30d909a28 pxeboot.n12 > > * You know how to use tcpdump. Use the 'ether host <MAC-ADDRESS>' > filter to capture all traffic that is going to your boot machine. Send > it to me off of the mailing list. > > Below you will find a snippet from my /var/log/messages on my Fedora 8 > dhcpd server. Client is a Broadcom NIC not using gPXE. > > > striper > > --- > > Jan 18 00:23:50 plumisland in.tftpd[9707]: RRQ from 192.168.101.99 > filename winpe20.0 remapped to winpe20/pxeboot.n12 > Jan 18 00:23:50 plumisland in.tftpd[9708]: RRQ from 192.168.101.99 > filename bootmgr.exe remapped to winpe20/bootmgr.exe > Jan 18 00:23:51 plumisland in.tftpd[9709]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:23:51 plumisland in.tftpd[9709]: tftp: client does not accept > options > Jan 18 00:23:51 plumisland in.tftpd[9710]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:23:51 plumisland in.tftpd[9711]: RRQ from 192.168.101.99 > filename \boot.ini > Jan 18 00:24:06 plumisland in.tftpd[9713]: RRQ from 192.168.101.99 > filename \Boot\BCD remapped to winpe20/bcd.striper > Jan 18 00:24:06 plumisland in.tftpd[9713]: tftp: client does not accept > options > Jan 18 00:24:06 plumisland in.tftpd[9714]: RRQ from 192.168.101.99 > filename \Boot\BCD remapped to winpe20/bcd.striper > Jan 18 00:24:06 plumisland in.tftpd[9715]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:24:06 plumisland in.tftpd[9715]: tftp: client does not accept > options > Jan 18 00:24:06 plumisland in.tftpd[9716]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:24:06 plumisland in.tftpd[9717]: RRQ from 192.168.101.99 > filename \hiberfil.sys > Jan 18 00:24:06 plumisland in.tftpd[9718]: RRQ from 192.168.101.99 > filename \winpe.wim remapped to winpe20/winpe.wim > Jan 18 00:24:06 plumisland in.tftpd[9719]: RRQ from 192.168.101.99 > filename \boot.sdi remapped to winpe20/boot.sdi > Jan 18 00:24:06 plumisland in.tftpd[9718]: tftp: client does not accept > options > Jan 18 00:24:07 plumisland in.tftpd[9720]: RRQ from 192.168.101.99 > filename \boot.sdi remapped to winpe20/boot.sdi > Jan 18 00:24:07 plumisland in.tftpd[9719]: tftp: client does not accept > options > Jan 18 00:24:07 plumisland in.tftpd[9721]: RRQ from 192.168.101.99 > filename \winpe.wim remapped to winpe20/winpe.wim > Jan 18 00:24:43 plumisland in.tftpd[9723]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:24:43 plumisland in.tftpd[9723]: tftp: client does not accept > options > Jan 18 00:24:43 plumisland in.tftpd[9724]: RRQ from 192.168.101.99 > filename \Boot\Fonts\wgl4_boot.ttf remapped to > winpe20/fonts/wgl4_boot.ttf > Jan 18 00:39:43 plumisland xinetd[9690]: EXIT: tftp status=0 pid=9693 > duration=957(sec) > |