@george1421 switch to working branch. Copy the packages/tftp folder contents to /tftpboot. Switch back to dev-branch or master. Do not run the installer.

@jonathan-cool Remove the 2 in the fixed file and deploy the image to a client…

@sebastian-roth not a clue. Only guess I would have is image/snapin replication.

Kernel 4.13.4 has been updated to include the 0927 identifier. Please update to working branch which will enforce your kernels to update to the latest on our site. Or you can do:

wget -O /var/www/fog/service/ipxe/bzImage https://fogproject.org/kernels/bzImage
wget -O /var/www/fog/service/ipxe/bzImage32 https://fogproject.org/kernels/bzImage32

Then test and let us know if it’s working for you please?

@ravigon No problem.

I would also check if the FOGImageSize service is enabled which you should be able to do with:

sudo systemctl enable FOGImageSize

This should ensure it can start on reboots.

@ravigon 127.0.0.1 is not the proper IP address at all. That means to literally reference itself.

While 127.0.0.1 is the “node” itself, it almost sounds like the IP that was configured during initial install has changed from what the new network IP address is.

@ravigon Please try:

systemctl restart FOGImageSize

Followed by:

systemctl status -l FOGImageSize

@kkroflin said in Init - Support for classless static route:

https://github.com/kkroflin/fog-init-scripts

This is your own thing? I mean adding classless static routes isn’t difficult or anything, but your case is the ONLY one I’ve heard of. That’s not to say others wouldn’t benefit from this, but this seems like a very edge case to me right now. That said, you could use postinit scripts to actually achieve this same effort without having to change the init’s at all.

I should add to this thread too, in that this size on server is a nice to have feature but should not impact any ability to actually image a device.

Please open the d1.fixed_pattitions file and add :1 to the file. This should fix it for you.