You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2017-08-30 14:52:55

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

DS 1.7.7 and APFS restore of 10.13 is possible :-) !

This thread is to post and share findings on restoring APFS and 10.13.

-https://support.apple.com/en-us/HT208020 states clearly that imaging is ONLY supported for re-installs of 10.13
-The required firmware updates are part of the upgrade process.

So : run a (net) install/upgrade from 10.12 to 10.13 to get the firmware.

What I have tested:

macoS 10.13beta8 , AutoDMG 1.8b537,DeployStudio 1.7.7

Here is what I did:
On Mac running 10.13b8 I created the AutoDMG image, (default settings) from the downloaded 'Install macOS High Sierra Beta' app.
The result is named : osx-10.13-17A358a.apfs.dmg

On the same mac I installed DeployStudio 1.7.7,  mounted the image just created, ran the DS assistant to create netboot set, used the mounted image as a source for the NetBoot set (I suspected recovery partition version mismatches)

Copied that .nbi to a 10.12.5 /server 5.3.1/DS 1.7.7 server, enabled the netboot set
Copied the osx-10.13-17A358a.apfs.dmg file to /Repository/Masters/APFS/ folder
Created a workflow with 3 steps: partition disk, restore image (with the APFS image created) and configure task (rename computer, create users, skip setup)

That worked fine on a MacBook Air 7,2 (that had installed 10.13 beta versions before), the result is a working 10.13b8 system, with the 2 configured users, and the usual AFPS layout (Macintosh HD, VM, Preboot and Recovery)

!! Yeah!!!! DeployStudio Rocks !!

The only catch so far is that I had to select 'first disk available' in the restore step.

I will share more experiences here, please do that too

Last edited by mjsanders (2017-08-30 14:53:47)

Offline

#2 2017-08-30 16:16:44

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

