TR Forums

jstutman · Thu Feb 09, 2006 10:40 pm

Like to start off and say thanks for allowing my presence here

To notfred, and others. Thanks for the wonderful tool, headless folding.

I however am having some "random" issues.

TFTPD32 server is running correct, It assigns Ips and the such, However It is slow at assigning Ips for xbox/ps2.vonage etc (this is not a big issue) I just seperated the networks.

My problem is the PXE linux stuff.

Following the directions, I edit the file, set everything up. When PXE is ran on the borgs. This is the last issue ever presented

Previously allocated address acked [09/02 12:00:09.741]
Read request for file <pxelinux.0>. Mode octet [09/02 12:00:09.851]
<pxelinux.0>: sent 24 blks, 11800 bytes in 0 s. 0 blk resent [09/02 12:00:09.913]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:5E:84:4A [09/02 12:12:15.132]
DHCP: proposed address 192.168.1.11 [09/02 12:12:15.538]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:5E:84:4A [09/02 12:12:17.288]
Previously allocated address acked [09/02 12:12:17.288]
Read request for file <pxelinux.0>. Mode octet [09/02 12:12:17.397]
<pxelinux.0>: sent 24 blks, 11800 bytes in 0 s. 0 blk resent [09/02 12:12:17.444]

When I hook up the video/monitor on the borg, I get

Loading (assorted numbers)
loading (assorted numbers)
Then I get
loading pxelinux.cfg

last message
could not find kernel image: linux

boot: (linux)
boot:

Does not move after this. SO I said (maybe i curropted the file) SO i tested using an untouched .cfg downloaded fron notfred. (using his info) Systems still wont get any further.

Am I missing a step? would request some help getting this going, This would be a life saver, come I ever get it working.

Thanks in advance.

Fri Feb 10, 2006 4:07 pm

Hmm, it doesn't seem to be trying to retrieve the pxelinux.cfg file looking at the server logs, and the client shouldn't be trying to get anything called "linux", the file is called "kernel".

Make sure you actually have pxelinux.cfg folder which contains the file called default, and not a file called pxelinux.cfg. Also make sure all the options are exactly as shown in the diagrams, e.g. do you have the virtual root option on?

jstutman · Fri Feb 10, 2006 4:57 pm

Thanks for the info. latest update.

Resorted to the second to newest version of tftpd32.

