You are not logged in.


[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 Re: Debug » 1.7.6 and 10.12.6 - latest hardware » 2017-09-21 10:22:50

Download the 10.12.6 installer from the app store, create a DMG of it with AutoDMG, mount the resulted DMG file and use the DS assistant to take that as the source instead.

This should fix your issue.

#2 Debug » [1.7.8] Netboot on 10.12 and 10.13 boot considerably slower than 10.11 » 2017-09-21 10:20:21

Replies: 5

Not sure if anyone else has noticed this but ever since the introduction of 10.12 the netboot set that the DS Assistant makes takes a considerably longer time to boot to the workflow selection compared to a netboot set based on 10.11.
This trend seems to have continued to 10.13 as well, granted this is only the GM so things may change but i still feel it may be worth mentioning.

Is there anything in the pipeline that can fix this?

If it helps i could probably make a video of this.

Thanks in advance.

#3 Re: Usage » Fusion Drive Workflow not working on 1.6.17/1.6.18 10.11.1 NBi » 2016-04-08 13:42:48

Im running into the same issue now, it's stuck on blessing after the restore task on 1.7.3 the log file doesn't even update in the DS Admin panel due to the task not finishing.
The only thing i changed was the restore target to "/Volumes/Macintosh HD" due to the other options not working at all for fusion drive disks.

Reverting to 1.7.2 resolved the issue, having it boot the right volume after the restore task remains impossible on my end.
Blessing doesnt work, systemsetup is not available in DS.

#4 Re: Install » upgraded to DS1.7.2 now I am experiencing Repository access Error » 2016-02-25 10:27:38

Did you read the release notes of DS 1.7.X about upgrading from 1.6.X ?

– when upgrading from DSS v1.6.x, you will need to run the Assistant server setup to update the different configuration passwords (ex: repository sharepoint credentials, default Runtime login, …).

#5 Debug » [DS1.7.1/OSX10.11.3] Fusion Drive HDD replacement, Couldn't open disk. » 2016-02-10 11:53:59

Replies: 0

Not quite sure what went wrong here but we replaced the HDD in the fusion drive set up and ran our fusion drive workflow like we normally do.
After the Fusion Drive was made it couldn't find the disk, multiple times (not all of the logs seem to have persisted, im 100% sure it was the same error each time).

When the workflow failed after i checked and rechecked our workflow, i went into disk utility and erased the fusion drive that DS had made and after that the workflow ran without any problem.
Now you'd say that was likely the issue, but the fusion drive workflow should be doing the exact same.

The log can be found here (i omitted the useless error spam)
The important line is: 334

The workflow used can be found here:

Unfortunately the iMac in question is no longer in our lab so i hope this is enough for a report.

#6 Re: Future » Fusion Drive detection and workflow selection » 2016-02-08 12:29:18

Wow Erik,

I just read it and it looks solid, thank you very much!

Will implement this later this week, i really appreciate this :)

#7 Future » Fusion Drive detection and workflow selection » 2016-01-28 13:05:26

Replies: 5

Hi there,

Since FusionDrive Macs were released the footprint of these models was rather small, however, we're seeing an increase of FusionDrive Macs since the last half year or so.
At the moment DS has no built in way to tell the difference between a normal Mac and a FusionDrive Mac -unless- you check beforehand, the latter is something that seems hard to implement into the brains of my techs.
Most of them just select the normal workflow which results in DS breaking the FusionDrive and restoring OSX on the SSD, leaving the HDD unused, which is rather undesired.

What i'm suggesting is a workflow that can detect and possibly select the appropriate action to take or ask which action to take (or select the desired workflow based on the outcome)

I'd write my own plugin to do this but i really lack the knowledge to do this, which is unfortunate.

Tell me what you think, please :)

#8 Re: Usage » Problem when Imaging fusion drive » 2016-01-28 12:50:04

I don't have a solution but i've posted about this issue here:
It continues on page 2, waiting for a response from the admin.

#9 Re: Usage » Fusion Drive Workflow not working on 1.6.17/1.6.18 10.11.1 NBi » 2016-01-28 12:27:20

> admin wrote:

> @JonathanG: may you share the fusion drive and restore tasks logs?

Sure, i put it on pastebin.
Apologies for the wait.


