![]() ![]() This seems to be a common issue with the new APFS file format. Apple support recommended formatting in the older format, not APFS. The Disk Utility process failed at the last stage due to a reported ‘failure to ‘invert’ the new drive or partition’, due to an invalid argument. While upgrading to a bigger SSD (960GB from Transcend- TA960GJDM500) in my MacBook Air mid-2011 (11”) (running macOS 10.13.6) the standard installation instructions from Transcend did not work. It has worked for me so far, albeit some of the packages I've tried to install during that build have failed, the OS works. ![]() I believe there is a thread out there (either here on JAMF or google) about pulling out the firmware update tool from the installer and making it a pre-run pkg first.Īs for building the OS base image, my vote is for AutoDMG. For reimages of workstations that Have already had 10.13 installed, this seems to go ok. But that could vary based on any other attached bootable volume connected. Generally for me it's usually disk3Īs the first attached external drive. Since that's the "synthesized" APFS share that would get imaging. MacBookPro:~ User$ diskutil listĢ: Apple_APFS Container disk1 2.0 TB disk0s2Īnd then your image would be applied with asr restore -s /Users/Ed/Desktop/10.13.0 Base Image.dmg -t /dev/disk1 -erase what I believe you ned to be running is identified by diskutil. Getting in on this thread since I'm in the same boat. I need automation and consistency to manage a modern enterprise Mac population. I don't care how I get that base image, but having technicians manually install the OS each time is ridiculous. So even if I just use an empty base image to start with, I need a "monolithic image" process to do that. Laying down a base image in a minute through an automated process is significantly better than having technicians perform a full OS install manually (which we then have to patch if they aren't keeping it current). ![]() That said, we have to have a method of wiping a system and reinstalling the OS to factory settings, since we aren't going to throw away computers when a person leaves the company. I found that amusing since we had scaled up to 50% more than our current Mac count (our company has since split), so I know we don't "need" MDM. They told us that MDM was a requirement to scale out our macOS deployments when we complained about SKEL requiring it. ![]() I have a feeling I may be entering the incorrect target location when trying to do the restore but I may be completely wrong altogether.Īpple likes to claim that inconvenient processes are "dead" so they can make changes without consideration for them. When I enter the below commands, I get an error stating "APFS inverter failed to invert the volume -invalid argument."Īsr restore -source /Volumes/ExternalHDD/FinalImage.dmg -target /Volumes/Macintosh HD/ -erase Note: Both Mac disks are already formatted to AFPS and running High Sierra. However, the problem I'm having is restoring the image created, either on the same machine that I created the image or on another Mac. This successfully worked and I then copied the image to an external hard drive. Hdiutil convert -format UDZO -o /Volumes/Macintosh HD/FinalImage /Volumes/ExternalHDD/tempimage.dmgĪsr imagescan -source /Volumes/Macintosh HD/FinalImage.dmg* *hdiutil create -srcFolder /Volumes/Macintosh HD/ -size XX -format UDRW -layout GPTSPUD /Volumes/ExternalHDD/tempimage I then booted it to recovery mode and entered the following commands in Terminal to create the image. I upgraded a MacBook from Sierra to High Sierra OS. Previously, I was able to do this as per the link below (scroll all the way down to the Advanced section) Basically my goal is to achieve a monolithic system imaging in High Sierra. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |