@sebastian-roth Thanks. I just updated to the latest. So far it is capturing an APFS drive on a hackintosh no problem.

I’ve used the way outlined here

https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@george1421 I would argue 3.20 has been tested quite a bit considering Clonezilla. Something that would be cool is - during the FOG install it would ask if the user would like to create ISO/IMG in order to create bootable media for devices that can not PXE boot (Macs). It could also take the settings that were plugged in during the install, even add the T2 kernel etc etc.

I digress, I can’t code and can barely build unless there is a ‘recipe’ containing the commands to build, so I have no idea how complicated (read time consuming) this would be. Maybe it is time for me to learn.

I’m just happy you guys made the inits with 3.20 available.

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

@sebastian-roth dm sent with log file

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

@sebastian-roth I don’t have a directory by that name. I can’t seem to find any detailed logs for FOG other than what is in the fog directory.

Hello,

I get this error during the install however, FOG seems to be working. I was able to capture and deploy an image.

After going from Ubuntu 21.10 to 22.04.1 LTS (The Jellyfish one) I used the following commands to get rid of php 8.0 (Thanks @Sebastian-Roth )

a2dismod php8.0
a2enmod php8.1
apt purge php8.0*
systemctl restart apache2

There was a minor issue when purging 8.0

“dpkg: warning: while removing php8.0-opcache, directory ‘/etc/php/8.0/mods-available’ not empty so not removed”

Then I upgraded from FOG 1.5.9.163 to FOG 1.5.9.175. The install went well with only the error regarding mysql but it seems to be working.

https://pastebin.com/1JTPtWm0

Is this something I should be concerned about.

Thanks all.

I think it may be due to repositories being disabled?

Here is a link to the pastebin of the FOG install, this also happened with version .174

https://pastebin.com/mnKX7HTu

Disabled repositories?

[sudo] password for [redacted]:
Ign:1 http://us.archive.ubuntu.com/ubuntu impish InRelease
Ign:2 http://us.archive.ubuntu.com/ubuntu impish-updates InRelease
Ign:3 http://us.archive.ubuntu.com/ubuntu impish-backports InRelease
Err:4 http://us.archive.ubuntu.com/ubuntu impish Release
404 Not Found [IP: 91.189.91.39 80]
Err:5 http://us.archive.ubuntu.com/ubuntu impish-updates Release
404 Not Found [IP: 91.189.91.39 80]
Err:6 http://us.archive.ubuntu.com/ubuntu impish-backports Release
404 Not Found [IP: 91.189.91.39 80]
Ign:7 http://security.ubuntu.com/ubuntu impish-security InRelease
Err:8 http://security.ubuntu.com/ubuntu impish-security Release
404 Not Found [IP: 185.125.190.36 80]
Reading package lists… Done
E: The repository ‘http://us.archive.ubuntu.com/ubuntu impish Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://us.archive.ubuntu.com/ubuntu impish-updates Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://us.archive.ubuntu.com/ubuntu impish-backports Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘http://security.ubuntu.com/ubuntu impish-security Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

@sebastian-roth Sure will do that now.

Also going to restore snapshot then upgrade to 22.04, use those commands listed above, then install the latest FOG dev (175)

@wayne-workman I have been using the dev build. Currently 1.5.9.163 and previous dev builds have been working fine on 21.10 LTS. But running the FOG upgrade to 1.5.9.174 fails with PHP errors (very similar to OPs)

I upgraded to 22.04.1 LTS on a whim to see if 1.5.9.174 worked on that but the upgrade to 1.5.9.174 failed on 22.04.1 too. PHP database error.

@sebastian-roth Is the latest dev branch 1.5.9.174 supposed to work on ‘22.04.1 LTS’? On Ubuntu 21.10 using 1.5.9.163 I was unable to upgrade to 1.5.9.174. It failed on getting most PHP modules (I can do it again with screen caps) So I reverted using a snapshot prior to the FOG upgrade, then updated the OS to to 22.04.1 LTS, and tried upgrading FOG to 1.5.9.174. It failed on PHP database.

@sebastian-roth Does 1.5.9.163 have these new inits?

I read the dev-branch info but wasn’t sure. I never know what most of that stuff means.

https://imgur.com/V9EZOmH.jpg

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

@sebastian-roth Yes, both mac addresses are Apple ones. I am at a loss. I tried the FOS stick on my laptop and PC and they both reported the correct MAC address to the FOG server when (re)registering.

I am trying to figure out how to clear any potential spoofs on the MAC address in mac OS but can’t find anything. Also, I installed the OS fresh so … IDEK. I tried asking in some apple related forums but haven’t gotten any information. I know Apple implemented auto MAC randomization on their wifi but not on Ethernet. Ironically my Ethernet is seen as en0 and usually it is supposed to be en1.

@Sebastian-Roth When I tested the new inits I removed the mac mini host from FOG and re-registered it. The same thing with the MAC address. I wonder if mac OS masks the actual MAC of the NIC and FOS sees the real one.

@sebastian-roth Yes, Clonezilla but I need to get some more SSDs/HDDs.

@sebastian-roth @george1421 Good news!

So far so good. I was able to capture the APFS drive on the real mac using the USB stick and the updated init.xy. I put the updated init.xy on both the stick and the server.

I was also able to capture both drives APFS and NTFS on the hackintosh laptop. Now I have to figure out how to back up the data in case deploying the images goes sideways.

@george1421

Thanks, I wasn’t sure how this one was made. I downloaded the img and used rufus to write it onto a USB. It works great by the way.

@sebastian-roth Uhm… @george1421 can probably answer that better than I can.

Sorry for deleting and reposting the replies. The way the thread looks after replying, it looks like I replied to the OP and not to another reply.