@Sebastian-Roth Yeah, it was honestly my fault. Normally I’d capture and deploy immediately after to test, but these past few weeks have been ridiculously insane for me and my machine to image allocations haven’t been as up to date as they normally would’ve been.

I noticed this happened once before with a Windows image, but it was related to the dirty bit and another issue I found here. All in all I wanted to at least report and give this a go, I apologize for taking your time but as always appreciate the help. If this does happen again, I’ll be sure to give those kernels a go and report back here the results.

@Sebastian-Roth Thanks!

@Sebastian-Roth Well I feel silly, I should’ve done that to start. Apologies for the stupid question, thanks and once backups are done updates are next on the list.

@Tom-Elliott @Sebastian-Roth Understood, thanks again guys!

@Wayne-Workman Interesting, I found our problem was the initial setup of the Ubuntu server that hosts FOG was set to allow auto-updates. This will come in handy for future installs, thanks!

I’m not understanding your question. Or at least not understanding what you mean or are intended to obtain.

FOG, itself, knows nothing about your Drives used/free space. We use a block based imaging tool called partclone. Partclone can detect the used vs. free/empty space.

All Fog does is use utilities that are readily available to do all the work. FOG just automates the usage and mathematics of these things to help with resizing and expanding.

I’m sure this isn’t the answer your looking for, but to understand what I mean you’d have to look at the source code. https://github.com/fogproject/fos

Specifically the bin and usr/share/fog locations.
https://github.com/FOGProject/fos/tree/master/Buildroot/board/FOG/FOS/rootfs_overlay

@Sebastian-Roth So far I’ve tried a fresh Ubuntu 16.04 install, and I’ve even used LVM and just captured as non-resizable with 0 issues. Now while this wasn’t Ubuntu 18, I did notice the machine I had the issue on originally is unable to install this OS due to something being wrong with the “file system” on the disk which for some odd reason it couldn’t format, delete, or write to. It is an SSD, and I couldn’t recreate this issue on any other box. I ran various SSD diagnostics with no errors being found so I’m stumped. I haven’t gotten to try with the exact iso posted above just yet - doing production stuff lately since I’m alone in IT currently.

@Tom-Elliott I see, the storage nodes themselves are not meant for capacity but redundancy and throughput? Is mounting a network storage location viable to expand my capacity?

A fog “image” consists of 2 parts.

The raw image files stored in /images The metadata stored in the mysql database.

You can copy all of the raw image files simply by the copy command. The metadata can easily be exported from the webgui into a csv file. With the raw data and metadata you can rebuid the images on a new fog server or whatever. If you don’t have the metadata but the raw image files you could rebuild the metadata if you are careful on how you name your images and are a good guesser for the rest. Point being, backup the image metadata with the raw data files and you will be good.

Hi,
I want to add that I have done some changes in the reports, imaging log report too, to make pre-filters and not shows all the registries.

For example, in the imaging log report you can do a a prefilter by image name, user name or hostname. In this way, the result is more small and you don’t need erase registries in the database.

The new version of the reports are available in the “working” branch

Haha I know that’s why I’m completely dazed. I appreciate the help though, we’ve gained some insight as to how to build our images moving forward because of this.

@tom-elliott It does, this was incredibly helpful thank you.

@salted_cashews said in Is a direct upgrade possible in this scenario while retaining all previous configurations and images?:

To be honest, I’m not 100% sure how our guy knew that was causing a problem.

People with even some Linux experience normally check free space as a first-step in troubleshooting. Glad you got it figured out.