First fail: the same workflow does NOT work on an iMac 2014 with HDD. (the scripts check for SSD's) Good sanity check!

Offline

#3 2017-08-30 20:34:46

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

Which makes sense as HDD's won't be... at install time. (read beta notes to fill in the blank about HDD and APFS (NDA?))

Offline

#4 2017-08-31 14:10:07

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

I am wondering how to create a foolproof workflow for deploying the next macOS version with APFS.

- Restoring APFS is working (on Mac's that have updated firmware)
- The mac's require a firmware update to be able to boot APFS
- Firmware update can be extracted out of the macOS Install app
  (see macadmin slack, #autodmg, this snippet worked for me https://macadmins.slack.com/files/bochoven/F6X6EF0SJ/Create_standalone_FirmwareUpdate_pkg.sh )
-The resulting package can be deployed TO A BOOT VOLUME with DeployStudio (not postponed), but requires a reboot to do the actual update.

So there is a catch 22: the Mac must have the firmware update before it can boot APFS.
Apple recommends to do upgrades (because it will convert HFS to APFS for SSD's, and update firmware to enable APFS booting)

How to do this in DeployStudio? A working solution can be:
1-Netboot, run workflow to install FirmwareUpdate pkg on existing HFS volume
2-reboot from local disk to install firmware
3-Netboot, run workflow to restore APFS

How to automate this? (designed for any mac in your fleet, any macOS version on it)
-There must be check for SSD's (default not converted by Apple upgrade, and restore failed on my iMac 2014 with HDD)
-how to automate the two workflows? default workflow automation can only use one (?!), or can we use some smart IF..-THEN embedded_workflow_1, ELSE embedded_workflow_2 ?
Not tried yet

Last edited by mjsanders (2017-08-31 14:10:49)

Offline

#5 2017-08-31 18:34:08

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

As fiddly as it sounds, maybe do the firmware update manually before netbooting?
and, um, how does one access the macadmins slack channel if one does not have a macadmins email address?

Last edited by Meat (2017-08-31 18:38:23)

Offline

#6 2017-08-31 19:13:45

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

enroll with (any) emailaddress here: https://macadmins.herokuapp.com

I have managed to extract the firmware update out of the Install macOS app, and deploy this as a pkg using deploystudio.
Great !

(but you can only test once on each Mac; when EFI is up to date, installer fails)

Offline

#7 2017-08-31 20:58:32

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

Does the extracted firmware update support multiple mac models?

Offline

#8 2017-09-01 08:25:03

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

It should, all the files are included, but I only tested it (yet) on a MacBookPro8.1

If I take a look inside one of the subfolders I can see these EFI firmwares, and this looks like the complete (? not checked) list of 10.13 supported Mac's (taken from 10.13 beta8) of munkipkg folder

$ls  FWupdSA_10.13b8/scripts/Tools/EFIPayloads/
IM101_00CF_00B.scap	IM171_0110_B00.fd	MBA71_0171_B00.fd	MBP143_0167_B00.fd
IM111_0037_00B.scap	IM181_0151_B00.fd	MBP101_00F2_B00.scap	MBP61_005A_00B.scap
IM112_005B_00B.scap	IM183_0151_B00.fd	MBP102_010B_B00.scap	MBP71_003D_00B.scap
IM121_004D_00B.scap	MB101_0154_B00.fd	MBP111_0142_B00.scap	MBP81_004D_00B.scap
IM131_010F_B00.scap	MB61_00CB_00B.scap	MBP112_0142_B00.scap	MBP91_00D7_B00.scap
IM141_0123_B00.scap	MB71_003D_00B.scap	MBP114_0177_B00.fd	MM41_0045_00B.scap
IM142_0123_B00.scap	MB81_0168_B00.fd	MBP121_0171_B00.fd	MM51_007B_B00.scap
IM143_0123_B00.scap	MB91_0159_B00.fd	MBP131_0212_B00.fd	MM61_010B_B00.scap
IM144_0183_B00.scap	MBA31_0067_00B.scap	MBP132_0233_B00.fd	MM71_0224_B00.scap
IM151_0211_B00.scap	MBA41_007B_B00.scap	MBP133_0233_B00.fd	MP61_0120_B00.scap
IM161_0212_B00.fd	MBA51_00F4_B00.scap	MBP141_0167_B00.fd
IM162_0212_B00.fd	MBA61_0103_B00.scap	MBP142_0167_B00.fd

Offline

#9 2017-09-12 11:03:34

jelockwood
Member
Registered: 2009-11-11

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

> mjsanders wrote:

> It should, all the files are included, but I only tested it (yet) on a MacBookPro8.1

If I take a look inside one of the subfolders I can see these EFI firmwares, and this looks like the complete (? not checked) list of 10.13 supported Mac's (taken from 10.13 beta8) of munkipkg folder

$ls  FWupdSA_10.13b8/scripts/Tools/EFIPayloads/
IM101_00CF_00B.scap	IM171_0110_B00.fd	MBA71_0171_B00.fd	MBP143_0167_B00.fd
IM111_0037_00B.scap	IM181_0151_B00.fd	MBP101_00F2_B00.scap	MBP61_005A_00B.scap
IM112_005B_00B.scap	IM183_0151_B00.fd	MBP102_010B_B00.scap	MBP71_003D_00B.scap
IM121_004D_00B.scap	MB101_0154_B00.fd	MBP111_0142_B00.scap	MBP81_004D_00B.scap
IM131_010F_B00.scap	MB61_00CB_00B.scap	MBP112_0142_B00.scap	MBP91_00D7_B00.scap
IM141_0123_B00.scap	MB71_003D_00B.scap	MBP114_0177_B00.fd	MM41_0045_00B.scap
IM142_0123_B00.scap	MB81_0168_B00.fd	MBP121_0171_B00.fd	MM51_007B_B00.scap
IM143_0123_B00.scap	MB91_0159_B00.fd	MBP131_0212_B00.fd	MM61_010B_B00.scap
IM144_0183_B00.scap	MBA31_0067_00B.scap	MBP132_0233_B00.fd	MM71_0224_B00.scap
IM151_0211_B00.scap	MBA41_007B_B00.scap	MBP133_0233_B00.fd	MP61_0120_B00.scap
IM161_0212_B00.fd	MBA51_00F4_B00.scap	MBP141_0167_B00.fd
IM162_0212_B00.fd	MBA61_0103_B00.scap	MBP142_0167_B00.fd

As far as I can see the above list is missing at least one model although this maybe deliberate. It is missing the MacPro5,1 for example which is officially supported by High Sierra. One obvious conclusion is that while a MacPro5,1 may support booting High Sierra it might not support booting High Sierra with an APFS volume.

It is somewhat surprising the MacPro5,1 is not listed since the equally old and also hard drive based Macmini4,1 is listed.

There have been firmware updaters in the past for the MacPro5,1 - this is after all how people unofficially upgrade MacPro4,1 models to 5,1 firmware enabling those 4,1 models to then run Sierra and High Sierra.

Offline

#10 2017-09-24 02:00:28

smajor
Member
Registered: 2013-11-23

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

Does anyone more in the know than me have a sense of APFS being supported on HDD?  I'm tempted to image 10.13 with HFS+ only on SSD & HDD until it's more universal (which will probably still boot an SSD, right)?

Offline

#11 2017-09-25 08:07:56

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

The reports about 'official' supported are contra litlle adicting:
-in the original specs Apple states that APFS is optimised for SSD, but will work on HD too .(https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/Introduction/Introduction.html, FAQ 1)

"Can I use Apple File System with my existing hard disk drive?
Yes. Apple File System is optimized for Flash/SSD storage, but can also be used with traditional hard disk drives (HDD) and external, direct-attached storage."

-in https://support.apple.com/en-gb/HT208018 it states: that SSD will be converted, no opt-out, and HD/fusion are not converted.

"When you install macOS High Sierra on the Mac volume of a solid-state drive (SSD) or other all-flash storage device, that volume is automatically converted to APFS. Fusion Drives, traditional hard disk drives (HDDs), and non-Mac volumes aren't converted. You can't opt out of the transition to APFS."

No word about if it is supported to convert HD to APFS manually.
But if apple does not convert by default there will be reasons.
I will wait with converting HD's (at least for 10.13.1 update ...)
And in my testing DeployStudio refuses to restore APFS to HD.

edit :

In this document https://beta.apple.com/sp/betaprogram/apfsfusion Apple states:

"The initial release of macOS High Sierra will provide support for the new Apple File System as the default boot filesystem on Mac systems with all-Flash built-in storage. If you installed a beta version of macOS High Sierra, the Fusion Drive in your Mac may have been converted to Apple File System. Because this configuration is not supported in the initial release of macOS High Sierra, we recommend that you follow the steps below to revert back to the previous disk format."

According to this post: APFS on fusion drive is not supported in initial release of 10.13.
Let;s wait for updates...

Last edited by mjsanders (2017-09-25 16:09:08)

Offline

#12 2017-09-26 01:49:55

Phych
Member
Registered: 2012-04-05

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

> mjsanders wrote:

> No word about if it is supported to convert HD to APFS manually.
> And in my testing DeployStudio refuses to restore APFS to HD.

I've successfully converted a couple HDDs to APFS manually (Mini 7,1) about a week ago, although I'm having the same problem as you in DS 1.7.8, where, when netbooted to DS, DS Runtime will quit out and a Terminal window will open with nothing happening when a restore task with an APFS image is executed.

Offline

#13 2017-10-03 15:39:34

cem62793
Member
Registered: 2015-11-05

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

I would like to see the steps of this setup as a workflow so I can reproduce it on our server here. I am going to have a workflow specifically for ssd's and apfs

Offline

#14 2017-10-03 15:43:15

costasppc
Member
Registered: 2008-01-23

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

A 10.13 nbi is needed for this. I created one, formatted the disk via the nbi's Disk Utility to APFS and used first disk available. Worked OK. Havent tested yet to restore to specific partitions.
My nbi is booting in 6 minutes (wired or wireless).

Best regards

Kostas

Offline

#15 2017-10-05 11:31:54

jelockwood
Member
Registered: 2009-11-11

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

As per this thread there is an approach where DeployStudio can run a workflow that allows formatting a drive as APFS and then restoring an image on to it. The trick part is checking and if needed updating the firmware.

It maybe that dealing with the firmware would be best done by a different tool to DeployStudio - for example Munki. You could have a package in Munki that you deploy based on a conditional check. The conditional check would first look for the current firmware version - here is a command to get the current firmware version

system_profiler SPHardwareDataType | grep -i "ROM Version" | awk -F ': ' '{print $2}'

If it is determined to be too old then the install is run. You would do this to your entire fleet and then you can presume in DeployStudio that all your Macs are already running new enough firmware.

It maybe however that another better approach would be adding functionality in DeployStudio to handle this directly. As far as I can see the current DeployStudio package install process does not provide a means of including conditional checks unless you create your own custom installer package as a wrapper around a standard install package. Hence it would currently fail if already up-to-date and then this causes the entire workflow to fail.

Frankly Apple are creating a problem here where one did not used to exist. It used to be that such firmware updates were simply pushed out using the standard Apple Software Update Mechanism and therefore would have automatically been installed.

Offline

#16 2017-10-05 13:44:17

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

I have learned two things in the past days:

1-extracting the firmware update out of Install macOS High Sierra app is currently working, but not supported by Apple. There are signs that in the near future (10.14 or even before that) firmware updates are ONLY part of macOS install/update. The reason is that there may be more updates than the EFI update (adapters, touchbar, etc) So we should not rely on this to work in the (near) future.

2-having said that, I found that on my fleet most mac's do boot from APFS, even with older firmware. (except 1 MacBook Pro 13" 2011).

So out of simplicity I have created this workflow that will restore any Mac to 10.13 state, (almost supported)

1-partition disk (1 partition)
2-restore APFS image (created by AutoDMG) to 'first disk available'
3-install pgk with firmware updates (unsupported, but working, see above) to install post-poned.
4-configure ... (as usual)

Netboot from DS .nbi (must be 10.13, I used DS 1.7.8)

this is what happends after restore:
-ds_finalize.sh will run, do configurationh, install pkg, and reboot again.
-if FW is out of date, firmware update will happen
-if FW is up to date, the pkg may try to install 3 times, with 3 reboots, then ds_finalize.sh gives up, and you can log in.

Running with 10.13 from APFS, and firmware update installed, mission accomplised.

Notes:
-I have no touchbar mac's in my fleet, so your milage may vary with those (I expect more or complex FW updates there)
-APFS restore works only on SSD's
-I decided that although not the official supported way, this method is the method I have now working, and worked for all Mac's (2010-2016 models iMac, MacBook air, etc) except 1, so this is good enough for me.
-this workflow is a one stop imaging workflow that results in a working High Sierra install, almost approved.
-MacPro5,1 does not have firmware in the package, need to install High Sierra manually to get EFI update.

Offline

#17 2017-10-11 20:16:18

stutz
Member
Registered: 2013-08-15

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

I've been working on this issue since 1.7.8 was released and I can't seem to get DS to image a computer properly with AFPS.

I created my 10.13 OS using AutoDMG.  I used the exact workflow as mention above who has it working for them but the workflow fails immediately when it gets to the "Restore" payload.  The error says "Sorry, cannot get the device destination for volume".  If I use an already formatted HFS+ partition and try the same workflow the error says "The destination volume is too small."  Anyone have any suggestions?

Output of the log file:

2017-10-11 14:05:24.156 DeployStudio Runtime.bin[334:21512] Running workflow: ' 10.13.0 (AFPs) - Base' (36BAF127-D32A-415A-BA1D-DEAE0784CD10)
2017-10-11 14:05:24.559 DeployStudio Runtime.bin[334:15347] Looking for available disks:
2017-10-11 14:05:24.560 DeployStudio Runtime.bin[334:15347] Boot device='/dev/disk1'
2017-10-11 14:05:24.560 DeployStudio Runtime.bin[334:15347] Repository device='(null)'
2017-10-11 14:05:24.560 DeployStudio Runtime.bin[334:15347] >> '/dev/disk1': boot disk
2017-10-11 14:05:24.655 DeployStudio Runtime.bin[334:15347] >> '/dev/disk0': ok (SSD)
2017-10-11 14:05:35.167 DeployStudio Runtime.bin[334:21507] Partitioning action:
2017-10-11 14:05:35.169 DeployStudio Runtime.bin[334:21507] Target disk size: 500277790720 bytes (500068075520 bytes available for custom partitions)
2017-10-11 14:05:35.169 DeployStudio Runtime.bin[334:21507] "/Applications/Utilities/DeployStudio Admin.app/Contents/Plugins/DSPartitionTask.bundle/Contents/Resources/Scripts/deleteparentlvg.sh" /dev/disk0 2>&1
2017-10-11 14:05:35.320 DeployStudio Runtime.bin[334:21507] /usr/sbin/diskutil unmountDisk force /dev/disk0 2>&1
2017-10-11 14:05:35.477 DeployStudio Runtime.bin[334:21507] Forced unmount of all volumes on disk0 was successful
2017-10-11 14:05:35.480 DeployStudio Runtime.bin[334:21507] /usr/sbin/diskutil partitionDisk /dev/disk0 1 GPTFormat "Journaled HFS+" "Macintosh HD" 1B 2>&1
2017-10-11 14:05:35.544 DeployStudio Runtime.bin[334:21507] Started partitioning on disk0
2017-10-11 14:05:35.545 DeployStudio Runtime.bin[334:21507] Unmounting disk
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk3 Mount point: /Volumes Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk8 Mount point: /private/var/folders Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk16 Mount point: /Library/Logs Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk11 Mount point: /Library/Preferences Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk2 Mount point: /private/var/log Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.900 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk18 Mount point: /Library/Caches Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk7 Mount point: /private/var/db Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk13 Mount point: /Library/Keychains Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk6 Mount point: /System/Installation Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk15 Mount point: /private/var/db/dslocal/nodes/Default/users Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk10 Mount point: /Library/ColorSync/Profiles/Displays Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk5 Mount point: /private/var/run Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.901 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk17 Mount point: /Library/Logs/DiagnosticReports Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.902 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk12 Mount point: /Library/Preferences/SystemConfiguration Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.902 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk4 Mount point: /private/var/tmp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.902 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk9 Mount point: /private/var/root/Library Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:35.902 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk14 Mount point: /private/var/tmp/RecoveryTemp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.375 DeployStudio Runtime.bin[334:21507] Creating the partition map
2017-10-11 14:05:36.404 DeployStudio Runtime.bin[334:21507] Waiting for partitions to activate
2017-10-11 14:05:36.411 DeployStudio Runtime.bin[334:21507] Formatting disk0s2 as Mac OS Extended (Journaled) with name Macintosh HD
2017-10-11 14:05:36.952 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk3 Mount point: /Volumes Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.952 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk8 Mount point: /private/var/folders Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.952 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk16 Mount point: /Library/Logs Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.952 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk11 Mount point: /Library/Preferences Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk2 Mount point: /private/var/log Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk18 Mount point: /Library/Caches Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk7 Mount point: /private/var/db Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk13 Mount point: /Library/Keychains Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk6 Mount point: /System/Installation Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk15 Mount point: /private/var/db/dslocal/nodes/Default/users Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.953 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk10 Mount point: /Library/ColorSync/Profiles/Displays Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk5 Mount point: /private/var/run Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk17 Mount point: /Library/Logs/DiagnosticReports Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk12 Mount point: /Library/Preferences/SystemConfiguration Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk4 Mount point: /private/var/tmp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk9 Mount point: /private/var/root/Library Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:36.954 Disk Utility[453:21043] Failed to get physical whole disk: SKDisk { BSD Name: disk14 Mount point: /private/var/tmp/RecoveryTemp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-11 14:05:37.368 DeployStudio Runtime.bin[334:21507] Initialized /dev/rdisk0s2 as a 466 GB case-insensitive HFS Plus volume with a 40960k journal
2017-10-11 14:05:37.369 DeployStudio Runtime.bin[334:21507] Mounting disk
2017-10-11 14:05:37.484 DeployStudio Runtime.bin[334:21507] Finished partitioning on disk0
2017-10-11 14:05:37.489 DeployStudio Runtime.bin[334:21507] /dev/disk0 (internal, physical):
2017-10-11 14:05:37.489 DeployStudio Runtime.bin[334:21507]    #:                       TYPE NAME                    SIZE       IDENTIFIER
2017-10-11 14:05:37.489 DeployStudio Runtime.bin[334:21507]    0:      GUID_partition_scheme                        *500.3 GB   disk0
2017-10-11 14:05:37.489 DeployStudio Runtime.bin[334:21507]    1:                        EFI EFI                     209.7 MB   disk0s1
2017-10-11 14:05:37.489 DeployStudio Runtime.bin[334:21507]    2:                  Apple_HFS Macintosh HD            499.9 GB   disk0s2
2017-10-11 14:05:47.496 DeployStudio Runtime.bin[334:21507] -> Partitioning action completed.
2017-10-11 14:05:47.497 DeployStudio Runtime.bin[334:21507] Partitioning successful (elapsed time: 0.21 minutes)
2017-10-11 14:05:51.946 DeployStudio Runtime.bin[334:21529] Restore action:
2017-10-11 14:05:52.171 DeployStudio Runtime.bin[334:21529] '/tmp/DSNetworkRepository/Masters/APFS/Base-10.13-17A362a.apfs.dmg' size: 24696.1 MB
2017-10-11 14:05:52.171 DeployStudio Runtime.bin[334:21529] '/Volumes/Macintosh HD' size: 499933.8 MB
2017-10-11 14:05:52.171 DeployStudio Runtime.bin[334:21529] "/Applications/Utilities/DeployStudio Admin.app/Contents/Frameworks/DSCore.framework/Resources/Tools/apfsphysicaldeviceid.sh" "/Volumes/Macintosh HD" 2>&1
2017-10-11 14:05:52.194 DeployStudio Runtime.bin[334:21529] Sorry, cannot get device for volume '/Volumes/Macintosh HD'
2017-10-11 14:05:52.194 DeployStudio Runtime.bin[334:21529] -> Restore action completed.
2017-10-11 14:05:52.194 DeployStudio Runtime.bin[334:21529] Restoration failure (elapsed time: 0.00 minutes)

Last edited by stutz (2017-10-11 20:17:04)

Offline

#18 2017-10-12 09:04:51

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

@stutz, I can run my workflow fine.
I guess there is a difference in the first two steps:
1-partition disk (one partition, user choice in my case, all options DE-selected)
2- restore (to first available disk, apfs type, Selected: Don't check restoratation, Delete machine dependent files and caches, rename ByHost prefs, Restore system recovery partitons, Automate. Others DE-selected

I am using a netboot setup (you are using a USB disk?)

Check the settings for the first 2 steps, and for comparison, my logs for a succefull restore of APFS volume to a macbook Pro 2011 with samsung evo 840look like this:

2017-09-25 13:00:18.658 DeployStudio Runtime.bin[357:8552] *** WARNING: Textured window <TransparentWindow: 0x7fae92d3b6e0> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.
2017-09-25 13:00:18.850 DeployStudio Runtime.bin[357:8552] ====================================================================================================
2017-09-25 13:00:18.851 DeployStudio Runtime.bin[357:8552] DeployStudio Runtime
2017-09-25 13:00:18.858 DeployStudio Runtime.bin[357:8552] DSCore.framework version 1.7.8 (b170908), Copyright 2017 The DeployStudio Team.
2017-09-25 13:00:18.860 DeployStudio Runtime.bin[357:8552] MAC address: 3c:07:54:XXXXXX
2017-09-25 13:00:18.898 DeployStudio Runtime.bin[357:8552] Network address: 10.0.0.253 (mac-c0CCCCC.local)
2017-09-25 13:00:18.924 DeployStudio Runtime.bin[357:8552] Network interface speed: AUTOSELECT (1000BASET <FULL-DUPLEX,FLOW-CONTROL>)
2017-09-25 13:00:18.949 DeployStudio Runtime.bin[357:8552] Operating System: Mac OS X Version 10.13 (Build 17A358a)
2017-09-25 13:00:18.950 DeployStudio Runtime.bin[357:8552] Date: 17/09/25 15:00:18
2017-09-25 13:00:18.950 DeployStudio Runtime.bin[357:8552] ====================================================================================================
2017-09-25 13:00:19.748 DeployStudio Runtime.bin[357:8552] 24 plugins were successfully loaded!
2017-09-25 13:00:22.856 DeployStudio Runtime.bin[357:8732] The user 'deploy' was successfully authenticated.
2017-09-25 13:00:23.041 DeployStudio Runtime.bin[357:8552] Connected to server mainserver.pretendco.com (1.7.8)
2017-09-25 13:00:23.692 DeployStudio Runtime.bin[357:54455] Checking server reachability (server=mainserver.local port=445) ...
2017-09-25 13:00:23.714 DeployStudio Runtime.bin[357:54455] Mounting repository share point...
2017-09-25 13:00:23.715 DeployStudio Runtime.bin[357:54455] /bin/mkdir /tmp/DSNetworkRepository 2>&1
2017-09-25 13:00:23.728 DeployStudio Runtime.bin[357:54455] /bin/chmod 777 /tmp/DSNetworkRepository 2>&1
2017-09-25 13:00:23.741 DeployStudio Runtime.bin[357:54455] /bin/chmod 777 /tmp/DSNetworkRepository 2>&1
2017-09-25 13:00:23.754 DeployStudio Runtime.bin[357:54455] Mount call...
2017-09-25 13:00:25.431 DeployStudio Runtime.bin[357:54455] Parsing result...
2017-09-25 13:00:25.444 DeployStudio Runtime.bin[357:54455] Checking repository content...
2017-09-25 13:00:26.416 DeployStudio Runtime.bin[357:54455] Checking host firmware version
2017-09-25 13:00:26.564 DeployStudio Runtime.bin[357:54455] Macintosh serial number: C02GXXXXX
2017-09-25 13:00:26.564 DeployStudio Runtime.bin[357:54455] Macintosh model: MacBookPro8,1
2017-09-25 13:00:26.564 DeployStudio Runtime.bin[357:54455] Boot ROM version: MBP81.88Z.0047.B32.1702180130
2017-09-25 13:00:26.564 DeployStudio Runtime.bin[357:54455] Firmware ok!
2017-09-25 13:01:49.349 DeployStudio Runtime.bin[357:57046] Running workflow: '9-restore 10.13 apfs incl FW update' (35AE0B8F-59D9-439D-A5A1-F6FCFA572698)
2017-09-25 13:01:50.209 DeployStudio Runtime.bin[357:8552] Looking for available disks:
2017-09-25 13:01:50.209 DeployStudio Runtime.bin[357:8552] Boot device='/dev/disk2'
2017-09-25 13:01:50.209 DeployStudio Runtime.bin[357:8552] Repository device='(null)'
2017-09-25 13:01:50.209 DeployStudio Runtime.bin[357:8552] >> '/dev/disk2': boot disk
2017-09-25 13:01:50.457 DeployStudio Runtime.bin[357:8552] >> '/dev/disk1': ok (SSD)
2017-09-25 13:01:50.600 DeployStudio Runtime.bin[357:8552] >> '/dev/disk0': ok (SSD)
2017-09-25 13:02:02.532 DeployStudio Runtime.bin[357:57046] Partitioning action:
2017-09-25 13:02:02.534 DeployStudio Runtime.bin[357:57046] Target disk size: 250059350016 bytes (249849634816 bytes available for custom partitions)
2017-09-25 13:02:02.535 DeployStudio Runtime.bin[357:57046] "/Applications/Utilities/DeployStudio Admin.app/Contents/Plugins/DSPartitionTask.bundle/Contents/Resources/Scripts/deleteparentlvg.sh" /dev/disk0 2>&1
2017-09-25 13:02:02.812 DeployStudio Runtime.bin[357:57046] /usr/sbin/diskutil unmountDisk force /dev/disk0 2>&1
2017-09-25 13:02:02.979 DeployStudio Runtime.bin[357:57046] Forced unmount of all volumes on disk0 was successful
2017-09-25 13:02:02.983 DeployStudio Runtime.bin[357:57046] /usr/sbin/diskutil partitionDisk /dev/disk0 1 GPTFormat "Journaled HFS+" "Untitled 1" 1B 2>&1
2017-09-25 13:02:03.106 DeployStudio Runtime.bin[357:57046] Started partitioning on disk0
2017-09-25 13:02:03.107 DeployStudio Runtime.bin[357:57046] Unmounting disk
2017-09-25 13:02:03.687 DeployStudio Runtime.bin[357:57046] Creating the partition map
2017-09-25 13:02:03.765 DeployStudio Runtime.bin[357:57046] Waiting for partitions to activate
2017-09-25 13:02:03.775 DeployStudio Runtime.bin[357:57046] Formatting disk0s2 as Mac OS Extended (Journaled) with name Untitled 1
2017-09-25 13:02:04.741 DeployStudio Runtime.bin[357:57046] Initialized /dev/rdisk0s2 as a 233 GB case-insensitive HFS Plus volume with a 24576k journal
2017-09-25 13:02:04.756 DeployStudio Runtime.bin[357:57046] Mounting disk
2017-09-25 13:02:04.871 DeployStudio Runtime.bin[357:57046] Finished partitioning on disk0
2017-09-25 13:02:04.884 DeployStudio Runtime.bin[357:57046] /dev/disk0 (internal, physical):
2017-09-25 13:02:04.884 DeployStudio Runtime.bin[357:57046]    #:                       TYPE NAME                    SIZE       IDENTIFIER
2017-09-25 13:02:04.885 DeployStudio Runtime.bin[357:57046]    0:      GUID_partition_scheme                        *250.1 GB   disk0
2017-09-25 13:02:04.885 DeployStudio Runtime.bin[357:57046]    1:                        EFI EFI                     209.7 MB   disk0s1
2017-09-25 13:02:04.885 DeployStudio Runtime.bin[357:57046]    2:                  Apple_HFS Untitled 1              249.7 GB   disk0s2
2017-09-25 13:02:14.893 DeployStudio Runtime.bin[357:57046] -> Partitioning action completed.
2017-09-25 13:02:14.893 DeployStudio Runtime.bin[357:57046] Partitioning successful (elapsed time: 0.21 minutes)
2017-09-25 13:02:16.843 DeployStudio Runtime.bin[357:57046] Restore action:
2017-09-25 13:02:17.184 DeployStudio Runtime.bin[357:57081] Looking for solid-state drives:
2017-09-25 13:02:17.184 DeployStudio Runtime.bin[357:57081] Boot device='/dev/disk2'
2017-09-25 13:02:17.184 DeployStudio Runtime.bin[357:57081] Repository device='(null)'
2017-09-25 13:02:17.184 DeployStudio Runtime.bin[357:57081] Devices to evaluate: /dev/disk0,/dev/disk10,/dev/disk11,/dev/disk12,/dev/disk13,/dev/disk14,/dev/disk15,/dev/disk16,/dev/disk17,/dev/disk18,/dev/disk19,/dev/disk2,/dev/disk20,/dev/disk3,/dev/disk4,/dev/disk5,/dev/disk6,/dev/disk7,/dev/disk8,/dev/disk9,
2017-09-25 13:02:17.184 DeployStudio Runtime.bin[357:57081] >> '/dev/disk2': boot disk
2017-09-25 13:02:17.329 DeployStudio Runtime.bin[357:57081] >> '/dev/disk0': ok (SSD)
2017-09-25 13:02:17.330 DeployStudio Runtime.bin[357:57081] "/Applications/Utilities/DeployStudio Admin.app/Contents/Plugins/DSRestoreTask.bundle/Contents/Resources/Scripts/deleteparentlvg.sh" /dev/disk0 2>&1
2017-09-25 13:02:17.585 DeployStudio Runtime.bin[357:57081] /usr/sbin/diskutil unmountDisk force /dev/disk0 2>&1
2017-09-25 13:02:17.740 DeployStudio Runtime.bin[357:57081] Forced unmount of all volumes on disk0 was successful
2017-09-25 13:02:17.744 DeployStudio Runtime.bin[357:57081] /usr/sbin/diskutil partitionDisk /dev/disk0 1 GPTFormat APFS _DS_DEV_DISK_X_ 1B 2>&1
2017-09-25 13:02:17.857 DeployStudio Runtime.bin[357:57081] Started partitioning on disk0
2017-09-25 13:02:17.858 DeployStudio Runtime.bin[357:57081] Unmounting disk
2017-09-25 13:02:18.054 DeployStudio Runtime.bin[357:57081] Creating the partition map
2017-09-25 13:02:18.104 DeployStudio Runtime.bin[357:57081] Waiting for partitions to activate
2017-09-25 13:02:18.114 DeployStudio Runtime.bin[357:57081] Formatting disk0s2 as APFS with name _DS_DEV_DISK_X_
2017-09-25 13:02:18.454 DeployStudio Runtime.bin[357:57081] Mounting disk
2017-09-25 13:02:18.632 DeployStudio Runtime.bin[357:57081] Finished partitioning on disk0
2017-09-25 13:02:18.647 DeployStudio Runtime.bin[357:57081] /dev/disk0 (internal, physical):
2017-09-25 13:02:18.648 DeployStudio Runtime.bin[357:57081]    #:                       TYPE NAME                    SIZE       IDENTIFIER
2017-09-25 13:02:18.648 DeployStudio Runtime.bin[357:57081]    0:      GUID_partition_scheme                        *250.1 GB   disk0
2017-09-25 13:02:18.648 DeployStudio Runtime.bin[357:57081]    1:                        EFI EFI                     209.7 MB   disk0s1
2017-09-25 13:02:18.648 DeployStudio Runtime.bin[357:57081]    2:                 Apple_APFS Container disk1         249.8 GB   disk0s2
2017-09-25 13:02:18.651 DeployStudio Runtime.bin[357:57081] /usr/sbin/diskutil mountDisk /dev/disk0 2>&1
2017-09-25 13:02:19.194 DeployStudio Runtime.bin[357:57081] Volume(s) mounted successfully
2017-09-25 13:02:19.199 DeployStudio Runtime.bin[357:57081] '/tmp/DSNetworkRepository/Masters/APFS/osx-10.13-17A358a.apfs.dmg' size: 24696.1 MB
2017-09-25 13:02:19.199 DeployStudio Runtime.bin[357:57081] '/Volumes/_DS_DEV_DISK_X_' size: 249849.6 MB
2017-09-25 13:02:19.345 DeployStudio Runtime.bin[357:57081] "/Applications/Utilities/DeployStudio Admin.app/Contents/Frameworks/DSCore.framework/Resources/Tools/apfsphysicaldeviceid.sh" /Volumes/_DS_DEV_DISK_X_ 2>&1
2017-09-25 13:02:19.520 DeployStudio Runtime.bin[357:57081] Setting boot device to '/dev/disk1s1'.
2017-09-25 13:02:19.521 DeployStudio Runtime.bin[357:57081] /usr/sbin/diskutil unmount force /dev/disk1s1 2>&1
2017-09-25 13:02:19.743 DeployStudio Runtime.bin[357:57081] Volume _DS_DEV_DISK_X_ on disk1s1 force-unmounted
2017-09-25 13:02:19.749 DeployStudio Runtime.bin[357:57081] /usr/sbin/asr restore --source /tmp/DSNetworkRepository/Masters/APFS/osx-10.13-17A358a.apfs.dmg --target /dev/disk0s2 --puppetstrings --noprompt --noverify --erase --buffers 8 --buffersize 8m 2>&1
2017-09-25 13:02:19.991 DeployStudio Runtime.bin[357:57081] XSTA	start	433	client
2017-09-25 13:02:19.992 DeployStudio Runtime.bin[357:57081] XSTA	setup
2017-09-25 13:02:19.992 DeployStudio Runtime.bin[357:57081] 	Validating target...done
2017-09-25 13:02:19.992 DeployStudio Runtime.bin[357:57081] XSTA	metadata
2017-09-25 13:02:20.872 DeployStudio Runtime.bin[357:57081] 	Validating source...done
2017-09-25 13:02:20.880 DeployStudio Runtime.bin[357:57081] 	Retrieving scan information...done
2017-09-25 13:02:20.966 DeployStudio Runtime.bin[357:57081] 	Validating sizes...nx_kernel_mount:1364: checkpoint search: largest xid 84, best xid 84 @ 38
2017-09-25 13:02:20.976 DeployStudio Runtime.bin[357:57081] done
2017-09-25 13:02:21.076 DeployStudio Runtime.bin[357:57081] XSTA	restore
2017-09-25 13:02:21.076 DeployStudio Runtime.bin[357:57081] PSTT	0	100	start restore
2017-09-25 13:02:23.288 DeployStudio Runtime.bin[357:57081] Progress: 2
2017-09-25 13:02:35.631 DeployStudio Runtime.bin[357:57081] Progress: 8
2017-09-25 13:02:47.874 DeployStudio Runtime.bin[357:57081] Progress: 14
2017-09-25 13:03:04.230 DeployStudio Runtime.bin[357:57081] Progress: 20
2017-09-25 13:03:16.092 DeployStudio Runtime.bin[357:57081] Progress: 26
2017-09-25 13:03:31.485 DeployStudio Runtime.bin[357:57081] Progress: 32
2017-09-25 13:03:39.979 DeployStudio Runtime.bin[357:57081] Progress: 38

Offline

#19 2017-10-12 14:23:24

stutz
Member
Registered: 2013-08-15

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

@mjsanders, I followed your workflow and I received the error: "Sorry, the target volume is too small to restore this image".  I'm running this workflow on a MacBook Pro (Retina, 15-inch, Mid 2015).

Some log lines that are different between your log and my log are:

2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] Boot device='/dev/disk1'
Your log shows: Boot device='/dev/disk2'

2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] >> '/dev/disk1': boot disk
Your log shows: '/dev/disk2': boot disk

2017-10-12 08:54:53.623 DeployStudio Runtime.bin[331:21921] APFS does not appear to be a valid file system format or partition type
2017-10-12 08:54:53.623 DeployStudio Runtime.bin[331:21921] Use diskutil listFilesystems to view a list of supported file systems

2017-10-12 08:54:53.894 DeployStudio Runtime.bin[331:21921] '/Volumes/_DS_DEV_DISK_X_' size: 0.0 MB
Your log shows: '/Volumes/_DS_DEV_DISK_X_' size: 249849.6 MB

2017-10-12 08:54:53.894 DeployStudio Runtime.bin[331:21921] Sorry, the target volume is too small to restore this image


Log output after following your exact workflow.

2017-10-12 08:54:35.704 DeployStudio Runtime.bin[331:21997] Running workflow: ' 10.13.0 (AFPs) - Base' (36BAF127-D32A-415A-BA1D-DEAE0784CD10)
2017-10-12 08:54:35.828 DeployStudio Runtime.bin[331:15338] Looking for available disks:
2017-10-12 08:54:35.828 DeployStudio Runtime.bin[331:15338] Boot device='/dev/disk1'
2017-10-12 08:54:35.828 DeployStudio Runtime.bin[331:15338] Repository device='(null)'
2017-10-12 08:54:35.828 DeployStudio Runtime.bin[331:15338] >> '/dev/disk1': boot disk
2017-10-12 08:54:35.919 DeployStudio Runtime.bin[331:15338] >> '/dev/disk0': ok (SSD)
2017-10-12 08:54:39.836 DeployStudio Runtime.bin[331:21921] Partitioning action:
2017-10-12 08:54:39.838 DeployStudio Runtime.bin[331:21921] Target disk size: 500277790720 bytes (500068075520 bytes available for custom partitions)
2017-10-12 08:54:39.839 DeployStudio Runtime.bin[331:21921] "/Applications/Utilities/DeployStudio Admin.app/Contents/Plugins/DSPartitionTask.bundle/Contents/Resources/Scripts/deleteparentlvg.sh" /dev/disk0 2>&1
2017-10-12 08:54:39.988 DeployStudio Runtime.bin[331:21921] /usr/sbin/diskutil unmountDisk force /dev/disk0 2>&1
2017-10-12 08:54:40.148 DeployStudio Runtime.bin[331:21921] Forced unmount of all volumes on disk0 was successful
2017-10-12 08:54:40.150 DeployStudio Runtime.bin[331:21921] /usr/sbin/diskutil partitionDisk /dev/disk0 1 GPTFormat "Journaled HFS+" "Untitled 1" 1B 2>&1
2017-10-12 08:54:40.214 DeployStudio Runtime.bin[331:21921] Started partitioning on disk0
2017-10-12 08:54:40.215 DeployStudio Runtime.bin[331:21921] Unmounting disk
2017-10-12 08:54:40.583 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk3 Mount point: /Volumes Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.583 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk8 Mount point: /private/var/folders Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk16 Mount point: /Library/Logs Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk11 Mount point: /Library/Preferences Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk2 Mount point: /private/var/log Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk18 Mount point: /Library/Caches Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk7 Mount point: /private/var/db Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk13 Mount point: /Library/Keychains Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.584 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk6 Mount point: /System/Installation Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk15 Mount point: /private/var/db/dslocal/nodes/Default/users Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk10 Mount point: /Library/ColorSync/Profiles/Displays Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk5 Mount point: /private/var/run Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk17 Mount point: /Library/Logs/DiagnosticReports Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk12 Mount point: /Library/Preferences/SystemConfiguration Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk4 Mount point: /private/var/tmp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.585 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk9 Mount point: /private/var/root/Library Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:40.586 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk14 Mount point: /private/var/tmp/RecoveryTemp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.040 DeployStudio Runtime.bin[331:21921] Creating the partition map
2017-10-12 08:54:41.070 DeployStudio Runtime.bin[331:21921] Waiting for partitions to activate
2017-10-12 08:54:41.076 DeployStudio Runtime.bin[331:21921] Formatting disk0s2 as Mac OS Extended (Journaled) with name Untitled 1
2017-10-12 08:54:41.609 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk3 Mount point: /Volumes Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk8 Mount point: /private/var/folders Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk16 Mount point: /Library/Logs Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk11 Mount point: /Library/Preferences Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk2 Mount point: /private/var/log Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk18 Mount point: /Library/Caches Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk7 Mount point: /private/var/db Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk13 Mount point: /Library/Keychains Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk6 Mount point: /System/Installation Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk15 Mount point: /private/var/db/dslocal/nodes/Default/users Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk10 Mount point: /Library/ColorSync/Profiles/Displays Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk5 Mount point: /private/var/run Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk17 Mount point: /Library/Logs/DiagnosticReports Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk12 Mount point: /Library/Preferences/SystemConfiguration Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk4 Mount point: /private/var/tmp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk9 Mount point: /private/var/root/Library Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk14 Mount point: /private/var/tmp/RecoveryTemp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:42.032 DeployStudio Runtime.bin[331:21921] Initialized /dev/rdisk0s2 as a 466 GB case-insensitive HFS Plus volume with a 40960k journal
2017-10-12 08:54:42.033 DeployStudio Runtime.bin[331:21921] Mounting disk
2017-10-12 08:54:42.147 DeployStudio Runtime.bin[331:21921] Finished partitioning on disk0
2017-10-12 08:54:42.152 DeployStudio Runtime.bin[331:21921] /dev/disk0 (internal, physical):
2017-10-12 08:54:42.152 DeployStudio Runtime.bin[331:21921]    #:                       TYPE NAME                    SIZE       IDENTIFIER
2017-10-12 08:54:42.152 DeployStudio Runtime.bin[331:21921]    0:      GUID_partition_scheme                        *500.3 GB   disk0
2017-10-12 08:54:42.152 DeployStudio Runtime.bin[331:21921]    1:                        EFI EFI                     209.7 MB   disk0s1
2017-10-12 08:54:42.152 DeployStudio Runtime.bin[331:21921]    2:                  Apple_HFS Untitled 1              499.9 GB   disk0s2
2017-10-12 08:54:52.159 DeployStudio Runtime.bin[331:21921] -> Partitioning action completed.
2017-10-12 08:54:52.160 DeployStudio Runtime.bin[331:21921] Partitioning successful (elapsed time: 0.21 minutes)
2017-10-12 08:54:52.939 DeployStudio Runtime.bin[331:21921] Restore action:
2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] Looking for solid-state drives:
2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] Boot device='/dev/disk1'
2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] Repository device='(null)'
2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] Devices to evaluate: /dev/disk0,/dev/disk1,/dev/disk10,/dev/disk11,/dev/disk12,/dev/disk13,/dev/disk14,/dev/disk15,/dev/disk16,/dev/disk17,/dev/disk18,/dev/disk2,/dev/disk3,/dev/disk4,/dev/disk5,/dev/disk6,/dev/disk7,/dev/disk8,/dev/disk9,
2017-10-12 08:54:53.165 DeployStudio Runtime.bin[331:21921] >> '/dev/disk1': boot disk
2017-10-12 08:54:53.245 DeployStudio Runtime.bin[331:21921] >> '/dev/disk0': ok (SSD)
2017-10-12 08:54:53.270 DeployStudio Runtime.bin[331:21921] "/Applications/Utilities/DeployStudio Admin.app/Contents/Plugins/DSRestoreTask.bundle/Contents/Resources/Scripts/deleteparentlvg.sh" /dev/disk0 2>&1
2017-10-12 08:54:53.402 DeployStudio Runtime.bin[331:21921] /usr/sbin/diskutil unmountDisk force /dev/disk0 2>&1
2017-10-12 08:54:53.561 DeployStudio Runtime.bin[331:21921] Forced unmount of all volumes on disk0 was successful
2017-10-12 08:54:53.563 DeployStudio Runtime.bin[331:21921] /usr/sbin/diskutil partitionDisk /dev/disk0 1 GPTFormat APFS _DS_DEV_DISK_X_ 1B 2>&1
2017-10-12 08:54:53.623 DeployStudio Runtime.bin[331:21921] APFS does not appear to be a valid file system format or partition type
2017-10-12 08:54:53.623 DeployStudio Runtime.bin[331:21921] Use diskutil listFilesystems to view a list of supported file systems
2017-10-12 08:54:53.625 DeployStudio Runtime.bin[331:21921] /usr/sbin/diskutil mountDisk /dev/disk0 2>&1
2017-10-12 08:54:53.892 DeployStudio Runtime.bin[331:21921] Volume(s) mounted successfully
2017-10-12 08:54:53.894 DeployStudio Runtime.bin[331:21921] '/tmp/DSNetworkRepository/Masters/APFS/Base-10.13-17A362a.apfs.dmg' size: 24696.1 MB
2017-10-12 08:54:53.894 DeployStudio Runtime.bin[331:21921] '/Volumes/_DS_DEV_DISK_X_' size: 0.0 MB
2017-10-12 08:54:53.894 DeployStudio Runtime.bin[331:21921] Sorry, the target volume is too small to restore this image
2017-10-12 08:54:53.895 DeployStudio Runtime.bin[331:21921] -> Restore action completed.
2017-10-12 08:54:53.895 DeployStudio Runtime.bin[331:21921] Restoration failure (elapsed time: 0.01 minutes)

The other thing is why am I getting all these "Failed to get physical whole disk"?:

2017-10-12 08:54:41.609 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk3 Mount point: /Volumes Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk8 Mount point: /private/var/folders Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk16 Mount point: /Library/Logs Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk11 Mount point: /Library/Preferences Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk2 Mount point: /private/var/log Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk18 Mount point: /Library/Caches Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.610 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk7 Mount point: /private/var/db Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk13 Mount point: /Library/Keychains Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk6 Mount point: /System/Installation Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk15 Mount point: /private/var/db/dslocal/nodes/Default/users Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk10 Mount point: /Library/ColorSync/Profiles/Displays Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk5 Mount point: /private/var/run Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk17 Mount point: /Library/Logs/DiagnosticReports Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.611 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk12 Mount point: /Library/Preferences/SystemConfiguration Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk4 Mount point: /private/var/tmp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk9 Mount point: /private/var/root/Library Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
2017-10-12 08:54:41.612 Disk Utility[434:20058] Failed to get physical whole disk: SKDisk { BSD Name: disk14 Mount point: /private/var/tmp/RecoveryTemp Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }

Offline

#20 2017-10-12 15:54:45

mjsanders
Member
From: Schiedam, Netherlands
Registered: 2008-09-02
Website

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

That is puzzeling, same workflow, different results.
My boot disk was disk2, I think that is because the local disk0 was using corestorage, resulting in Macintosh HD being disk1, and the netboot disk will be disk2.
I note that most of your errors are not reported by Runtime, but by Disk Utility !
I don't understand that. is that running too?
the error in the line

