@Bristow-0 You can clone the repo, and run the installer from the branch you want to work from. When you install FOG (either downloading the files or running it through git), it will create a settings file that will be read during subsequent install attempts to fill out the default answers.

@danieln Why would the QC be done after imaging instead of before? Just curious.

Do you have any other system for running remote commands? If you can maintain a list of system names (maybe using the FogAPI), you could run remote commands to your systems from one console on demand - would that work?

@limbooface Is this still an issue? If not, I’ll close this issue.

@limbooface So on a fresh Rocky 8.9 (the latest version in the 8.x stream) available, the install goes without a hitch.

Tracking on Github: https://github.com/FOGProject/fogproject/issues/577

Having the same issue on a Dell Latitude 3140. There is no option for RAID, only AHCI and Off. Secure boot is disabled, UEFI security mode set to disabled on PXE/Internal HDD. Updated to the latest FOG dev version, Kernel version 6.1.22.

Clonezilla will recognize the drive, but not the FOG kernel.

@Sebastian-Roth I’ll take a look - haven’t touched Red hat stuff for many many years though! Lol

@Sebastian-Roth I didn’t know about the 100% option - I like that!

@RogerBrownTDL Try this instead:

lvextend -L +398g ubuntu-vg/ubuntu-lv --resizefs

@RogerBrownTDL Yes.

lvextend - Increase the volume size
-L - Specify the size to increase it by
ubuntu-lv - The name of your logical volume (as reported)
--resizefs - Resize the EXT{2|3|4} file system

@RogerBrownTDL

lvextend -L +398g ubuntu-lv --resizefs

You may need to reboot for it to take effect. This will use all the remaining LVM volume space for your logical volume. You can’t go smaller after the fact, so be sure you want to use it all first.

@Scootframer Hmmm… I’m not sure off the top of my head. I know I’ve seen this issue before, but I do not recall what the fix was.

@Scootframer ls -la /images?

@Scootframer To verify what it is first, run ps aux | grep 2643. Then run kill -9 2643 to forcefully kill it.

@Scootframer Oh good!

Anyways, I would try the latest dev-branch and see if the issue persists. If not, then we would start looking at the logs on the server.

@Scootframer On your server, navigate to the folder you downloaded fog to, and run git checkout dev-branch. Then, re-run the ./bin/installfog.sh script to install the latest version.

If you only have 3.9 GB of free space, I’m going to guess that it’s running out of space before it can set the permissions (but someone else would have to verify that for me). The partitions are supposed to be saved into that dev folder until captured, then it gets moved over and renamed.

@Scootframer Can you confirm you’re using the latest FOG version in the dev-branch branch?

How full is your /images partition/drive? Is it a local drive on your server or an NFS mount? Does /images/a4bb6d84ebf4 exist on your server?

@kalafina I use Samba on a file server. Since you’re running Windows clients, it should work with minimal setup. You need to ensure that wherever the file is stored that the computer account can access it, not necessarily just the user.

But you are right - FOG is defaulting to adding the uploaded snapin file to the end of the command line. There is a walkthrough for adding a Wi-Fi key as a snapin that includes how to upload a ZIP file and run a command from inside - I’d recommend trying that if the above isn’t working.

https://www.youtube.com/watch?v=M-HXtqeukks

@Tom-Elliott You are crazy, but not for that reason… I keep forgetting to check the non-master code -.- That’s a me issue, lol

@danieln Looks like it’s failing at the password part:

$password = htmlspecialchars_decode($password, ENT_QUOTES | ENT_HTML401);

https://github.com/FOGProject/fogproject/blob/master/packages/web/lib/fog/fogftp.class.php#L464

Not sure who is maintaining the PHP code, but it’s failing at that line and breaking out.