Since 10.11 it does some weird stuff with the log, i'm sure you've seen it before.


If you're wondering what the scripts are doing: (it's useless as DS is setting it back to disk0 after finishing the workflow):

# Setting proper boot priority
bless -mount "/Volumes/Macintosh HD/" -setBoot

exit 0

# Enable OSX Language chooser
touch /var/db/.RunLanguageChooserToo

exit 0


# Check if fsck is running, if so, kill it.
kill $(ps aux | grep 'fsck_hfs' | awk '{print $2}')

exit 0

#10 Re: Usage » Fusion Drive Workflow not working on 1.6.17/1.6.18 10.11.1 NBi » 2015-12-29 15:11:51

Running 1.7.1. here and no issues with creating a fusiondrive.. BUT.. after it completes the workflow it always boots the recovery HD instead of the Macintosh HD.
I tried to fix this with a script but this doesn't work because even though "Set as Default startup volume" is unchecked deploystudio still does this at the (after the script) end of the Fusion workflow:
DeployStudio Runtime.bin[302:8664] /usr/sbin/bless --device /dev/disk0 --setBoot --verbose 2>&1

Even though disk0 is not the fusiondrive..

How would i go about resolving this?

#11 Debug » Changing the boot order after restore » 2015-06-16 15:23:37

Replies: 0


I've been struggling with a fusion drive workflow, i got it working to some extent where it works but it does not set the boot order properly.
After the restore it will set the default boot volume to the Recovery HD which is unfortunate but it does this exactly after a workflow is completed.

2015-06-16 16:09:07.030 DeployStudio Runtime.bin[394:23104] Task successful (elapsed time: 0.03 minutes)
2015-06-16 16:09:10.607 DeployStudio Runtime.bin[394:7287] /usr/sbin/bless --device /dev/disk0 --setBoot --verbose 2>&1

Now, a script to change the boot order is, in this case, useless as it will change the boot order after the workflow completes.
The option "Set as default startup volume" is unchecked, as you can see above it still sets the boot volume.

How do i circumvent this ?


#12 Re: Debug » Still Recovery Partition troubles on iMacs with Fusion Drive » 2014-12-16 08:12:44

> mjsanders wrote:

> What I did is using a recovery image from an image created after a clean install of 10.10.1, and duplicate this, and renamed it to match the name of the image created by AutoDMG , ending in ....recovery.dmg in stead of ....hfs.dmg
Do this only with exactely the same version os OS X!!

I'm not exactly sure how that would work ?

The AutoDMG image would still contain the recovery HD right ?

My issue is that an AutoDMG image (which contains the recovery HD) will not restore in a fusion drive workflow, it attempts to restore, but after restoration only the recovery HD shows up and the macintosh HD is not there.
Doesnt matter wether the option for the recovery HD is checked or not.

#13 Re: Debug » Still Recovery Partition troubles on iMacs with Fusion Drive » 2014-12-15 07:57:33

Fair enough.

The strange thing is, every non fusion drive recovery works with the autodmg images, also, about a year back i had fusion drive working with a recovery hd present in the image with no problems.

How should we set up a fusiondrive workflow and restore both the OS and Recovery HD ?

#14 Re: Debug » Still Recovery Partition troubles on iMacs with Fusion Drive » 2014-12-11 11:48:32

Having the same issue, i cant create a working fusion drive workflow.
our OS DMG's contain the recovery partition (made with AutoDMG)  checking restore the recovery partition makes the macintosh HD unbootable (doesnt show up in startup disks) and unchecking it will result in the same, only the recovery HD available.
Honestly i have no clue how to solve this.


#15 Re: Usage » Fusion Drive workflow » 2014-09-02 08:50:59

Thanks for that script, i was looking for something like it!

How do i apply it though?
You say Embedded workflow script, but i only see 'generic' which can call a script.
If i use Generic it will display in the log 'RuntimeSelectWorkflow: 0829B418-9DA5-453C-A697-6D2CAA8FC515' but nothing happens after that and i can select a new workflow.

Edit: ahhhh i figured it out, you need the 'Workflow' option and in there you can embed.. totally missed that one! it works now, thanks for the script!

Also, out of curiosity, can a script call an unpublished workflow ?
I wouldnt want to have extra workflows in my workflow list that confuse my normal users.

Board footer

Powered by FluxBB