Windows Diskless Folding!!!

[unhappy_mage]

Does your system allow setting different flags for each layer?

Sorry I missed this. My system autoconfigures, so that it looks at how "big" the box is and determines what flags to give FAH. It's based on cpu flags (if it has SSE, MMX and the like), how much memory the machine has, and cpu speed. You could theoretically change the parameters, but they're fairly reasonable.

The simplest way to deal with HT is, unfortunately, turning it on and off in BIOS. Linux will see all the virtual processors, and (with my system, anyways - haven't looked at what this does) start one instance of FAH per virtual CPU. Thus, if HT is on it starts 2N, if it's off just N.

 

[iceage]

Looking for some help with this. I have tftpd32 loaded and when I boot the diskless client it gives me this in the TFTP Server tab.

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [27/03 19:07:22.781]
DHCP: proposed address 192.168.1.123 [27/03 19:07:22.781]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [27/03 19:07:24.781]
Previously allocated address acked [27/03 19:07:24.781]

And thats all. No network activity showing that its loading a core and WU. In the 'current action' field it says, "Previously allocated address acked".

I'm using a linksys router as a switch, with the server PC plugged into port 3 and the diskless workstation plugged into port 2. Router is powered on.

Needless to say, I'm a network n00b. Any help is appreciated!!

Btw, currently I'm trying to use 1 PC-DL as the server and another PC-DL as the diskless workstation.

 

[iceage]

Ok. I had to set the wireless network connection and the local area network connection to have the same default gateway. At this point I get all the way to the diskless workstation looking to 'Resolve www.stanford.edu...failed: Temporary failure in name resolution." Then it reports error code 1 - "wine: cannot find 'FAH502-Console.exe"

Here is the take from the TFTPD server...

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:37:22.984]
DHCP: proposed address 100.110.120.140 [28/03 22:37:22.984]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:37:25.015]
Previously allocated address acked [28/03 22:37:25.015]
Read request for file <pxelinux.0>. Mode octet [28/03 22:37:25.015]
Using local port 3932 [28/03 22:37:25.015]
<pxelinux.0>: sent 24 blks, 11800 bytes in 0 s. 0 blk resent [28/03 22:37:25.031]
Read request for file <pxelinux.cfg/01-00-11-d8-14-98-8b>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\01-00-11-d8-14-98-8b> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E788C>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E788C> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E788>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E788> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E78>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E78> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646E7>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646E7> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646E>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646E> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/64>. Mode octet [28/03 22:37:25.125]
File <pxelinux.cfg\64> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.125]
Read request for file <pxelinux.cfg/6>. Mode octet [28/03 22:37:25.125]
File <pxelinux.cfg\6> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.125]
Read request for file <pxelinux.cfg/default>. Mode octet [28/03 22:37:25.125]
OACK: <tsize=143,> [28/03 22:37:25.125]
Using local port 3942 [28/03 22:37:25.125]
<pxelinux.cfg\default>: sent 1 blk, 143 bytes in 0 s. 0 blk resent [28/03 22:37:25.140]
Read request for file <kernel>. Mode octet [28/03 22:37:25.406]
OACK: <tsize=1886563,> [28/03 22:37:25.406]
Using local port 3943 [28/03 22:37:25.406]
<kernel>: sent 3685 blks, 1886563 bytes in 1 s. 0 blk resent [28/03 22:37:26.343]
Read request for file <initrd>. Mode octet [28/03 22:37:26.359]
OACK: <tsize=10285056,> [28/03 22:37:26.359]
Using local port 3944 [28/03 22:37:26.359]
<initrd>: sent 20089 blks, 10285056 bytes in 5 s. 0 blk resent [28/03 22:37:31.453]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:38:51.609]
DHCP: proposed address 100.110.120.140 [28/03 22:38:51.609]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:38:51.625]
Previously allocated address acked [28/03 22:38:51.625]
Read request for file <latest.100.110.120.140.2>. Mode netascii [28/03 22:38:51.687]
File <latest.100.110.120.140.2> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:38:51.703]
Read request for file <latest.100.110.120.140.1>. Mode netascii [28/03 22:38:51.703]
File <latest.100.110.120.140.1> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:38:51.703]

Any ideas?

 

[InTheFlow]

Do you have to have a copy of XP or Win2K for each headless system you set up for folding?

 

[ghettocomp]

Ok. I had to set the wireless network connection and the local area network connection to have the same default gateway. At this point I get all the way to the diskless workstation looking to 'Resolve www.stanford.edu...failed: Temporary failure in name resolution." Then it reports error code 1 - "wine: cannot find 'FAH502-Console.exe"

Here is the take from the TFTPD server...

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:37:22.984]
DHCP: proposed address 100.110.120.140 [28/03 22:37:22.984]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:37:25.015]
Previously allocated address acked [28/03 22:37:25.015]
Read request for file <pxelinux.0>. Mode octet [28/03 22:37:25.015]
Using local port 3932 [28/03 22:37:25.015]
<pxelinux.0>: sent 24 blks, 11800 bytes in 0 s. 0 blk resent [28/03 22:37:25.031]
Read request for file <pxelinux.cfg/01-00-11-d8-14-98-8b>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\01-00-11-d8-14-98-8b> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E788C>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E788C> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E788>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E788> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.093]
Read request for file <pxelinux.cfg/646E78>. Mode octet [28/03 22:37:25.093]
File <pxelinux.cfg\646E78> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646E7>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646E7> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646E>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646E> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/646>. Mode octet [28/03 22:37:25.109]
File <pxelinux.cfg\646> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.109]
Read request for file <pxelinux.cfg/64>. Mode octet [28/03 22:37:25.125]
File <pxelinux.cfg\64> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.125]
Read request for file <pxelinux.cfg/6>. Mode octet [28/03 22:37:25.125]
File <pxelinux.cfg\6> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:37:25.125]
Read request for file <pxelinux.cfg/default>. Mode octet [28/03 22:37:25.125]
OACK: <tsize=143,> [28/03 22:37:25.125]
Using local port 3942 [28/03 22:37:25.125]
<pxelinux.cfg\default>: sent 1 blk, 143 bytes in 0 s. 0 blk resent [28/03 22:37:25.140]
Read request for file <kernel>. Mode octet [28/03 22:37:25.406]
OACK: <tsize=1886563,> [28/03 22:37:25.406]
Using local port 3943 [28/03 22:37:25.406]
<kernel>: sent 3685 blks, 1886563 bytes in 1 s. 0 blk resent [28/03 22:37:26.343]
Read request for file <initrd>. Mode octet [28/03 22:37:26.359]
OACK: <tsize=10285056,> [28/03 22:37:26.359]
Using local port 3944 [28/03 22:37:26.359]
<initrd>: sent 20089 blks, 10285056 bytes in 5 s. 0 blk resent [28/03 22:37:31.453]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:38:51.609]
DHCP: proposed address 100.110.120.140 [28/03 22:38:51.609]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:118:14:98:8B [28/03 22:38:51.625]
Previously allocated address acked [28/03 22:38:51.625]
Read request for file <latest.100.110.120.140.2>. Mode netascii [28/03 22:38:51.687]
File <latest.100.110.120.140.2> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:38:51.703]
Read request for file <latest.100.110.120.140.1>. Mode netascii [28/03 22:38:51.703]
File <latest.100.110.120.140.1> : error 2 in system call CreateFile The system cannot find the file specified. [28/03 22:38:51.703]

Any ideas?

No Ideas here, It actually looks like a DHCP server problem. Have you entered the IP and Mac addresses of each of the layers into the server computers registry? that may make a difference.
Also.. You are using wireless? that may be something too..

 

[iceage]

I talked with some people over at tech forums where notfred posts alot of stuff. It seems my wireless connection and my wired connection to the diskless stations is conflicting. I'll have to move my wireless router upstairs and run the diskless stations by wire to the router. I have wireless PCI cards and I'll have to use those on the downstairs computers. No biggie, just didn't want to move things around any more than necessary.

 

[ghettocomp]

I talked with some people over at tech forums where notfred posts alot of stuff. It seems my wireless connection and my wired connection to the diskless stations is conflicting. I'll have to move my wireless router upstairs and run the diskless stations by wire to the router. I have wireless PCI cards and I'll have to use those on the downstairs computers. No biggie, just didn't want to move things around any more than necessary.

kind of what I thought, looked like two DHCP servers fighting for control. Did you get everything resolved yet?

 

[Rpkole]

thankyou ghetto i just got 2 diskless rigs up and running the would have ben headless but they have onboard video

 

[AlabamaCajun]

"Thread Diving"

This thread could be a sticky! :hint:

 

[robertm]

