@Sebastian-Roth For FOG, it’s Ubuntu 16.04.

It’s possible my memory is wrong, but I remember starting the deployment within a minute after the capture completed. I had waited for the task to complete and disappear from the web GUI’s “Active Tasks”. I could be thinking of the issue with the unclean Ubuntu file system I had made another topic about (still working on that situation btw) in which correlation might not be causation, that could’ve just been something I had noticed different and thought “well the size was 0 so maybe that’s why it broke, it didn’t finish compressing.” when in reality it could’ve just been the file system.

@Sebastian-Roth When you say on the fly compression do you mean it compresses on the server as it is being captured rather than after? This reminds me - after a capture completes I notice image management still shows “size on server” at 0, and only reports a “real” value after a certain amount of time (of which seems to be based on the size and compression level of the image). Is FoG still compressing at this point? Why does this happen / what is going on in this process? I’ve tried to deploy during this process (before a real value is reported) and it breaks the image on the server as well as deploys a broken image.

Any guides for a linux newbie related to safely cleaning up old kernel packages / boot partition? I figure it’s something I don’t know how to do so it’s something to learn. Most of my linux cli experience comes in the form of directory changes and file transfers.

@Sebastian-Roth I do, we had about ~400gb of space leftover and the image before compression was about ~480gb.

Oh I see, are you referring to grub.conf or the “grub” file itself? Or is that the same file?

@Sebastian-Roth So at the time (the image posted above wasn’t during this event) the WebGUI reported 0% space free and the server when I ran a df -h reported the /images dir to be at 100%. The image captured fine and everything was ok, I was just curious how this was even possible. It must’ve just used another directory/swap?

Also thanks for the heads up on the /boot partition. So long as I don’t plan to upgrade this doesn’t hurt anything right? (this fog server is hosted in a lab environment)

@Wayne-Workman

The /images dir is a mounted dir on a separate RAID (within the same box) if that means anything.

More specifically, I’ve ran into situations where the FOG server has the total space available to store an image, but during the capture process it reports “0%” on the homepage yet the image still captures fine and the value returns to a non-0% number after completion.

My question is how does FOG do this if it’s out of space to store the temporary capture-in-progress? I understand fog doesn’t overwrite/add image data to the main directory /images until it’s completely captured. It uses a temporary directory first to write the image data from capture, then moves it once complete.

@Sebastian-Roth If you could keep it open that’d be great, I’m now going to do some more testing with this on Ubuntu 16 as well as 18. I’ll keep you posted.

EDIT: Also am I understanding correctly that FoG/Partclone cannot use the “Single Disk Resizable” option on LVM partitions? We’ve had issues with LVM in the past and FoG/partclone and we ended up having to use RAW format.

@Sebastian-Roth That direct “Desktop” link is the exact one I used. I installed it without LVM the first time, but we’ve moved over to CentOS since then. I formatted a USB 3.0 device using Rufus (latest) and specified MBR - everything else was left at defaults. Sorry if I couldn’t be more help, it’s been a while since then.

More specifically, I was reading up on the Single Disk - Resizable mode on https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images and it got me thinking. How exactly does FOG do this? Does FOG include the empty/unallocated (unformatted/raw) space in the capture, and how does it discern between the two? If I only partition out half of a 500gb drive and capture, it would make it smaller than a 500gb drive fully partitioned out with the same OS/data on the drive even if only 100gb on both images were being “used”?

@Sebastian-Roth It does, and it’s a hardware machine. What makes this weirder is we’ve had this issue in the past, forcing us to use Raw image type to capture. The weirder part is it’s a straight out-of-the-box Ubuntu 18.04.1 install, only adding xrdp, net-tools, and ssh.

Is it possible this is the result of mounting everything on one partition? The full capacity of the drive is also not being used, we’re only using 200gb of 500gb.

@Sebastian-Roth
On deploy (after successfully capturing thanks to fsck.ext4 fix):

On capture (after running the fsck.ext4 on the original machine image was built on):

@Sebastian-Roth Much appreciated!

@Tom-Elliott I’ve moved the compression to the default of 6 and I received the same error. I’m also receiving an error directing me to /var/log/partclone.log but that doesn’t seem to exist. I appreciate the compression level info, I wasn’t aware.

@Sebastian-Roth So after running that command it captures fine, but during deployment I get a similar error. If I try and capture again on a fresh base image, (different machine same OS/config) I get the same error.

Is this due to me having only 1 partition mounted via “/”? Is it something to do with Ext4? Image settings are:

@Sebastian-Roth Whoa, this worked! Thanks, now correct me if I’m wrong but Fog is the one detecting, warning, cleaning, etc in this case right? I’m not doing anything with my Ubuntu install’s grub / os ?

As an aside, does making everything ext4 and mounting everything on the same mount point (/) best practice?

File system specified during install was ext4. What does this mean exactly?

@george1421 There we are, thanks! On that note, I know absolutely nothing about MySQL. Is there a reference you can provide or any basic tips one should know when using it? I’m mainly looking for best practices/how-not-to-break things.

@george1421 We’ve been doing a lot of testing/deploying with our new network. I seemed to have not ran the previous commands properly. Is (ilHostID) what I type or should that be a specific value? I’m typing exactly what is typed there (excluding the // statements)?

@george1421 Is there a file stored somewhere that I would be able to delete in the future? I might have to do this more frequently than I thought.

@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?