@Fog_Newb Yep, it’s as I suspected:

The Line:

Subsystem sftp /usr/lib/openssh/sftp-server

should be changed to:

Subsystem sftp internal-sftp

Then restart ssh services: systemctl restart sshd

Then your Storage Node testing should succeed!

@Fog_Newb Yep, it’s as I suspected:

The Line:

Subsystem sftp /usr/lib/openssh/sftp-server

should be changed to:

Subsystem sftp internal-sftp

Then restart ssh services: systemctl restart sshd

Then your Storage Node testing should succeed!

@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.

I ran chkdsk prior to capturing and it came up clean

alt text

UPDATE: So I tried everything for the ntfsresize error … turns out, I had to shrink the partition in windows a bit then expand it. After that, I could capture.

@Tom-Elliott sounds good!

@Fog_Newb probaly just typoed it and i went with it too lol.

@Small0145 No, it’s not.

@Tom-Elliott All good with 1.5.10.1629

Thanks

@JJ-Fullmer @Tom-Elliott

I’ve found a work around. I now have /images on USB HDD passed through the to VM. When I run a standard back up of the VM via the VM software (Virtualization Station), it only back-ups the OS VM drive.

For the /images drive - I use a sync program to back-up the files, not the disk .

@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

@Fog_Newb

Hi,
I had the same problem as you, and I solved it this way:
I updated FOG to the latest version (1.5.10.1655), and configured the time zone I wanted in the graphical interface, in “Fog Configuration > Fog Settings > General Settings > TZ INFO”.
On the VM where I have the FOG server installed, which is an Ubuntu Server 24.04, I only edited the file “/etc/php/8.3/fpm/php.ini” adding the information: date.timezone = “America/Fortaleza” (this is my local time zone). I added this information just below the explanation about timezone that the file itself brings, as you did and showed here in the images.
I restarted the VM and the time was finally correct in the FOG records.

I also followed this topic by @Sebastian-Roth, it helped a lot!
https://forums.fogproject.org/topic/15434/time-lag-between-the-fog-web-interface-and-the-system-time/2

@AUTH-IT-Center Should be addressed in the latest.

@Tom-Elliott

Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.

Yeah, that fdrive number… 🙂 It is the serial number of the drive.

The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.

@george1421

Thanks George. No but I will now that I have time machine back ups. Can I use mac-boot to create the stick then just update those 2 things?

@Sebastian-Roth Unfortunately the USB external drive wasn’t see by FOG, I tried the serial number listed in Windows but it backed up an NVMe drive Please disregard

@Sebastian-Roth Yes. Thanks

@george1421 Cool. Is the T2 Kernel known to address this specific issue?