@Tom-Elliott said in FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS:

@Fog_Newb

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?

Yes. vdb is /images, so moving a file from /images/dev (vdc) to /images (vdb) should cause the disk to increase on vdb? The sice on vdc wouldn’t decrease but the amount of usable space off vdc should be increased by the amount of the file that was moved to now vdb?

That’s what I’m understanding here. I don’t know if this means there is an issue or if this is working as intended, but it seems like it is?

That is what I was thinking - I was trying to establish that the mount points are set up correctly and that it’s not an issue with fstab.

It only takes a few minutes or so to spin one of these VM’s. I spun up another VM, same parameters and mount points. The only things added other than the ssh server during the Ubuntu install were - the Ubuntu updates, dnsmasq, pip, tzlocal, tz… and of course the latest FOG dev version 1.5.10.1614. All cloud services, disabled

I exported it to OVF right before registering a host and capturing an image… which exhibited the same problems.

If you or anyone else wants to check it out

https://drive.google.com/file/d/1GPJH0ZuJFZaTqmGvIe1EM2HBCVlde4FI/view?usp=sharing

username: test
password: 123456

All 3 VM drive images are included with the OVF. A 2.8 GB zip since the drives have barely anything on them.

Fog web interface - user and password are defaults

It takes a ridiculously long time to import the OVF into VMWare Workstation. But it will import

If you want it quick and dirty create a new UEFI based Linux VM and chose to use the existing vmdk drives contained in the zip.

A copy of the conf file used by dnsmasq is in the home directory

@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

@AUTH-IT-Center said in FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS:

@Fog_Newb

try the below

/dev/disk/by-uuid/d61ab2ae-b79a-4b07-bfc5-4678ab0902f4 /images ext4 defaults 0 1
/dev/disk/by-uuid/3d7874cb-8c59-4e6d-8735-fb8361994590 /imagesdev ext4 defaults 0 1
/imagesdev  /images/dev   none    defaults,bind   0   0

Sources:

• https://man.archlinux.org/man/systemd.mount.5
• https://wiki.archlinux.org/title/Fstab#Bind_mount

Same results only - the changes you suggested making to fstab created /imagesdev along with /images/dev on vcd. Both are bound together.

Create a file in /imagesdev it is seen in /images/dev and vis-a vers-a.

@Tom-Elliott

If you’re looking at the Storage Configuration screen cap, those numbers are something else and are slightly different. The end numbers - 01, 02, 03

The UUID’s for vda1, vda2, vdb, and vdc are different

@AUTH-IT-Center

Unfortunately, making those change to fstab, saving then rebooting resulted in errors during boot when it attempted to mount vdc (/images/dev) and ultimately led to “emergency mode”.

No worries though, in emergency mode I was able to edit fstab

I know when the box is booted, mount points are correct vdb is mounted as /images, and vdc is mounted as /images/dev

To test this I moved a 20 something GB directory from /images/dev to /images. The size of the VM disk image for vdb grew 20 something GB. The directory I coped from, /images/dev had to have been on vdc since the OS drive (vda) doesn’t have that much space. And it couldn’t have been on vdb since it would have moved instantly and the VM disk image for vdb wouldn’t have increased in size.

edit - just for the heck of it, I removed /images and /images/dev from fstab and once booted, I manually mounted /images (vdb) once I confirmed that was mounted and working I manually mounted /images/dev (vdc) - still the same problem with FOG

@Tom-Elliott said in FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS:

1. Change the ownership back to chown -R fogproject:fogproject /images; chmod 775 -R /images

This should allow your system to work without issues.

I ran each command separately, this time on the new FOG server. The one where FOG created the permissions and files during the install. However I’m still experiencing the same issue

Your FSTAB needs to have the mount set correctly too so that dev gets mounted appropriately on subsequent boots which I presume is already happening?

Yes, in both cases - on the original FOG server and new test FOG server fstab was correct, the mount points mounted fine at boot and I was able to manually write directories and files to each mount (/images /images/dev). I’ve pasted the contents of the fstab in an earlier comment

So strange. As long as both /images and /images/dev are on the same mount/drive everything goes off without a hitch

@AUTH-IT-Center

Thanks -The fstab paste is below. The parameters are correct as far as I can tell and they were added by Ubuntu during the install. And it appears both /images and /images/dev are mounting correctly and accessible since FOG was able to capture to /images/dev and create a file in /images. I was also able to manually create files and directories in each mount location without any problem. If you see something out of place feel free to let me know.

On my other FOG server, where there is only the 2nd drive, and it’s is a mount point for /images, it uses the same fstab parameters (albiet different UUID) and it has been working fine.

@Tom-Elliott

Yes, I even spun up a new FOG VM where the mount points were created before FOG was installed to makesure the FOG installer created all the files and set permissions.

edited - words

@Tom-Elliott

Quick TLDR. incase my word salad OP doesn’t make sense.

If /images/dev is on a different mount point than /images, captured images will remain in their temporary location in /images/dev and a directory for the newly captured images with not be created in /images

