Posts made by Fog_Newb

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

@sebastian-roth Thanks I tried another browser without any plugin and I cleared cache. Same issue. The error log shows.

https://pastebin.com/VZQrPF7v

@george1421 What does the T2 kernel do differently than the stock kernel?

@george1421 I boot from a FOS usb stick that pxe boots to the FOG server. So I am thinking put the T2 Kernel on the server and specify that kernel under the “host kernel” setting for the macs, then on the the FOS stick put the t2 kernel as well?

@sebastian-roth The mac, the image is deployed then it boots to the mac OS login screen, it displays the only account on mac OS when the image was captured. But it doesn’t accept the password. It tells me if I can not log in - reboot into Recovery. Recovery doesn’t allow me to make any changes because there isn’t an Administrator account associated with the installed OS (Not to be confused with activation lock) The image was captured from the same mac it was deployed to.

I would be happy to provide pics but to do that I would have to duplicate the problem which means the mac will be down.

Apparently this is a thing with T2 macs when imaging. The admin account gets stripped of its admin rights amongst other things. A quick search brought me here

Unfortunately deleting ‘.AppleSetupDone‘ and rebooting did not restart the set up. It just brought me back to the login screen which displayed my admin account (at least it was an admin account when I captured the image) but wouldn’t accept the password.

@george1421 Oh that is right. I forgot about putting the T2 kernel on the new FOG server. Shoot. Where do I get the T2 Kernel again and does it go on the FOS stick or the FOG server?

Sometimes deploying an image works, like if it is the same mac and it is the same install the image was captured from but if I wipe the drive and deploy the image I get the dreaded No Administrator account found. What is the trick? Definitely not a FOG issue but thought someone here might now.

I don’t like these newer macs at ALL. The T2 chip is foolish.

Hello,

I’m not sure when this started. Some time after going from .204 to .207?

When I click on a specific host to set parameters the page displayed is strange.

It only happens with this one host. I’m thinking I should delete the host and re-register it?

It looks like this

https://imgur.com/a/0eEF0xD

Something that may be relevant. Next to this host, there is a gear icon, when I hover over it, a small window comes up that say FOS. It is a mac that uses a FOS USB boot stick. This is definitely something new though, it was not like this before.

https://imgur.com/B2X1o1k.jpg

@kibade

My memory I really bad but IIRC I ended up having to upgrade to Ubuntu I was on 20.04 at the time

@george1421 Not much but… I did a little testing at home. 4 different machines, HP Laptop hackintoshed (all drives, non resizable, Other OS) (one SSD NTFS the other APFS), 2 gaming PCs (win 10 single drive all partitions resizable), A 2018 mac mini all boot security turned off.

And… and !!! I finally migrated, well actually, I made a new FOG server from scratch using only the ltsc.conf from the previous FOG server . I installed Ubuntu Server 22.04.1 fresh in Virtual Station on a NAS, (QNAP TS-451+), latest dev branch with the new inits built in, and was able to capture and deploy from/to 4 home computers no problem. I wish I still had older images and more things to test with.

I love this NAS especially since it was given to me. I dropped in 16GB of RAM (from 2) and got cray stupid -configuring all the drives in a RAID 0 stripe, hey I live on the edge , I can’t believe this thing is running a couple VMs no problem on that Celeron CPU.

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