Tag: troubleshooting

  • AutoPkg failed: hdiutil: attach failed – no mountable file systems error

    If, when running AutoPkg, you get an error like failed: hdiutil: attach failed – no mountable file systems but you’re able to mount the .dmg manually (i.e., it’s not a corrupted download), double-check you don’t have a restrictions profile installed that requires you to authenticate when mounting disk images. That setting is pretty much useless…

  • If you update an AutoPkg parent recipe, but your override is still using old settings…

    AutoPkg has a cool feature called parent trust that allows you to create recipe overrides that store a hash of the parent recipe (instead of running the parent recipe directly), and then prevent you from running the recipe if there’s a change to the parent recipe, until you update the trust info. (I also have…

  • Force-stopping the MunkiStatus progress bar at the login window

    Sometimes, the MunkiStatus progress bar over the login window can get stuck, and pressing the Stop button can take a while to halt the progress bar completely. To kill it immediately, press Cmd-Option-Shift-Escape (this is a slight modification of the usual force-quite key combination, which is Cmd-Option-Escape). Full credit to Yehuda Bialik and Greg Neagle…

  • Fixing Jamf device signature error

    Even though this Jamf Nation thread is five years old, as of this writing, it’s still got the solution to the Device Signature Error – A valid device signature is required to perform the action error message. In my experience, the actual working solution is to run sudo jamf enroll -prompt and then enter credentials…

  • Fix for custom user icons freezing up System Preferences

    Even though there is some flexibility in terms of what sizes and resolutions you can use for custom user icons (to select for user pictures), if your icon’s resolution is way off, you may see a frozen blank, grey screen when trying to change the picture from that too-high-res picture to something else: To get…

  • Upping the logging level in Munki

    As noted in the Troubleshooting section of the Munki wiki, you can increase the logging level for Munki clients. The default logging level is 1, which looks like this: Dec 12 2019 20:04:20 -0800 GoogleChrome version 79.0.3945.79 (or newer) is already installed. If you increase the logging level to 4, it will look like this:…