You should not need to disable DHCP on your router not sure you need to enable the DHCP on the tftpd software. If I remember correct this type of setup uses bootp or some such network layer. If so it will find the tftpd server without it running the DHCP server. Once I get some of my older systems up and running I will try this out and give more detail. I used to run a number of system at work off diskless for time clocking function with out accounting software. I had different DHCP and bootp/tftpd servers. But these where both linux based systems so I need to do some testing to confirm setups.

 

[ghettocomp]

I have never disabled the DHCP of my smoothwall or of the TFTPD server either. There is an option where you enter the Mac address of each diskless layers NIC and your desired IP address into the windows registry of the server and as the BootP picks up the mac address, It assigns the IP and runs from there, 99.9% (PFA) of the time with no errors.

The whole trick of getting it to run properly is to make sure you follow the instructions given. If you get creative like I tried at first, it will fail. Only problem i have now is that I can't find any way to run Beta WUs.

 

[Rpkole]

hey ghetto do you know why evey time the client is retarted it d/l a new core
and is there any way to set it up so it will jsut get the core off the main box

 

[ghettocomp]

It has to download the core and client each time directly from Stanford to avoid violating any of their rules. besides, it is not a bad thing to start fresh with each restart. the only thing saved on the main box is the work that has been done, Just have to allow around 2 hours for each backup to happen.

 

[iceage]

I need to get a kill-a-watt and find out how much I'm saving on power with the headless/diskless setup. I know how much I'm saving on vid cards/HDs!

 

[ErikD]

I have been thinking of doing something like this with some spare P3s I have sitting around. So all of the work and usual config files that would go in the F@H folder are saved to the server in some folder?

Now I just need to find some cheap P# motherboards and PXE capable NICs.

 

[the garynator]

I have been thinking of doing something like this with some spare P3s I have sitting around. So all of the work and usual config files that would go in the F@H folder are saved to the server in some folder?

Now I just need to find some cheap P# motherboards and PXE capable NICs.

you don't have to worry about the wu's or config files sept when initially setting it up... There's a main one that the server uses to send the os to the layer...

The wu's aren't stored like they are in normal folding, they are in the form of backup files which are only backed up every 2 hours (unfortunately).

Oh, and you don't need a pxe compatible nic either, just a boot disk, whether it be a usb thumb drive (assuming the board is capable of booting from usb) or a floppy disk. All this disk does is load the nic and tell the computer to boot off the network. All the info needed to make one of these is located on that page (at least linked).

If you take a crack at it (and i'd suggest you do, it's absolutely wonderful) make sure you follow the directions to a T the first couple times so you can get used to how it works. If you have problems feel free to ask, but try going through the how-to again and make sure everything's correct. I had a problem where i named the "pxelinux" "prelinux" and luckally I looked at the log file a couple of times and was able to fix it in about 5 minutes.

Good luck!

 

[ErikD]

Well funny story. I have a bunch of P3s sitting in a cabinet, and a small ESD bag full of PC100 SDRAM sitting on my desk. So all I would need to complete this is a motherboard, PSU, and NIC. Well on my way home tonight I spotted an old PC in the trash. Wouldn't you know its a P3!

Well I gutted it to try this out. I got the TFTP server running, and I saw the request for an address, etc. Now how do I know that the client is actually folding like it should be? Wait 2 hours to see a backup file? How long should it take before I can see the web monitoring page? Reason I ask is that when I looked in on it using the onboard video it was just sitting there saying TFTP......... and then a curser. Couldn't ping it or view the web page.

My ultimate plan is to fill my server closet with diskless folders as I have the time/money/parts. Probably look into doing multiple per PSU diskless/headless pure network boot.

 

[ghettocomp]

Ditto!

I would suggest for ease of anything to use the Folding CD for older motherboards. The CD eliminates most headscratching and questions. The CD itself contains all the files that the server would download to the layers anyway. Once the OS and F@H is loaded, the computer no longer has any need for the CD so power usage is very minimal anyway. Just make sure after 2 hours that your layers are backing up to the TFTPD32 server.

Another Tip: watch for the MAC address of your NIC and enter it into the registry using the instructions (to the letter) given by the author of TFTPD32. This way if the computer is offline for any time for maintenance or whatever and restarted, that layer will get the same IP and pick up where it left off.

 

[ErikD]

With some fooling around I got it working totally diskless. Turns out that not only did I need to set the BIOS to PXE boot I also needed to set the NIC to PXE boot. It is now folding diskless!

Not for long thoush as sitting on the floor of my room it is just waiting to be stepped on. Now that I know it works I will be running some more CAT 5 cables into my server closet for the farm.

 

[ghettocomp]

Hey hey!! another Closet folder...