Skip to main content

Anyone had any issues creating a 10.9 net boot image? I ask because System Image Utility on any OS is refusing to accept my .dmg as a valid source.

Is your OS you are using to build the netboot (and run System Image utility) on Mavericks too?



To create a netboot set, the netboot image and the netboot creator OS need to be the same version. Been true since at least 10.4.x I'm afraid.



Hope that helps



Darren


Correct, run SIU on a 10.9 box and it works fine serving from linux or from Mac servers


Yes. Same OS version. It won't recognize the disk image.



Process is as follows:



Install OS X from fresh onto a computer
Customise for our particular needs. Similar to JAMF kb article.
Reboot to usb based recovery partition.
Capture with Disk Utility.
Reinstall OS X on the computer.
Prep image with System Image Utility. (this is where I get stuck).
Any other customizations and general image shrinkage.
Upload to test server and test.
Upload to main servers for out of hours syncing.


Here's an interesting article about NetBoot and Mavericks and some changes, some of them quite awesome. http://enterprisemac.bruienne.com/?p=208


^ thanks for that link!


Unless i'm doing something radically wrong here, 10.9 SIU doesn't accept self created DMGs anymore. Two clean installs, same issue.


You're not alone ... I'm having the same issue. Hopefully someone who has been successful with doing this in Mavericks will chime in!


I have just put a clean install in a mac mini, when I target disk the machine I only get firewire as a option to connect and not thunderbolt??? any answers as I can make an image in the first place. I have an identical mac mini with 10.8.5 and it's fine in thunderbolt


my process that i followed is as such.
I have a MBPR installed 10.9 customized, shut down and booted into target disk mode
connected to a 15"MBP via thunderbolt with a 10.9 seed installed
ran SIU saved the contents to the linux server
edited dhcpd.conf
netbooted all of my lab machines and they all booted just fine.


that seems fine but my puzzle is why do I not get the thunderbolt option when in target disk mode only firewire?


that seems fine but my puzzle is why do I not get the thunderbolt option when in target disk mode only firewire?


I don't have a mini so i cannot begin to guess why. do you have other hardware if so just start over on the new hardware. heck boot the mini normally, attach a USB drive and use CCC to backup the current running OS, then run SIU on the mini to make an image from the USB disk.


Hrm, my work colleague James may have found a way of doing it. It seems that it's possible to click "customize" button, then manually specify the mounted dmg. Has to be in the format of /Volumes/Macintosh HD 1


I have tried booting target disk mode (via thunderbolt) from my MBP to my iMAC (both running 10.9). My iMac sees the Macintosh HD, and I am even able to make an image of that through Disk Utility, and scan the image for restore. Regardless of which method I try to use (mounting the DMG created through Disk Utility, or accessing the MBP drive directly via target disk mode), SIU reads "No sources found".


Im not getting thunderbolt as an option to connect via on the mini, only firewire I am at mo doing it via booting up from USB and them Composer on the usb drive working as far


Im not getting thunderbolt as an option to connect via on the mini, only firewire I am at mo doing it via booting up from USB and them Composer on the usb drive working as far


The "customize" trick worked for me. Thanks for that tip!


Confirmed. The SIU in 10.9 is buggy and should be "customised" to make it work. Sigh.


We had a similar problem when trying to create a NetBoot set from a mounted thunderbolt drive. SIU wouldn't accept it as a valid source. Renaming the mounted volume worked for us (from "Macintosh HD" to "NetBoot" in our case).


Renamed the target volume to NetBoot (Suppose it doesn't matter what you call it) as swarby suggested and was able to get the utility to build the image without using "customise" option.


Renaming the volume to Netboot also worked for me. Thanks!


Rename fixed here too, cheers, odd.


I'm sorry but what do you mean by



"Has to be in the format of /Volumes/Macintosh HD 1"??


It has to be in that format with the spaces in the file path escaped by the character.


So I renamed the volume to NetBoot but yet I can still only use the mavericks.app installer as the source. How do you manually point it to a certain volume? If I hit customize, it still only sees the mavericks.app as a source. I guess I'm missing something.