Mavericks NetBoot Image won't boot (access denied symbol)?

I'm starting the process of creating some new NetBoot Images to support Mavericks and I'm having boot issues that I've never come across before (I've been building NetBoot images for years using using OS X 10.4–10.8). I always make sure to use the latest OS version available at the time to support our latest hardware (mainly iMacs and Mac minis).
Right now, I'm using a Mac mini (Late 2012) running OS X 19.9.3 (13D65) to build a Mavericks-based "Tool Kit" NetBoot Image (for drive recovery tasks, drive repairs, etc.). Using the same process I've always followed, I've installed/configured the Mavericks "Tool Kit" system (also OS X 19.9.3, build 13D65) itself on an external FireWire drive attached to the Mac mini, then run System Image Utility (10.9.3, build 677) from the Mac mini (internal drive) to then create the NetBoot Image (using the system on the external FireWire drive as the source).
Everything proceeds as normal, but when I load the image onto my NetBoot Server (OS X Snow Leopard Server, dedicated to NetBoot), client machines fail to boot off the image (they attempt the NetBoot, but get the "Access Denied" flashing symbol. Normally, I'd get this when trying to boot a system pre-installed with a newer version of the OS than exists in the NetBoot Image (or, when the hardware requires a hardware-specific OS version, which isn't what the NetBoot Image is running), but that's not the case here (as I'm able to successfully boot these same machines using my 10.8 "Tool Kit" NetBoot Image).
As well, I'm able to boot these machines from the Mavericks "Tool Kit" system via the FireWire drive directly. So, hardware is "capable" of booting the system I've built, but not when attempting to boot via my NetBoot Server.
So, I'm wondering if anything has changed with Mavericks that would result in Mavericks-based NetBoot Images not being able to boot from images served from Snow Leopard Server? Honestly, I don't think this is the case though, because I'm able to serve DeployStudio-created Mavericks-based NetBoot images (served from the NetBoot Service running on this Snow Leopard Server box) to these same machines, without issue. The the DeployStudio created image was built using the same "Tool Kit" system as a base for the image creation. So, it really doesn't seem like an issue with Snow Leopard Server nor the Mavericks base-system I've built to create the images—it seems like it's an issue with the images created via System Image Utility.
Anyway, I'll continue my trouble-shooting, but if anyone has any advice, it'd be greatly appreciated!
Thanks,
Kristin.

In this discussion it is said that 10.9.x does not NetBoot on certain models due to a microcode issue.
https://jamfnation.jamfsoftware.com/discussion.html?id=9836

Similar Messages

EFI Boot access denied symbol

Hello everyone,
my problem is the following:
i was installing windows with bootcamp,
after some time trying to boot, the mini showed me a flashing apple logo and an access denied symbol, i shutted the mini down after two hours on the boot screen,
i wanted to boot from firewire the mac os 10.6 dvd with a mac book (my mini has a broken dvd drive). how can i resolve the problem and at least boot the install dvd?
My mac mini specs
Mac mini intel core solo 1.5 ghz
2gb of 667mhx soddr2 ram
250 gb segate hard disk
wired alluminium keyboard and mighty mouse
no cd-dvd drive
help me, i need my mac mini back

Holding down the letter C on the keyboard when you turn on your Mac, should cause it to boot from an already inserted Optical disc that contains a compatible bootable operating system. If you turn on the Mac and then insert the Optical disc, it will not be recognised in time, so you will then need to reboot again with it still in.
You can also hold down the Option/Alt key and the Mac should then switch to displaying a list of all available bootable disks, including any optical disc.
In your case as you want to boot effectively from the MacBook, you could try one of the following two possibilities.
1. Put the installer disc in the MacBook, and make sure the MacBook has DVD/CD sharing enabled (in System Preferences)
2. Boot the Mac mini holding down the Option/Alt key and see if the MacBook disc is listed, obviously both machines have to be on the same network.
or
1. Boot the MacBook Pro in FireWire target disk mode by holding down the letter T when you turn it on (Some MacBook non Pro models do not have FireWire so it may not support this.)
2. Connect the MacBook via FireWire to the Mac mini
3. Turn on the Mac mini and hold down the Option/Alt key
You can do the reverse of the second method assuming your MacBook has FireWire. That is put the Mac mini in FireWire target disk mode, plug it in to the MacBook, and then run the installer on the MacBook. It is better however to do it the first way round as the installer will then know it is supposed to be configuring a Mac mini and not a MacBook.

10.6.7 netboot image won't unmount internal hdd in disk utility

I recently upgraded my snow leopard server from 10.6.6 to 10.6.7 in order to use the latest SIU to create some diagnostic images for the new MBP Early 2011. I can create the images just fine and can netboot the early 2011 MBP to the images, but when i try and use disk utility to repair the internal hard drive it says that it can't unmount the drive. Disk utility can unmount all external drives and repair them but not the internal drives.
My source machine is the early 2011 MBP and I placed the 10.6.7 OS on the internal hard drive. Once I made all the adjustments to my source machine, I put the source machine in target disk mode and connected it to my mac mini server via firewire 800. I used the default options for creating a netboot image in SUI. The image is created every time I try this but I can't get disk utility to unmount the internal hard drive for diagnostics. Any ideas?
Thanks,

Not sure if you've tried it on more than one client...
I've seen this occur when the HD on the client was corrupted. I had to boot from an install CD/DVD and use DU to erase the HD. Once I did that, the netinstall ran just fine.

3rd gen won't boot past apple symbol

My 3rd gen ipod won't boot up. It only display the Apple symbol, makes a few clicks and restarts, looping over and over. The computer does not register it because it hasn't fully booted up. Tried connecting it to both mac and pc. I cannot reset it or restore it.
Trouble started when ipod did not sync correctly.

My 3rd gen just did the same thing. I would guess it is toast. Anyone? I tried a reset, but no luck. I was hoping I could restore it, but it will not even be acknowledged by my computer

Netinstall Image Won't boot...

Hi,
I have succesfully created a 10.5.6 image in SIU from a pre-configured image of one of our iMacs. Set up the Netboot service OK, and when I got to Sys Prefs in any client machine and select Startup Disc, the image is shown in there as an option, however, when I select the option and try to reboot the machine, the client just sits with the Globe logo for a little while, and then reverts back to booting up from the internal HD. Is there some sort of log I can look at to see what is happening here?

This could be caused by a server misconfiguration, or by external forces.
Do a 'showmount -e' in the terminal on the server. Does the returned path properly reflect the location of the image(s)?
Another simple thing to try is: 'sudo killall -HUP bootpd'. This will force bootpd to re-read its configuration file.
You can also check to see that tftp is functioning properly. There is a walkthrough of the at Mike Bombich's site... http://www.bombich.com/mactips/netboot.html

OS X Mavericks installer on bootable USB boots with stop symbol

I've recently been trying to reinstall OS X Mavericks on my late 2010 Macbook Pro but I've ran into some problems.
I followed this guide to create a bootable USB to reinstall Mavericks. So first of all the copying took longer than it's meant to, which at first was a bit concering but I just continued. Then, once it had finished, I boot up from startup by holding 'alt' and selecting the drive. It boots up like it usally does, but then after around a minute it came up with a stop symbol and a spinner below. I've left it to load but nothing happens, I've rebooted and even tried to copy the files again.
It's not like this method dosen't work because I did it when Mavericks first came out and it worked without a hitch.
Any help would be appreciated very much. Thanks.

Eric Root wrote:
Make a bootable USB copy using the free program below. The program does all the work for you.
Bootable USB Flash Drive – Diskmaker X
What does it do if the dmg file is not on my comptuter?
Phil

Mac won't boot after prohibited symbol

I'd like to thank in advance anyone that will bother reading this. My guess is there is something wrong with the logic board...
I believe my macbook is the early 2011 13" model. kitted with the i7.
Here is a sequence of maybe relevant, maybe not, events that happened before the issue:
1- I run bootcamp quite often
2- I had been running my macbook on clamshell mode for about 2 weeks, connected to an external screen and keyboard&mouse
3- I installed a large amount of plugins for pro tools (10-15Gb worth) the day of the incident.
4- The last time i shut down the computer, i changed the boot disk to mac OSX, under the bootcamp menu in Windows' control panel.
5- When I booted up the next day the boot was going fine until the prohibited symbol appeared, replacing the apple logo.
5.1- After some time, the screen went light-blue (the snow leopard color thing) and the computer suspended itself. (it usually does that when i run it in clamshell mode, right after it finished booting, presumably because the lid is closed)
5.2- The computer was unresponsive to mouse and keyboard input, so i unplugged it and opened the lid.
5.3- It went to desktop, but rather than a mouse, i had a static colored wheel (which i could move). The dock didn't come up, and everything was frozen.
6- I long-pressed the power button to shut it down.
7- When turning it back on, all i can hear is that growly sound from the optical drive/hard drive (not really sure tbh), and the screen doesn't turn on. I can also hear the fans running, and the CPU area heats up.
On a sidenote, i don't hear the traditional apple chime ever since i had HDD data corruption problems and had to run system recovery into a more recent OS. After which i reinstalled a snow leopard (10.6.8) via a system backup i had, which dated from 2011 (and that was this year).
So, is there a magical key combination that will resuscitate my mac? Does this look like a 500€ fix on the logic board?
Thanks for reading!

