Topics created by Fog_Newb

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

@fog_newb said in Strange formatting when selecting host. Dev Branch1.5.9.207 Ubuntu 22.04.1 LTS:

I saw Partclone 3.20

Yes that is the version that contains the updated code for apfs support. So it should clone apple based computers beyond getting access for the T2 chip.

@sebastian-roth I just noticed .177 was out and updated. No errors at all during the update process.

@sebastian-roth I figured it was something like that. The good news is FOG is working for me under 22.04.1

@sebastian-roth That is on the list of things to do next.

@george1421 Awesome - this worked. It booted from the stick fine and I was able to perform a quick registration. I started to capture the drive and it worked up until it came to the APFS portion. I ran into the apfsclone.c: bitmap error, like with the hackintosh.