2017-10-12 08:54:53.623 DeployStudio Runtime.bin[331:21921] APFS does not appear to be a valid file system format or partition type

makes me think: is your netboot set 10.13?
Support for apfs is only complete for diskutil, asr etc in 10.13. (70% works in 10.12.x too)

Good luck with finding the root of the issue

Offline

#21 2017-10-12 19:54:49

stutz
Member
Registered: 2013-08-15

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

It appears to have been my Netboot image not being made from a 10.13 OS...figures I didn't try the obvious option.  DS imaged my MBP 2015 with 10.13 APFS perfectly!  Thanks for the clues @mjsanders.

Offline

#22 2017-10-18 03:43:26

shovett
Member
Registered: 2016-11-15

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

hopefully someone can point me in the right direction. We have been using DS for years now..have never really had an issue until High Sierra came along.

We can create an image and deploy High Sierra on older Mac Pro models. When we try this on the new 2017 Mac Pro, we always boot to the folder with a question mark after restore.

This is what we have done.

Mac Pro updated with latest OS updates.
Update DS to 1.7.8. on server running 10.8
Created .nbi file on target Pro that has been updated with the latest High Sierra updates.
Copied .nbi to DS and enabled it.
We can boot to the new .nbi (bit slower than previous .nbi files) and create a master form the volume. This master is then copied to the APFS folder in DS.
We boot to .nbi and restore the master we have created Which shows as filename.i386.apfs.dmg. Select first disk available.
It completes the restore fine and we select QUIT.
The Pro then boots to the ? folder