Thanks Tom,

Everything you mentioned is what I did on my existing FOG server. And the same problem occurs on a freshly spun VM I set up just to make sure I didn’t miss any files or permissions from the original /images/dev location

The images in the OP are from the new VM. All mount points were specified at the beginning of the Ubuntu install - fstab created by the Ubuntu installer (see code below). The files and permissions on the /images/dev mount were created by FOG.

I still have it up if any logs could be of help.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/vda2 during curtin installation
/dev/disk/by-uuid/078f54eb-340b-41fc-ab34-1494cd59e4e4 / ext4 defaults 0 1
# /boot/efi was on /dev/vda1 during curtin installation
/dev/disk/by-uuid/DD22-44A9 /boot/efi vfat defaults 0 1
# /images was on /dev/vdb1 during curtin installation
/dev/disk/by-uuid/d61ab2ae-b79a-4b07-bfc5-4678ab0902f4 /images ext4 defaults 0 1
# /images/dev was on /dev/vdc1 during curtin installation
/dev/disk/by-uuid/3d7874cb-8c59-4e6d-8735-fb8361994590 /images/dev ext4 defaults 0 1
/swap.img       none    swap    sw      0       0

This is long. My FOG server has /images as a mount point for a 2nd drive. Everything was working fine. The /images mount was set up prior to installing FOG.

With FOG storing temp images in /images/dev, it was really inflating the disk space on my VM drive. As some of you know, with VM drives, the size of the drive increases as data is added to it.

So I decided to make /images/dev a mount point on a 3rd drive. I made sure to copy all the exiting files and permissions from the original /images/dev.

After re-capturing an image, I noticed something peculiar, The temp image remained in /images/dev and the directory where that image was initially stored (/images/NAMEOFIMAGE), was no longer seen as directory. But it wasn’t a symbolic link either. This only happened after trying to capture the images using the new mount.

Just to make sure it wasn’t something I messed up copying and setting permissions on the newly created /images/dev mount, I spun up a new VM specifying the mount points during install. Then installed FOG

But… the same thing happened.

It’s looking like FOG has issues if the temp storage location is on a different volume than the images.

I know this isn’t a big deal in the grand scheme of things and most users will never run into this but would be cool if there was an easy fix/change that could be implemented in the next release.

Quick TLDR. incase my word salad OP doesn’t make sense.

If /images/dev is on a different mount point than /images, captured images will remain in their temporary location (/images/dev) and a directory for these newly captured images will not be created in /images

Thank you

@AUTH-IT-Center

Yes, the reddit post is the way the drives were mounted. Just to make sure it wasn’t user error, I spun up another FOG VM really quick and during the installation specified the mount points

Same thing

It’s looking like FOG has issues if the temp storage location is on a different volume than the images.

@AUTH-IT-Center Something weird happened after mounting another drive as /images/dev I made sure to copy everything from the original /images/dev and copy them to the new mounted /images/dev

Then

sudo chown -R fogproject /images

sudo chown -R fogproject /images/dev

After doing this and capturing an image. The tmp image remained in /images/dev and the usual directory where that image was stored, was no longer seen as directory. But it wasn’t a symbolic link either. This only happened after trying to capture the images using the new mount.

Just to make sure it wasn’t something I did when mounting the new /images/dev storage drive, I made sure the directories for the remaining pre-existing captured images were still being seen as directories. They were. I then captured one of those those images and just like that, the directory for that image was no longer seen as a directory and the tmp image for that capture remained in the /images/dev. Weird.

@AUTH-IT-Center

Thanks. I currently have a 2nd drive mounted as /images. That’s is the one that keeps blowing up. I thought about mounting a separate drive as /images/dev (that’s were FOG seems to create the temp files). I may do that and see how it goes.

Hi,
It would be cool to have an option that shows image capture and deployment using local time of the FOG server (not UTC). Another would be an option to specify a alternate temp directory for FOG to when capturing images. This would help keep VM drives from blowing up in size.

Thank you

@Tom-Elliott

Ok thanks

@Tom-Elliott

I’m not. But 8.3 is the only subdirectory in /etc/php

@Tom-Elliott

Thanks. I edited the php.ini under /etc/php/8.3/cli/php.ini and apache2/php.ini. I added

date.timezone = 'America/New_York'

Under the [date] section, saving then restarting and it is still the same.

Like this

Random time stuff related to box

@Tom-Elliott

The one located in /etc/php/8.3/apache2 ?

If so under the [date] I’ve tried adding

date.timezone = "America/New_York"

date.timezone = America/New_York

and just now tried

date.timezone = 'America/New_York'

Saving and restarting each time but it’s still showing captures in UTC time.

Here is a screencap

Thank you

Hello,

I have local time set correctly on the Ubuntu box and TZ INFO in the FOG settings is set to the correct tz. Is there another time settings I need to change?

Thank you

@Tom-Elliott Thanks. Updating to 1.5.10.1581 worked fine.