@smoooo I replied to your pm with the script I use to expand OSX partitions.
Also, the prohibitory symbol (crossed out circle) could also mean an incompatible OS for the hardware, I do a little bit with snow leopard to make it work on unsupported hardware, and it usually involves a kernel swap at a minimum to get old OS’s booting on new hardware.
Not sure if youre still having issues with corestorage or not, but “diskutil cs list” will show you your corestorage groups, which would typically need to be deleted before cloning or modifying partitions (you would get the prohibitory symbol from this too).
Also, just as a random tidbit, you can install OSX on an HFS+ disk all the way up to 10.13 (never tested 10.14+, might still work) if you run the installer from the commandline and use the
switch for the installer. This might give you a LITTLE bit more flexibility as far as being able to read partitions/volumes from linux utilities (APFS support is much harder to come by).
@Smoblikat If you have 2017 (guess) or newer Apple started including the T2 chip, which is the security controller for the apple devices. All communications go through this T2 chip. You need a special FOS Linux kernel to get these systems to image correctly.
I would say lets create a new thread and we can discuss in detail there.
@george1421 It looks like the apple T2 chips encrypt the drives at rest, but only 2 or 3 of the 5 partitions for the apfs volume. not sure if anyone knew of a way to bypass this from happening. I am able to boot the mac after transferring but looks like it loses all user information and can not login.
@saftkartoffel@kudlab While I can’t test USB booting here in my VM setup quickly I would ask you guys to try out using the last menu point from your USB key GRUB menu 8. FOG iPXE Jumpstart EFI after you’ve scheduled a multicast task.
I don’t think this is a FOG problem. FOG is moving the files from the source computer to the target computer and the target computer boots OK. The problem you see is inside OSX itself. FOG doesn’t step inside the target OS. The only way it can do this is with the FOG Client and that is only to change the workstation name or deploy applications.
Understand the next thing I say is a guess because I don’t know. Its possible that Microsoft has connected user management or maybe password management to the T2 chip. Its possible with a different T2 chip it also protects/encrypts the password file. It may also be possible that changing the computer name does something unexpected with the user accounts. I don’t use Apple computers so I don’t have any experience with them.
From a debugging standpoint, we know that FOS Linux can access the hard drive of the Apple computer (because it can send a computer image). You may be able to use debug mode to access files on the target computer. I don’t know what you can do to reset the password externally but if you need to do things on a file level you can do this with FOS Linux. If you find a solution in debug mode then possibly you can write a FOG Post Install Script to apply those same settings during image deployment.
@rathan While you can. You shouldn’t. Apple has made imaging a dead workflow through a number of things, the most important being the T2 chip preventing netboot/external boot. MDM and DEP is the appropriate way to now provision MacOS devices. Erasing would be done via CMD+R in recovery or by pushing an erase and install from your MDM.
@rhulet Ok, nice! You will find the new kernel binary in fos/kernelsourcex64/arch/x86/boot/bzImage. Copy that to your FOG server in /var/www/html/fog/service/ipxe/ but I suggest you rename the original bzImage in that directory instead of overwriting it. Just so you have a surely working backup copy of the kernel.
Now, applying the patch I notice that I gave you instructions for building our current kernel version. But for this stuff you need to use a newer one. Sorry for that. Move that 4.19.64 code out of the way, you might want to use it some other time:
mv kernelsourcex64 kernelsourcex64_4.19.64
Now add the patch and build the newer kernel:
./build.sh -kn -a x64
patch -p1 < ../nvme-mac-5.1.16.diff
This will get you the same kernel version I built for you some days ago. But there also seems to be a patch for kernel 5.2. If you want to give that a try instead:
./build.sh -kn -a x64
patch -p1 < ../nvme-mac.diff