Is this just not possible at the moment? What would cause the ? folder error.

We have tried erasing the SSD in Disk Utility in the .nbi to APFS before we restore. So far we just cannot get the image to boot after its restored.

thanks for reading

Offline

#23 2017-10-19 21:16:41

Phych
Member
Registered: 2012-04-05

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

> shovett wrote:

> hopefully someone can point me in the right direction. We have been using DS for years now..have never really had an issue until High Sierra came along.

>We can create an image and deploy High Sierra on older Mac Pro models. When we try this on the new 2017 Mac Pro, we always boot to the folder with a question mark after restore.

>This is what we have done.

>Mac Pro updated with latest OS updates.
>Update DS to 1.7.8. on server running 10.8
>Created .nbi file on target Pro that has been updated with the latest High Sierra updates.
>Copied .nbi to DS and enabled it.
>We can boot to the new .nbi (bit slower than previous .nbi files) and create a master form the volume. This master is then copied to the APFS folder in DS.
>We boot to .nbi and restore the master we have created Which shows as filename.i386.apfs.dmg. Select first disk available.
>It completes the restore fine and we select QUIT.
>The Pro then boots to the ? folder

>Is this just not possible at the moment? What would cause the ? folder error.

>We have tried erasing the SSD in Disk Utility in the .nbi to APFS before we restore. So far we just cannot get the image to boot after its restored.