Also, i don't hear any hard drive read/write activity, so i'm not quite sure if it's spinning.

Not Enough Free Space on NetBoot Image Partition

Since the NetBoot server isn't all that popular, I'm going to explain how it works a bit before I get into my problem.
I assume everyone knows how it works on the client end. You choose an image and your Mac boots that image over the network. Quick, easy, painless. It's a cool system. So on the server/admin side…
Every version of OS X Server comes with it's own System Imaging Utility. So lets say you want to make a netboot image with some utilities on it. So you take an external hard drive. Make two partitions on it. On one partition, you set it up to be the netboot image. So you install all of the utilities you want installed. You configure all of the preferences just the way you want them. Set your background image, etc, etc. On the other image, you just do a quick clean plain installation of your OS. And you also install your OS X Server Admin tools (or in case of 10.8, the Server app). So once your image-to-be is configured, you boot the second partition, and run the imaging utility. This utility will turn your volume into a netboot image. A netboot image is basically just a folder with some .plists in it, a read-only disk image of your initial volume, and a kernel or two (10.5).
NetBoot images are read-only. So when you boot them, you can make as many changes as you want. But once you shut down, all changes are lost. Every time any mac boots a netboot image, it is booting the image exactly as it was when you made it. The changes you make are stored in shadow files on the server that you can periodically toss, since they are only used during the current active session. Once you reboot, the shadow files are useless.
So here is the problem: When you make a netboot image from a real volume, the utility only leaves a small amount of free space on the volume. Even though the disk image is read only, the amount of free space matters because that's still all you get to use. In other words, if the .dmg file in the netboot image i just made only has 900 MB of free space in the volume, then that's all I get for free space on any machine I boot off that image. Even though the image is read only, and all of the "free space" is actually being stored as shadow files on the server, that limit is still applied. And 900 MB is not very much free space. So you can boot a utilities volume and if a program eats up a lot of ram, that virtual memory can eat up what little free HD space you have, and suddenly your netboot image is not very functional.
Now being the clever fellow that I am, I came up with a solution to this problem last time around. I used the following command to resize the partition (and only the partition) of the .dmg file, inside the netboot image (netboot images are just folders).
hdiutil resize -size 60g -partitiononly NetBoot.dmg
This resized the volumes to 60 GB. But it was all blank space, so the .dmg file's size did not change. It would just mount as a read only volume with 40 GB of free space instead of a few hundred MB. This little trick worked very well. But it's not working any more. I can't figure out why. But every time I try to run this command on the .dmg file, I get an error very similar to the following:
hdiutil: resize request 125829120 is above maximum size 18005952 allowed.
hdiutil: resize: failed. Invalid argument (22)
I get this error while running 10.8, 10.7, or 10.6. I get this error whether I'm trying to resize an image containing 10.8, 10.7, 10.6, 10.5, 10.4 or 10.3. I get this error whether I convert the image to a read/write image first, or even a spare image first. I get this error whether the original hard drive that volumes were on, is partitioned as APM or GUID.
The "maximum size" listed in the error message is different for each image I try to resize. It's as if the tool is trying to fit the increase volume inside the existing free space of the image's volume. Which isn't what I'm trying to do at all.
I've been using netboot images filled with utilities for years now. And overall it works very very well. I started back when the first macbooks came out with no firewire. I quickly realized I needed a better solution than booting my Mac into firewire mode to repair other Macs. And then when I got into it, I realized I could host images of all different OS versions. So now I can plug my MBP into a client's network, and boot any Mac they have off of a utility volume of any version of Mac OS X needed, all the way down to 10.3, all at the same time. And I also have NetInstall volumes too that let me install OS X for all these versions as well. The only real quirk I've had over the years, is this 'free' space issue. In the past (before the last time I updated my images, where I used the command above to resize the partitions and solve the problem), what I've done when I've ran into a HD pinch while working, is to immediately start deleting apps I don't think I'm going to need, right off the netbooted Mac. This frees up space on the netboot volume and the system is happy. And again it's all read only, so I'm not actually making changes to the image itself. One real half assed solution I thought of was to set up all of my netboot volumes as having a 1 GB file in their trash and not emptying it before creating a netboot image from the volume. Then when this problem came up and the OS was running out of disk space, I could just empty the trash. I'm quite sure this little trick would have worked, but it's so half-assed. I'd much rather just have more free space on the mounted disk images.

