@Tom-Elliott Yes, I’ve force set the password everywhere.

What table should I check in the database for the password? There is a = in the (auto-generated) password so that could possible cause issues then.

What version of the trunk are you on?

Latest trunk version.

I just noticed though that it seems to change the fog user password every time I update it (even though the password in /opt/fog/.fogsettings is 100% correct, I copy pasted it from TFTP Server settings before updating)

How do you know ftp is not working? (i.e. what problems are you experiencing)

FOG moves the images using FTP from /images/dev to /images, which it fails to do for me.

Does any of the log files in /opt/fog/logs show any clues to the problem?

There’s only groupmanager.log and servicemaster.log in there

Servicemaster reports all FOG Services running.

Nothing relevant in groupmanager.log

Hi, I’ve been over the FTP troubleshooting guide, followed each step and confirmed that FTP is indeed working, correct passwords everywhere (I can copy paste the password from any location into the ftp client and it works), but images are unable to be moved.

The FTP config file is identical to the one on the wiki as well. Ownership and permissions should all be fine. (0777, fog:root)

As for the log files, I can’t see any of the FOG Service log files anymore.

Doesn’t CRC check for broken sectors? Is it possible the target HDD has a couple of broken sectors?

Navigate to iPXE Menu configuration.

Uncheck the default item checkbox for local

Check the default item checkbox for usb boot

@Hanz You probably have to kill the udpsender process as well?

This often happens when there are two DHCP servers running on the same network.

@Miguel-Palacios For some people updating the firmware helps, if that’s a possibility at all it might be worth giving it a go.

@Miguel-Palacios What’s the output of rpcinfo -p?

@Miguel-Palacios I believe it only gives output if there’s an error, so that’s good news already.

@Miguel-Palacios Hi, can you run exportfs -r on your FOG Server, post the output here and try again on the FOGclient? (if it doesn’t work, try exportfs -r a second time)

@wdmartin I’m not sure, I’ve never tried this, it should announce its proper size and thus work, but I guess it wasn’t doing so until you expanded it?

Is the original partition 58gb in size or is there 58gb of data?

Either way fixed size is better if disk intensive activity is going to take place anyway.

@wdmartin Is the virtual disk a dynamic one by any chance?

@Sebastian-Roth Would it be hard to implement an error warning specifically for hard drive size?

@Wayne-Workman If I’m not mistaken matching doesn’t work in proxy mode (meaning BIOS + UEFI compatibility is not possible in dnsmasq)

Hi, there should be a field at your Storage Node that asks you to specify the snapin folder location.

@eric0626 If the PXE is located on the same server all you should need is

chain pxelinux.0

If it’s located on another server then

chain tftp://10.2.5.239/pxelinux.0

Should work.

Assuming your tftp directory is /tftpboot you will need the following:

/tftpboot/pxelinux.0
/tftpboot/pxelinux.cfg/default (<- config file)

And of course other relevant PXE files.

You have to chain the pxelinux.0 file, not the configuration file itself.

And your default file should be in the pxelinux.cfg folder which should reside at the root of your tftp directory

@inafog9 Are you using DNSMasq by any chance?