@Tom-Elliott
I think this thread has gotten a bit off track, partly due to my explanation about trying to modify an existing FOG server.
So, if I could - Let’s forget about the old FOG server - a re-cap - the new ‘test’ FOG server.
Fresh Ubuntu 24.04.1 install with 3 drives. During the install process, I created mount points for /images (vdb), and /images/dev (vdc)
each drive has a unique UUID

mount points correct

fstab created by the Ubuntu installer

I installed FOG 1.5.10.1612 without any issues—no errors at all. During the installation, the FOG installer successfully wrote files and set permissions on both mount points (/images/dev (vdc) and /images (vdb)). And all the files that should be in each directory/mount are present when compared to a functioning FOG server.
When capturing an image, it gets stuck in the temporary location /images/dev/[randomnumbers] and never moves to the /images directory.
executing both
sudo chown -R fogproject:fogproject /images
and
sudo chmod 775 -R /images
then re-testing/capturing - no change
Manually moving a directory (which couldn’t possibly fit on vda) from /images/dev (vdc) to /images (vdb) caused the virtual disk size on vdb to increase. IMHO, it seems clear the directory was initially stored on vdc. Am I wrong in assuming this confirms that the mounts are correctly configured and functioning?
Anyway, it’s not a big deal. I just wanted to make sure I’ve at least clarified everything
Thanks