But how did my command work so perfectly last time? Here's an image. On the left, the info window of the disk image inside my 10.7 Utilities netboot image. On the right, the info window for that disk image's mounted volume. The file is only 7 GB and the volume is a 30 GB volume with ~23 GB free. None of the free space of the volume is using up any actual disk space in the .dmg file. I did this once, there's got to be a way to reproduce this again?
Here's the same thing with my 10.6 Utilities netboot image. Also in case I'm not being clear, these netboot images these screen shots are of, are from the last time I updated my netboot images ~11 months ago. These are not my current batch that I'm trying to finalize.

How to access old G5 Beige Tower that won't boot?

I own a couple of computers, a G5 Beige Tower and some early iMac I believe (come to think of it, now I can't picture what it looks like).
The G5 won't boot up—I haven't given it a try in years, but I refused to throw it away. I think it shows a flashing question mark inside of a macintosh icon.
I lugged that thing into an Apple store long ago and they managed to retrieve SOME files (they sure didn't try very hard, imo), so that tells me that I may still be able to access the hard drive, is this correct? Do I only need a boot drive somehow? I'm not sure if I even have one, floppy or CD.
The second computer was fried in an EMP. Lightning must've struck somewhere nearby (there was a huge storm at the time) and the craziest pulse of energy went through my body, I'll never forget it. It was like exploding in slow-motion, every particle in my body pushing outward, and when it was over, I was fine (shaken), but my computer was dead along with other electronic gizmos. Any opinions on if I should give up on this?
Would an Apple genius even know what to do if I took that computer in?
Both are old but may have some files from college that I'd love to recover.

Hi,
You mentioned a "G5 Beige Tower". The last beige Macintosh tower computer was a G3 model (http://support.apple.com/kb/sp406). Could it be this one instead?
If it is the G3 model in the technical specifications above, minimum Mac OS 8.0 would be needed for startup. This could be an appropriate/supported system CD. It could also be the Disk Tools PPC floppy that has been made available for download from Apple (you would then need a working older Mac with a built-in floppy drive and Disk Copy 6.3.3 in order to create a bootable floppy from the disk image):
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English -North_American/Macintosh/System/Mac_OS_8.1_Update/Disk_Tools_PPC.img.bin
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English -North_American/Macintosh/Utilities/Disk_Copy/Disk_Copy_6.3.3.smi.bin
A bad logic board battery can sometimes cause startup problems. You may also want to try a PRAM reset:
http://support.apple.com/kb/ht1379
Another possibility would be to remove the internal hard drive (the same could be tried with the iMac). An IDE/ATA drive can be connected to an external USB adapter (such as the example below) and then read on a more modern Mac (or even a PC with the correct software).
http://www.newertech.com/products/usb3_universaldriveadap.php
If necessary, disassembly guides can be found, for example, at ifixit.com.
Jan

Mac mini 2009 mavericks won't boot. Blank display no logo,etc. Tried all keyboard boot functions, no help. replaced RAM w/known good. No help. Removed HD mounted in external enclosure and ran permissions and repair. No help. Upgraded HD to Yosemite a

Mac mini 2009 Mavericks won't boot. Chimes and power light comes on. USB ports have power. Blank display no logo,etc. Tried all keyboard boot functions, no help. Replaced RAM w/known good. No help. Removed HD and mounted in external enclosure and ran permissions and repair. No help. Upgraded HD to Yosemite and was able to boot another mini from HD mounted in external enclosure, reinstalled HD still no boot. Any ideas on how to proceed appreciated.

- Make an appointment at the Genius Bar of an Apple store. You have a hardware problem.
Apple Retail Store - Genius Bar

Mdworker deny mach-lookup. But macbook won't boot in safe mode

I have a common problem, I get theese messages every now and then in console:
2/8/13 6:38:24.000 PM kernel[0]: Sandbox: sandboxd(793) deny mach-lookup com.apple.coresymbolicationd
2/8/13 6:38:24.534 PM sandboxd[793]: ([791]) mdworker(791) deny mach-lookup com.apple.ls.boxd
2/8/13 6:38:24.556 PM sandboxd[793]: ([792]) mdworker(792) deny mach-lookup com.apple.ls.boxd
There is a solution, which should resolve it, like here https://discussions.apple.com/message/19750564?searchText=mach-lookup%20com.appl e.ls.boxd#19750564
I have just boot in safe mode. (holding Shift during boot)
but my macbook won't boot in Safe mode. It just freeses with a grey screen for hours and wont boot.
I tried to leave it overnight to boot, but it didn't.
Please help me make my macbook to boot in SafeMode.
my configuration is the following:
MacBookPro8,1
OSX 10.8.2

There is a bug in fsck_hfs that is affecting a bunch of people. Basically as your comptuer starts in safe mode, it runs a file system check (fsck) against your hard drive, it gets to a certain point and... just sits there. No one knows why outside of apple.
Lots of info here, including a way to get around it by tricking the system to think fsck had been run, though the fsck will not be complete so it is not a good solution.
https://discussions.apple.com/message/21389737?ac_cid=tw123456#21389737

My Macbook won't boot up because there isn't enough free space for my start up disk. It's now stuck on a blue screen. How am I meant to delete files to free up space if I can't access the computer?

My Macbook won't boot up because there sin't enough free space to run the startup disk. My Macbook now won't go past the blue screen so exactly how am I meant to be able to delete files if I can't access the computer?

Do you have a bootable backup?
What operating system are you running? If OS X 10.6 or lower, boot from your original OS X DVD or a retail OS X DVD and then delete files as needed. Your goal should be to get to 10% of your disk capacity free.
If you have OS X 10.7 Lion or 10.8 Mountain Lion, you don't have many choices in recovery mode (boot holding the command and r keys down).
If you have a FireWire or Thunderbolt connection, you can try target disk mode with another mac.
If none of those work, perhaps your local Apple store can help with a bootable external drive.

I'm having trouble with my computer, I boot it up and within a few minutes it freezes and I have to restart it, I tried updating it to the latest mavericks but it won't finish the installation it's stuck at the end, what can I do to fix this?

As stated I'm having trouble with my computer, I boot it up and within a few minutes it freezes and I have to restart it, I tried updating it to the latest mavericks but it won't finish the installation it's stuck at the end, what can I do to fix this? I need it for homework tonight.

Crowntheme,
you can try this: boot your MacBook Pro into Recovery mode by holding down a Command key and the R key as it starts up. Once the Mac OS X Utilities menu appears, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk’s boot partition (typically called “Macintosh HD”). On the right-hand side, press the Verify Disk button if it’s not greyed out; if it is greyed out, or if it reports that errors were found, press the Repair Disk button. Once the verification/repair is completed, exit Disk Utility and select Restart from the Apple menu to restart in normal mode. Does it still freeze after a few minutes?

Mac mini won't boot after latest update Maverick

My Mac mini running Maverick after an automatic update won't boot. " no bootable device -- insert boot disk and press any key"
What option do I have here?

Reinstall Mountain Lion or Mavericks
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is
three times faster than wireless.

I have a RAM problem,, my Mavericks won't boot

My 2009 iMac desktop won't boot up. It starts to, but once the apple icon appears, it shuts down after about 20 seconds. Sometimes, instead of shutting down, it sends out alarm bursts in sets of 3 beeps at a time. Obviously I have no start-up disk for Mavericks, but I do have my old Snow Leopard disk. What can I do to restore it? I already removed the RAM, shot some compressed air over the cards and into the slots to clean out the dust but I still have the same problem.

Your RAM is failing or you might be able to clean it using a soft cloth.
Startup Tones

Mavericks NetBoot Image won't boot (access denied symbol)?

Similar Messages

Maybe you are looking for