@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.
@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.
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.
@sebastian-roth Ok thanks, I will try it out and report back. These inits, they just go on the FOG server right? Or do I also need to add something to the mac OS Grub/FOS boot stick?
No. I do not have any USB / Ethernet or Wifi devices. Just the built in Ethernet and WiFi. I am going to remove this registration and re-register when testing out the updated partclone inits. I’ll be sure to post what happens AFA MAC address
Not sure what happened or if this is something to do with the latest mac OS (Monterey 12.5.1) security
I created a FOS USB stick and registered my mac Mini. The MAC shown in the FOG web UI after registration is different than the MAC address of the Ethernet port.
Actual mac address
MAC address seen by FOG when registering
Also, any word on when the latest partclone will be integrated into FOG so we can capture APFS images?
@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.
@george1421 said in Can't get to FOG booting from USB Boot UEFI client:
FOS linux
Is there a tutorial for creating a FOS Linux usb client to work with the pre existing FOG server?
@brakcounty
Not sure. I don’t think it gets that far but it is hard to tell. It boots from bootx64.efi (the renamed ipxe.efi) on the USB something, maybe the banner appears or whatever text when ipxe.efi loads, then the screen goes black really quick - as it reboots. I can try to take a video of what happens.
I thought about making a USB stick with an EFI partition and putting the bootx64.efi on there but not sure if it would make any difference.
Hi,
I followed the instructions here and created a USB Boot UEFI client.
https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way/12
I disabled secure boot and enabled booting from anything. And I can boot from the USB drive, it starts to ipxe boot but then my display goes out, then a mac OS error screen really quick then it boots from the mac OS SSD.
I have a 2018 Mac Mini, I manually added the host to FOG, blah blah and added the t2kernel and specified in the settings for it to use that kernel but I don’t think it is getting that far. I am using the built in Ethernet on the mini.
Is there an updated guide for pxe booting t2 intel based macs?
Hello,
Any luck with incorporating the 0.3.20 into FOG? Also, is there something I can check or turn on the debug/partclone logs? Nothing ever shows up in /var/logs
Thanks