I'm having the same problem on an iMac18,1 and my server is on High Sierra. I'm getting the question mark folder after restore. I've been able to get the system to boot by reinstalling High Sierra via USB, but that defeats the purpose of having a network restore in the first place.

Last edited by Phych (2017-10-19 21:18:20)

Offline

#24 2017-10-24 00:23:19

Trikster
Member
Registered: 2015-06-25

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

> shovett wrote:

> hopefully someone can point me in the right direction. We have been using DS for years now..have never really had an issue until High Sierra came along.

> We can create an image and deploy High Sierra on older Mac Pro models. When we try this on the new 2017 Mac Pro, we always boot to the folder with a question mark after restore.

> This is what we have done.

> Mac Pro updated with latest OS updates.
> Update DS to 1.7.8. on server running 10.8
> Created .nbi file on target Pro that has been updated with the latest High Sierra updates.
> Copied .nbi to DS and enabled it.
> We can boot to the new .nbi (bit slower than previous .nbi files) and create a master form the volume. This master is then copied to the APFS folder in DS.
> We boot to .nbi and restore the master we have created Which shows as filename.i386.apfs.dmg. Select first disk available.
> It completes the restore fine and we select QUIT.
> The Pro then boots to the ? folder

> Is this just not possible at the moment? What would cause the ? folder error.