Everything came to life, watching my headless borgs, they are working on dbgromacs right now. SO this part is working. However, this is my current log in tftpd32....

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:11:D8:5E:84:4A [10/02 15:52:17.666]
DHCP: proposed address 192.168.1.111 [10/02 15:52:17.666]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:11:D8:5E:84:4A [10/02 15:52:19.822]
Previously allocated address acked [10/02 15:52:19.822]
Read request for file <pxelinux.0>. Mode octet [10/02 15:52:19.931]
<pxelinux.0>: sent 24 blks, 11800 bytes in 0 s. 0 blk resent [10/02 15:52:19.978]
Read request for file <pxelinux.cfg/01-00-11-d8-5e-84-4a>. Mode octet [10/02 15:52:20.072]
File <pxelinux.cfg/01-00-11-d8-5e-84-4a> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.072]
Read request for file <pxelinux.cfg/C0A8016F>. Mode octet [10/02 15:52:20.087]
File <pxelinux.cfg/C0A8016F> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.087]
Read request for file <pxelinux.cfg/C0A8016>. Mode octet [10/02 15:52:20.353]
File <pxelinux.cfg/C0A8016> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.353]
Read request for file <pxelinux.cfg/C0A801>. Mode octet [10/02 15:52:20.369]
File <pxelinux.cfg/C0A801> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.369]
Read request for file <pxelinux.cfg/C0A80>. Mode octet [10/02 15:52:20.384]
File <pxelinux.cfg/C0A80> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.384]
Read request for file <pxelinux.cfg/C0A8>. Mode octet [10/02 15:52:20.384]
File <pxelinux.cfg/C0A8> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.384]
Read request for file <pxelinux.cfg/C0A>. Mode octet [10/02 15:52:20.400]
File <pxelinux.cfg/C0A> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.400]
Read request for file <pxelinux.cfg/C0>. Mode octet [10/02 15:52:20.400]
File <pxelinux.cfg/C0> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.416]
Read request for file <pxelinux.cfg/C>. Mode octet [10/02 15:52:20.416]
File <pxelinux.cfg/C> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:52:20.416]
Read request for file <pxelinux.cfg/default>. Mode octet [10/02 15:52:20.431]
OACK: <tsize=138,> [10/02 15:52:20.431]
<pxelinux.cfg/default>: sent 1 blk, 138 bytes in 0 s. 0 blk resent [10/02 15:52:20.431]
Read request for file <kernel>. Mode octet [10/02 15:52:20.447]
OACK: <tsize=1886563,> [10/02 15:52:20.447]
<kernel>: sent 3685 blks, 1886563 bytes in 9 s. 0 blk resent [10/02 15:52:29.556]
Read request for file <initrd>. Mode octet [10/02 15:52:29.556]
OACK: <tsize=10285056,> [10/02 15:52:29.556]
<initrd>: sent 20089 blks, 10285056 bytes in 50 s. 0 blk resent [10/02 15:53:19.119]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:11:D8:5E:84:4A [10/02 15:53:23.103]
DHCP: proposed address 192.168.1.111 [10/02 15:53:23.103]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:11:D8:5E:84:4A [10/02 15:53:23.212]
Previously allocated address acked [10/02 15:53:23.212]
Read request for file <latest.192.168.1.111.1>. Mode netascii [10/02 15:53:26.072]
File <latest.192.168.1.111.1> : error 2 in system call CreateFile The system cannot find the file specified. [10/02 15:53:26.072]

cheesyking · Fri Feb 10, 2006 7:27 pm

I think that's normal.

The PXE client is just searching through possible configuration files until it finds one that applies to your node's IP address.

It starts off looking for one specifically for that IP (in hex) and then tries looking for a file for a less and less similare IP address until it just uses the default one.

craigon69 · Sat Feb 11, 2006 1:29 pm

Thanks for this post. I had the same issue using TFTP 2.82. I was racking my brains trying to figure out what I did wrong! I read your above fix and noticed that there was a new TFTP version 2.83 which was posted yesterday (2/10), so I tried that and I am now folding away on 2 diskless clients (verified by hooking up my monitor). Awesome!

Notfred. (or whomever), is there a way to monitor the clients remotely from XP? I’m referring to this comment in your HOWTO “….This can help in determining the IP addresses of them for you to point a web browser at to monitor them” . How’s that work?

jstutman · Sat Feb 11, 2006 1:52 pm

type the IP address of the specific diskless node into your browser.

using a /1 lists all the files.

example

192.168.111/1/

However EMIII is unable to monitor it via this way, if only there was a fix.

Is there?

seanf · Mon Feb 13, 2006 5:01 pm

First of all, please let me apologize if this is not the correct forum or post, but it seems to be very close to what I am trying to do. I have a Toshiba Satellite 5205 - the CD drive died and now it won't boot, freezing on app440.sys

I have the restore CD and have tried to use PXE boot to restore.
http://home.allegiance.tv/~joem298/

I am able to get pxelinux.0 to load, but cannot get the msdos image to boot.

Intel(R) Boot Agent FE v4.1.09
Copyright (C) 1992-2002, Intel Corporation

CLIENT MAC ADDR:00 08 0D C9 01 53 GUID: 1ABCE900 23C0 11D7 800D AAD253087854
CLIENT IP: 192.168.1.10 MASK: 255.255.255.0 DHCP IP: 192.168.1.100

