Not yet, I am currently in the process of imaging the devices via time machine and confirming functionality on the iMacs in the new environment before doing additional testing or changes.
I am still using the FOG-Client to manage hostnames and computer names as that is a useful feature in itself.
Short term I am going to be using a time machine network backup & deploy, as I have minimal time to fix this and need this working.
I will circle back around sometime after I get the machines working at least.
@Sebastian-Roth said in Apple Fusion Drive:
/dev/nvme0n1
I will do that momentarily, mind you it is already capturing and writing to /dev/nvme0n1 and booting off of /dev/nvme0n1 when it starts the boot process.
Is there a way to rig it so it does, a hotfix or a one-off fix?
There is a new hurdle, but this is a seperate FOG-Server in a different environment that will only be interfacing with the exact same iMacs with the exact same hardware, quick fixes/rigging it up are wanted. I am in a bind due to not realizing the hard drive type.
I have an iMac (36 of them) that have a fusion drive.
27GB SSD and a 1TB SATA drive.
When I just do a typical imaging process via FOG it does not work.
When I boot up after cloning I get the following boot screen:
Help please!!
Organization Name: High Point University
Location (Optional) High Point, NC
Approximate Number of systems: 50
How long: 1 month
Wiki entry:
I am able to properly capture and deploy images to Mac OSX Mojave and on Ubuntu Linux 18.04 LTS both using nvme drives, and supported with hostname changing via the Fog-Client.
I migrated us to FOG, suggested by a faculty member, after realizing manually doing this with CloneZilla was not ideal.
We at High Point University in North Carolina have migrated from CloneZilla to this open-source software and image management.
You have saved us a lot of future time by creating this software.
From the Webb School of Engineer, as the solo systems admin here, thank you.
Not a complaint just a general thank you of the devs and to put in the Wiki testimonials.
@Tom-Elliott @george1421 @Sebastian-Roth for helping me the past 3 weeks.
I am able to properly capture and deploy images to Mac OSX Mojave and on Ubuntu Linux 18.04 LTS both using nvme drives, and supported with hostname changing via the Fog-Client.
We at High Point University in North Carolina have migrated from CloneZilla to this open-source software and image management.
You have saved us a lot of future time by creating this software.
From the Webb School of Engineer, as the solo systems admin here, thank you.
@Tom-Elliott said in Failure in Capturing an image:
wget -O /var/www/fog/service/ipxe/init_32.xz https://fogproject.org/inits/init_32.xz
It now works completely.
Thank you very much.
@Tom-Elliott
Trying this now, will attempt to see if it deploys properly.
But it still needs to be able to write the partitions and data in the correct order.
If that wasn’t the case then why did we make a post init to properly identify the nvme0n1p1 when we did the:
lsblk -dpno KNAME -I 3,8,9,179,202,253,259 | uniq | sort -
readlink /sys/class/block/nvme0n1p1
disk=$(readlink /sys/class/block/nvme0n1p1)
disk=${disk%/}
disk=/dev/${disk##/
echo $disk
lsblk -no pkname /dev/nvme0n1p1
When my capture/hardware hasn’t change.
Look back at the conversation in PM from 11 days ago and see if that maybe adds more context? I am a little confused myself x.x
That is what I told @Tom-Elliott in the priv-chat.
This is similar to what happened before and he fixed in a post-init but it’s not working again.
I am out of the office but will do that tomorrow.
Additionally this WAS working before I updated utilizing his post-init, as I can deploy the image fine that I capture before and I use to be capture fine, now it’s broken.
@Tom-Elliott
https://github.com/Thomas-Tsai/partclone/blob/master/src/partclone.c
-aX --checksum-mode=X Checksum formula to use to add error detection\n"
" where X:\n"
" 0: No checksum (no slowdown, smallest image)\n"
" 1: CRC32 (Fast to compute, basic detection)\n"
Yes, it’s a Mac.
The Mac will deploy an image fine (dd, raw, everything).
But capturing an image (dd, raw, everything) does not work.
@Tom-Elliott That is a capture task from the webUI, not a deployment.
Just did it via the ‘task selection’ from the host page, and same interaction happened.
Mac’s can deploy but cannot capture.
It instantly finishes writing the content but is not make any actual image, the size is saying 0.00KB on the file server:
Here is the boot process in order.
Removed the postinit
Replaced the inits with artifacts.
Linux is working with capturing, still need to test deployment with Linux.
Still needing to test deployment & capture with Mac after the above changes.
-Edit 1-
Linux deployment works.
Mac deployment works, still needing to test capture. Want to write the master image before rewriting the golden image on Mac.
In https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.upload
done
echo "Done"
debugPause
dots "Getting Windows/Linux Partition Count"
countPartTypes "$hd" "ntfs" "ntfscnt"
countPartTypes "$hd" "extfs" "extfscnt"
countPartTypes "$hd" "*" "partscnt"
if [[ $ntfscnt -eq 0 && $extfscnt -eq 0 ]]; then
echo "Failed"
debugPause
handleError "No resizable partitions found ($0)\n Args Passed: $*"
fi
echo "Done"
Is where it is failing in the code, not sure what is causing this issue?