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

Any ideas how to resolve this? Nothing was changed on the FOG server since updating to the previous build.

• Setting up and starting NFS Server…Failed to get unit file state for nfs.service: No such file or directory
  Failed!

!!!
!! The installer was not able to run all the way to the end as !!
!! something has caused it to fail. The following few lines are !!
!! from the error log file which might help us figure out what’s !!
!! wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log !!
!! in /opt/fogproject/bin/error_logs/fog_error_1.5.10.1580.log !!
!!!

Aug 13 16:35:48 fogger rpc.nfsd[35204]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 98 (Address already in use)
Aug 13 16:35:48 fogger rpc.nfsd[35204]: rpc.nfsd: unable to set any sockets for nfsd
Failed to enable unit: Unit file nfs.service does not exist.
Failed to start nfs.service: Unit nfs.service not found.
Unit nfs.service could not be found.
srossi@fogger:/opt/fogproject/bin$

I ended up restoring a VM image from a few days ago. I am back up on 1.5.10.1578 but not sure how to continue getting newer builds.

@Tom-Elliott Thanks, it seems to be sorted

Last night I did re-clone fresh. After deleting the /opt/fogproject directory then

I did

sudo git clone https://github.com/FOGProject/fogproject.git /opt/fogproject

sudo git checkout dev-branch

Then ./.install - This installed the latest stable release

Just a few minutes ago, I did a git pull and some files were updated and when I ran the install this time, I got the latest dev-branch version: 1.5.10.1566

@george1421 @Tom-Elliott Something is going on with the repository/branches

@JGeear I was getting stuff like this.

https://i.imgur.com/zdqF4q8.png

@JGeear Yeah something is messed up with the branches or something. I got that too. Tons of conflicts and a message about not a trusted repository or something. I figured it was on me because I had just restored a snapshot of the FOG VM.

I wiped the fog installer directory, in my case /opt/fogproject then I re-downloaded,

sudo git clone https://github.com/FOGProject/fogproject.git /opt/fogproject 

set to dev-branch but it ended up installing the latest stable version: 1.5.10.1565

sudo git checkout dev-branch

Tells me - Already on ‘dev-branch’

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

I’ve been able to capture and deploy images just fine. Until… mounting a 2nd hard drive as /images and upgrading to FOG 1.5.10.48 from the previous dev version. .mntcheck exits under /images/dev

I thought I had the permission set correctly since I can still capture… anyways, I’m not sure what to do.

The error message is attached

What do?

Thanks

update: SOLVED

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

Preamble

A while back @george1421 helped me create a bootable USB stick to allow IPXE bootinig my 2018 mini to FOG (I have all the T2 security features disabled in the mac BIOS no secure boot etc)

It was able to capture images no problem. I ran into problems deploying the captured images (to the same mac they were captured from). I guess it had something to do with the T2 chip. The image would deploy fine but would not boot the OS.

It started to get complicated for me and I decided to suck it up and just use Time Machine. I do not like Time Machine.

IIRC, since then T2 support has been baked into the Linux kernel and…

I just noticed this! Are there any plans to update it?

https://github.com/FOGProject/mac-boot/releases/tag/v0.1.0

Thanks

Hello,

Not sure if this is the right place to ask but is there a way to change the resolution of the ipxe boot menu the clients come to when booting IPXE?

Thank you

@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

That is awesome. I tried using a power-shell command to get the drive serial number.

 Get-PhysicalDisk | FT FriendlyName,AdapterSerialNumber,serialnumber 

Just to confirm, what this command lists as the Adapter Serial Number matches what Crystal Disk Info shows as the NVMe serial numbers as well as the serial number listed on the box the NVMe came in. Just to note, the SSD’s do not have an Adapter serial number

Thanks again for all you help.

@Sebastian-Roth Thank you so much.

Have there been any updates in dealing with dual NVMe drives that are the same size?

@Sebastian-Roth This is going to sound really dumb but I don’t know how to query FOS to figure out how the USB drive will be listed. Like to find out what /dev/???