Hi,

Thanks george1421. The second storage node was running 1.5.6. As it is still in a test environment, I completely rebuilt it from scratch. All working fine now.

Yes, the remote storage node is a full FOG server, so I will export / import the metadata.

Thanks again 🙂

@kmonroe79 said in Starting cmain( )...:

This now brings my screen to black with flashing cursor 😞 I can’t seem to find a happy balance

Using which settings exactly??

@kburns Yes, George is probably right. Take a look at /tftpboot/default.ipxe text file and put in the correct IP. It’s important you read this wiki artikle: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

@cammykool It can do remote execution, printer management, power management, login recording, and other things. I’ve used it to run scripts, deploy software, and other things. Check out these wiki articles below, they might help you understand the capabilities.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

There’s also a ton of stuff on the forums about printer management. Here is one with some detail: https://forums.fogproject.org/topic/8051/printer-deployment?page=1 though there’s probably hundreds of topics about printers.

Updated the URL in the official code (ref).

@ITCC Switch your DHCP config to point to ipxe.pxe instead of undionly.kpxe and the issue should go away.

@george1421
Changing the settings in the default.ipxe file worked! Man this community is great! I’m going to update my documentation to make note of this so in the event we move subnets again we can tackle this same day!

@doubleve You only need tftp if you want to boot from the nas. If you have a real fog server on the same network you can use that. For a storage node you only need NFS and FTP service.

thanks, i figure up what’s the problem, i’ve add corrupted lines on /etc/fstab.
thanks for everything.
everything is working now.
🙂

@Beyondlimitation said in PXE Client tries to find wrong file:

By the way, if i copy “undionly.kpxe”, paste it in directory “/tftpboot” and rename it to “undionly.kpxe.0”
pxe boot successfully works

While I see you have it sorted out, requiring the boot file to end in a “.0” was a requirement of DNSMASQ before 2.76 (as well as syslinux). With 2.76 and later its just the file name. The “.0” requirement was removed since that is a bios related thing. What version of dnsmasq are you running (i.e. dnsmasq -v)

@kwisher Well life may be better on the dev branch. Why I asked if you were on 1.5.7.55 or later, stay there. FOG 1.5.8 is almost release. 1.5.7 had a few bugs where 1.5.7.55+ in the dev branch fixed.

@Spicoli Thanks! RAID to AHCI worked for me.

@tlehrian It would be really great if you could test this fairly soon so we have a little bit of time in case it needs further work. The earlier we know the better! We can’t guarantee a quick fix some time in January when you really need it.

@george1421 Morning George
the issue is resolved - it was the ‘-M’. There was no <space> at the beginning so iPXE clearly doesn’t like ‘-’ at the beginning. Thanks again 😄

@fogQuestions said in Can fog deploy images to a single partition?:

However, whenever I deploy images to from my FOG server to my computer, the iPXE software gets wiped by my image.

May I ask why you have iPXE installed on disk at all? Usually this is send to the client on PXE boot on the fly and there is no need to have it on disk.

Can fog deploy images to a single partition? If so how?

Yes you can define an image in the web UI to capture/deploy only one single partition. The problem with this is that on the target machine you already need to have the correct partition layout set from an earlier deploy as we don’t touch that but simply deploy the contents of that one single partition set in the image definition.

Hey @Daniel-Miller and @george1421 thanks again for your effort in helping me figure this out. I think the complexity (for me) for what I was about to do scared me into thinking of a roundabout approach to solving this issue. I think I found a better solution than what I was originally trying to do (and WAY simpler). I will post here in case this will be of use for anyone in the future.

Rather than appending a date to the hostname so I can change the computer name I decided to start out with the date appended to the hostname so that renaming the computer would be exactly how I want it to be then for my other requirements (adding the user to be admin of the computer) I simply removed the date from the hostname to come up with the username.

Basically, if my username is bobsmith and today’s date is 2019-12-06, I will name the host: bobsmith191206 then in my Powershell script I just need to set $userName = $env:computername -replace '[0-9]' then the hostname remains bobsmith191206 and now I have a variable $userName that now equals BOBSMITH

Anyhow, that is one of those… so easy it is dumb solutions. Not sure why I didn’t think of it earlier. Thanks again you guys for helping me to think outside of the box I stuck myself in.

Found and should be fixed if you do the latest pull.

Thank you,

Of note, I’m calling it 1.6 because when we do release it, that’s what this will become.

It is using the current latest version (1.5.7) and the .XXX after is the number of commits ahead of the master branch the working-1.6 branch is at.

@franck25 said in How to boot uefi on ltsp server via ipxe fog:

I find myself facing a problem of boot on my server “ltsp ubuntu”

Please take a picture of the screen where we see what goes wrong and post that here.

@sudburr In my FOG installation (1.5.5), the value for DATABASE_PASSWORD in config.class.php is in single quotes, so the sed statement for needs to be:

sed -i.bak 's|DATABASE_PASSWORD', '<oldpassword>'|DATABASE_PASSWORD', '<newpassword>')|g' /var/www/html/fog/lib/fog/config.class.php

I would also like to note that the values in .fogsettings are only initial values for during installation. So it does not matter if you patch the password there really (not 100% sure though).