PXELINUX 2.10 2004-06-18 Copyright (C) 1994-2004 H. Peter Anvin
UNDI data segment at: 00094550
UNDI data segment size: 94B0
UNDI code segment at: 0009DA00
UNDI code segment size: 21E0
PXE entry point found (we hope) at 9DA0:0106
My IP address seems to be C0A8010A 192.168.1.10
ip=192.168.1.10:0.0.0.0:0.0.0.0:255.255.255.0
TFTP prefix:
Trying to load: pxelinux.cfg/01-00-08-0d-c9-01-53
Trying to load: pxelinux.cfg/C0A8010A
Trying to load: pxelinux.cfg/C0A8010
Trying to load: pxelinux.cfg/C0A801
Trying to load: pxelinux.cfg/C0A80
Trying to load: pxelinux.cfg/C0A8
Trying to load: pxelinux.cfg/C0A
Trying to load: pxelinux.cfg/C0
Trying to load: pxelinux.cfg/C
Trying to load: pxelinux.cfg/default
Could not find kernal image: linux
boot:

and it hangs there

I have created a directory called h:\tftpboot where I am running Tftpd32 from. The ms dos image "bootd.img" is in this directory. There is a subdirectory called pxelinux.cfg, where I have the following "default" file:

default boot
prompt 0
say booting...
label boot
kernel memdisk
append initrd=bootd.img

I am pretty sure it is not finding this as there is no "booting..." echoed to screen on the laptop

My Tftpd32 settings:
PXE Compatabilty - on
Show Progress Bar - on
Allow \ as virtual root - on

I've been at this for 2 days!! :-?

So any help will be greatly appreciated!

cheesyking · Tue Feb 14, 2006 5:56 am

yeah it's probably the wrong forum...

also you can't network boot MS dos, it's just impossible.

You might be able to network boot a copy of linux and use that to repair the file system. How much do you know about linux?

EDIT: just read a little bit more into the site you'd linked to.

Doing it that way should work however it may be easier to get an adapter to plug the laptop's hard drive into a desktop and repair it that way.

Either that or fix the CD drive which shouldn't cost too much. Most laptop drives are interchangeable (once you've taken all the little bits of plasic off that hold it in the case)

As for the problem you've got at the moment I'd suspect an issue with the pxelinux.0\default file. Make sure it isn't saved as a txt file (it shouldn't show up in explorer with a notepad icon!). It may also be necessary to create the file with a Unix compatible text editor like notepad++.

Tue Feb 14, 2006 9:04 am

To boot from an external USB CD drive may be another option.

Tue Feb 14, 2006 9:57 am

Cheesyking - check the link seanf posted. It's an MS-DOS floppy image booting using PXELinux.

seanf - this is really the wrong forum, Networking or Linux ones would be better. Having said that, it is not picking up the correct pxelinux.cfg/default file because it is trying to load a kernel called "linux" and not the kernel called "memdisk". Try different versions of the TFTPD32 as reported by the others above, seems there's a version out there that doesn't send the correct files.

cheesyking · Tue Feb 14, 2006 10:13 am

notfred wrote:
Cheesyking - check the link seanf posted. It's an MS-DOS floppy image booting using PXELinux.

seanf - this is really the wrong forum, Networking or Linux ones would be better. Having said that, it is not picking up the correct pxelinux.cfg/default file because it is trying to load a kernel called "linux" and not the kernel called "memdisk". Try different versions of the TFTPD32 as reported by the others above, seems there's a version out there that doesn't send the correct files.

just did so dude...

Logan[TeamX] · Wed Feb 15, 2006 8:21 am

It's vital that your PXELINUX image be in the same working directory as your TFTP executable. You CAN do it from other folders, but both the TFTP Server and DHCP nodes need to know this!

I set it up last night using NotFred's diskless how-to with TFTPD 2.83 and it works like a champ. The only real difference here is that in 2.81 and 2.82 (I think) the DHCP and TFTP server parts are separate entities. In 2.83, they're back under the TFTPD program together.

If you follow NotFred's how-to explicitly, you'll be fine as long as your NICs play ball.

TR Forums

notfred, diskless folding problems

notfred, diskless folding problems

That fixed it for me too! Any way to monitor them?

PXE Booting for system restore

Who is online