> We have tried erasing the SSD in Disk Utility in the .nbi to APFS before we restore. So far we just cannot get the image to boot after its restored.

> thanks for reading


Does the target computer have the firmware installed onto it before the imaging process?

Last edited by Trikster (2017-10-24 00:24:07)

Offline

#25 2017-10-24 23:12:50

pjmills
Member
Registered: 2017-10-24

Re: DS 1.7.7 and APFS restore of 10.13 is possible :-) !

Hello, hoping someone can help out.

I have been able to successfully image a MacBook Air (13-inch, Early 2015) with a High Sierra image created from AutoDMG (version 1.8) and deployed with DeployStudio (version 1.7.8).  However I had to install High Sierra on the computer first for the image to boot. I understand this has to do with the Firmware. The Netbook image used was created from the 10.13 image.

I am trying this again on another MacBook Air that currently has Sierra 10.12.6 installed. It does not have the required firmware yet. It is running firmware MBA71.0166.B08. I have extracted the Firmware from the 17A405 installer using the below methods:
http://www.amsys.co.uk/2017/09/deploying-firmware-updates-imaging/
https://www.afp548.com/2017/08/31/uefi-10-13apfs-and-your-imaging/

I have tried deploying the firmwareupdatestandalone-1.0.pkg file using DeployStudio as postponed. It fails every time. I tried installing it manually and it fails.

Can anyone point me in the right direction?

Thank you

Offline

Board footer

Powered by FluxBB