I'm following [How to create a bootable installer for macOS](https://support.apple.com/en-us/HT201372) guide by Apple, but it's giving me an error. When I execute sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/disco It gives me this: dyld: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD Referenced from: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia Reason: no suitable image found. Did find: /Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x103C4F000, size=0x00006000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD /Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD: mmap() error 1 at address=0x103C65000, size=0x00006000 segment=__TEXT in Segment::map() mapping /Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD ADMINs-MBP-2:~ ADMIN$ I'm using OS X Yosemite 10.10.5 on a Macbook Pro 2015. The USB device is a 1TB External Hard Drive, Mac OS Extended formatted.

I'm asking for the opposite of https://apple.stackexchange.com/q/98416 , which requests a way to ensure that unkillable processes are eventually SIGKILL'd [\[3\]] (like SystemD's TimeoutSec ). To compare: 1. On NT-based Windows 11, sudo shutdown /r /fw /t 0 (yes, that's Windows sudo) is the sole official way to reboot to the EFI UI. This invokes the standard shutdown method (that its DotNet APIs would). 1. However, on Linux-based OSes, multiple methods may exist. As an example: 1. All include reboot, alongside their initialisation system's method (SystemD's systemctl reboot --firmware-setup [\[1\]] or OpenRC's loginctl reboot --firmware-setup, [\[2\]] etcetera). 1. However, KDE advises busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager SetRebootToFirmwareSetup b true && qdbus-qt6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logoutAndReboot, so that the DE gracefully shuts down its first-party applications. I'm aware that Apple, on its own platforms, tends to design its applications differently to 3rd-parties, and OS design frequently necessitates this. Consequently, is macOS like Windows, in that it solely exposes one way to shut down the OS via the CLI, or does a more graceful manner (that SIGTERMs) exist than merely reboot? [\[1\]]: https://superuser.com/revisions/1083166/1#content:~:text=setup%20menu%20using:-,systemctl%20reboot%20%2D%2Dfirmware%2Dsetup,-Documentation:%20https://www.freedesktop.org/software/systemd/man/systemctl.html%23%2D%2Dfirmware%2Dsetup [\[2\]]: https://github.com/OpenRC/openrc/issues/539#issuecomment-2203036622:~:text=OpenRC%20uses%20elogind:-,loginctl%20reboot%20%2D%2Dfirmware%2Dsetup,-so%20I%20shall [\[3\]]: https://stackoverflow.com/revisions/690631/6#:~:text=SIGKILL%20is%20used%20to%20forcefully%20remove%20the%20process%20from%20the%20kernel.%20It%20is%20special%20in%20the%20sense%20that%20it 's%20not%20actually%20a%20signal%20to%20the%20process%20but%20rather%20gets%20interpreted%20by%20the%20kernel%20directly.

I have a Mac Mini, M1, which I use remotely via SSH / VNC. From time to time I need to issues a reboot to the machine. After rebooting however, I am unable to establish an SSH connection as all I get are 'Connection Refused' packets. It seems that machine does not actually finish the boot process until first login; only after entering my password on the local machine does it start accepting SSH connections. How can I make the Mac actually finish booting without someone physically at the machine?

Apple Mail, the OS bluetooth subsystem and some other applications (e.g. Fantastical and Things app) loose relevant (but not all) configuration and preferences on nearly every reboot. For Apple Mail it seems that all lost settings are stored in the file ~/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.mail.plist. I haven't yet identified the other affected files. It does not happen if I hunt for it (keep rebooting), but only after using the Mac for a while. I currently run macOS 10.15.6 on a MacBook Pro 16" with only a few popular Apps from the App Store plus Microsoft Office. I am a long term Mac user. The bad behavior started approximately 2 years ago after an update to macOS High Sierra (I think). The Mac became more a more unusable because of this and other strange bugs (it also started to become extremely slow, so I had to reboot regularly, loosing all settings afterwards). Repairing and even installing the OS did not help. Therefore, I got a new Mac and installed everything from scratch (no restore from a backup) and installed only very little software on the system. However, the preferences still get lost on nearly every reboot! What could cause the file contents to be lost on nearly every reboot?

I've had this issue intermittently over the last ~month or two where I'll be doing something on Chrome on my laptop and it will suddenly restart; usually the screen freezes, the audio repeats its last beat a handful of times, and then it goes through the rebooting process. The only known issue is that I have way too many Chrome tabs, but I also use a plugin to keep them from using too much memory (The Great Suspender). Does anyone know what is causing this and what I can do to stop it from happening going forward? The main concern is that it might reboot while I'm in the middle of an important video call (which thankfully hasn't happened yet). If it would be of assistance and if it doesn't contain any identifying information, I could post the problem report (the message is all Greek to me and very long so I don't know if it's okay to post or not).

I have a 13" M1 MacBook Pro (2020). Recently it has been restarting immediately after logging in and showing a popup stating "Authentication is required to verify startup disk". After entering my password, the Mac boots to the login screen, I login, the computer works fine for a minute or two, then immediately restarts again. I took it to the Apple Store. They ran diagnostics but couldn't find any hardware issues. They helped me erase my SSD and reinstall MacOS - it worked fine for an hour or two of active use. But now the restarting loop is back as I described earlier. I've tried running first aid through disk utility but everything seems normal. Could it just be a hardware issue still? Has anyone ever encountered this issue? EDIT: The problem seems to be related to disk I/O. My mac seemed to work fine after not using it for a couple hours - however as soon as I tried downloading some large data the computer restarted. I was curious about this so I wrote (i.e. asked ChatGPT to write) a Python script which spawns a couple processes and writes to /tmp. Whenever I run that script, the Mac will reboot by itself.

I want my Mac to be remotely accessible even after rebooting. This is prevented by FileVault and one needs to physically login first after the reboot. One can solve this by the command line fdesetup authrestart. However, this is only useful for an immediate restart. I want instead the restart pmset scheduled. For instance, I set pmset relative poweron 25000 and then remotely shut down the machine. 25000s later, it restarts but runs back to the FileVault problem. Any workaround besides turning FileVault off?

Two years ago I had to buy a new iPhone and since I am in area where iPhones are very expensive and hard to get I actually bought two devices -- iPhone Mini 13. Both of them were configured in the same way and one was stashed away in a water and dustproof bag as a backup, the other has been in use ever since. The main iPhone has now stopped working. When trying to activate the backup it does not start. The Apple logo sometimes flashed quickly but I cannot get it to force restart using the volume up, volume down, long press side button routine. Now I am wondering if the long time without use might have discharged the battery to a state that's unusable? Any tips greatly appreciated. *A quick update:* After a lot of different tries to get the device to boot it at some point showed the computer connect icon and my mac did recognize it and offered an "update" to restore the device. While downloading that update however the phone shut down again at some point and went into the short boot loop again.

I have this strange problem of my Mac rebooting. Everything was normal until I started syncing photos from iCloud (this could be coincidental, maybe not). First time I noticed a problem after 1-2 days as my system fan started going crazy, with CPU utilization at a max, several minutes later followed by system shut down. I traced the 100% CPU to Spotlight reindexing constantly; I temporarily disabled indexing: sudo mdutil -a -i off Problems with fans went away, but now photos service was going at very high CPU, accelerating fans again. I disabled Photos app (as much as I knew how) to avoid performing any analysis. This solved the fans and CPU going crazy problem. I could live without Photos on this Mac, no problems here. Photos/Spotlight searching might just be coincidental, this part I'm not sure. Just so my system was more or less stable for at least several month before this addition. But, **here's the problem**: As soon as I leave my computer alone, after several minutes of inactivity, something happens that my computer goes into sudden reboot. I can't even leave it for 5 min for bathroom break. For information: putting computer to sleep was always disabled on my Mac, only screen saver and later on monitors were to trigger. Now I disabled it all, with no difference. I tried: 'caffeinate' with no difference as well. Also, working on my Mac, performing various tasks has no effect whatsoever, but leaving it idle, goes to reboot soon. Please help. What I was trying to find is if there's some kind of log that I could dump of a system on freeze, some entry to trace of what was the final activity before my Mac reboots. Any idea?

I am aware of the [authenticated restart](https://superuser.com/a/1024694/493903) when using FileVault 2 on OS X. Running the fdesetup authrestart command does however restart the system immediately. Now, when running the OS X Update from the App Store (which often requires restarting the system) the update process reboots the system automatically at "its own convenience". It prompts about the restart requirement before starting the whole update process and there is no "you should reboot now"-point in time. Is there any way to "combine" OS X Update from the App Store with authenticated restart so that a remote system with system drive would not require manual drive unlocking from the console?

I have been dealing with an issue for a few months now and I have debugged it enough to be pretty confident that I know the cause. - The problem: Occasionally, my 8am personal automation does not run. - 1st clue: When this happens, there's always a notification on the lock screen that says something like "Automations will run once iPhone is unlocked" - 1st order reason: The phone rebooted. Any automations that would happen between shutdown and the next unlock will not run. This is how the iPhone is designed to behave. Once I realized that the iPhone was unexpectedly shutting down overnight, maybe once or twice a week (and only overnight), I started debugging to figure out why that was happening. The next time it happened, I noted that the battery health graph showed the pause symbol under it, and an absence of battery bars suggested that the iPhone was shutting down around 3am when the battery is charged to between 80 and 100%. I checked this for multiple occurrences. I learned that this *could possibly* be due to optimized charging, so I turned optimized charging off - but the problem persisted. After speaking with Apple Support, I was informed that this shutdown (during AI-learned periods of inactivity) is also designed behavior after the battery has reached a certain level of "degraded performance". In my case, the max capacity is 83% and has been through over 500 charge cycles. I have a reason^ for not wanting to replace the battery, so my question is: How do I prevent the AI from shutting down my phone overnight? My first hunch is perhaps a personal automation that disrupts the pattern the AI has discerned about my usage. **Footnote:** ^ *I'm satisfied with current battery performance and I feel like the phone has a reasonable amount of life left. I only have empirical evidence to support this (i.e. I don't know what actually goes into the max capacity calculation), but I suspect that the max capacity estimate is based (at least partially) on battery drain behavior and that that is artificially poor due to a problem immediately apparent after update to iOS 16. The phone occasionally gets hot and when this happens, whatever it's doing tanks the battery in under an hour. I suspect that there is an errant process/state, possibly due to an app or 2 that needs an update to be better compatible with iOS 16 (which I have discerned through my interactions online with others who have experience this issue and from discussions with Apple Support about the hotness issue). If I do nothing once the hotness starts, the phone will drain its battery and become extremely hot, and be dead in under an hour. But if I reboot the phone, it cools down and lasts for hours longer. In short, I believe this is primarily a software issue, and this behavior makes the battery graph look like the battery is in poorer health than it really is. No doubt, the battery has seen better days and could be "solved" by a battery replacement, but if I reboot the phone when these "hot flashes" occur (maybe once a week or so), the overall battery performance is pretty good, TBH. No significant complaints - minor just annoyances.*

Occasionally I get the message about TouchID needing my password after reboot on an iPhone 5s running iOS 8. Problem is, I haven't been rebooting my phone, so the message is confusing to me. So I'm concerned my phone is rebooting itself in my pocket without me knowing it. I want to know for sure if my phone is rebooting by itself, or if the TouchID message is just erroneous. How can I find out if my phone is rebooting by inspecting the logs for power off / power on events?

I started a remote reboot of my machine but a couple of *stuck* processes are hanging the reboot. - login with SSH is still possible - sudo reboot or sudo shutdown -r hang - two processes are *trying to exit* USER PID PPID PGID SESS JOBC STAT TT TIME COMMAND root 43 1 43 0 0 ?Es ?? 0:00.00 (mds) corti 407 376 407 0 1 ?E ?? 0:00.00 (talagent) - I did not manage to kill them (i.e., sudo kill -9 43 or sudo kill -9 407 have not effect) - A remote desktop session is no more possible (last screen that I got was a gray screen with the wheel while shutting down) - Trying to reboot without flushing the caches does also hang (any combination of -n and -q) Any other things I could try other than going home and physically reboot the machine?

I tried to reinstall my Macbook, so I rebooted it into recovery mode and cleared my disk. I then rebooted, at which point it prompted me to connect to Wi-Fi for "Remote Recovery". I've been trying for hours, but no matter what I do, it will spin for a while then exit with an error. I've tried every boot keyboard shortcut in the book for alternative recovery modes, but it always boots into remote recovery mode. Connecting an Ethernet cable doesn't work, it still just prompts me to connect over WiFi. Other people with this issue recommended setting DNS servers to 8.8.8.8, with guides for how to do this on the Macbook, which makes no ****ing sense when I'm stuck in remote recovery mode. I updated my router to use 8.8.8.8 but it made no difference. Worse yet, it's not possible to power off my Macbook. If I shut it down by holding the power button, it turns itself back on after a few seconds, no matter if the lid is down and I'm not connected to power. And to make things better, it's running hot as hell, to the point where I almost can't touch the touch bar. I am actually losing my &#(/"%#ing mind here. What do I do. --- I believe it's the latest generation of Macbook Pro with touch bar before the M1 chip came out, so it's an Intel machine.

I need the boot manager at startup every time. I have a 2014 mini with 2 bootable partitions. Yosemite on one and Catalina on the other. Obviously, need to run legacy software. When running Yosemite, the Catalina drive doesn't mount. So it can't be selected as the boot disk from within Yosemite. The wireless keyboard doesn't interrupt the boot sequence for keyboard shortcuts to work. Haven't found a third party boot manager to work in this setup and a wired keyboard doesn't suit the workspace. I have the "sudo nvram manufacturing-enter-picker=true" saved to a text file. Too much to explain to the user,"open terminal, cut, paste, etc." It would seem that this would just be a line written into a file but which, where, how?

I opened my Macbook Pro to discover it was off, I pressed the power button and it had the AHH and the apple symbol and loading bar. However, the screen is covered in alternating bars of pink and blue. After the loading bar was almost full, the mac suddenly went to a very dark blue (but not black) screen. After 30 seconds, there is a power off click and the screen goes black for a few seconds before rebooting again. It is trapped in an infinite loop. I reset NVRAM, SMC, no effect. I shut it down to stop the loop, but the loop just restarts. Booting to safe mode breaks the loop... by taking me to a blank white screen until I shutdown. Booting to recovery mode simply traps me on the loading screen, but there is no loading bar or apple logo, just an eternal circle with a line through it. Please help. I tried booting to Verbrose Mode, here is a video. After the text stopped, the screen turned solid gray and the text disappeared, and a few minutes later it rebooted again back into the loop. https://streamable.com/e/m4xuku I used option D to run a test, it found nothing wrong.

For example, I often end up with a situation were I'm logged in over Apple Remote Desktop (Teamviewer etc.) and the computer crashes...ARD says reconnecting, but doesn't... However, I can nearly always still access the computer via SSH. But what often happens is, even after logging in and sending shutdown -r now or sudo reboot, it still doesn't reboot. It just ends up hanging... Things not being saved etc. etc. isn't relevant, I just want to bring the computer back up...so the closest command to just physically power cycling it basically? What about some of the options here: https://ss64.com/osx/reboot.html sudo reboot -lnq maybe? or here: https://ss64.com/osx/shutdown.html sudo shutdown -r now -k maybe? Something else?!? Thanks for any help/thoughts! P.S. I do have a failsafe, I can power cycle it with a smart plug...and that nearly always works...but I'd prefer not to have to rely on that so often. And then I have another failsafe for that, i.e. if "Start up automatically after a power failure" doesn't work (sometimes it doesn't), I have this set up to turn the computer on every hour: https://www.dssw.co.uk/powermanager ...just thought I'd add those for anyone who is interested...they'd saved me many a trip...

Have had some problems from time to time on macOS 12.x where it hangs indefinitely. I'm working with Apple engineers on a resolution, but I'd like to figure out how to set up a method to send the equivalent of a sudo reboot to the kernel via a crazy key combination so that when apps and everything hang for hours on end I can break out of the situation more safely than just holding in the power button. Anyone see such a trick that still works for macOS 12?

My Macbook Pro 2020 cannot be turned off. If I shut it down normally, smoothly, it will reboot 5 seconds after being off. Even if I hold the power button for 10 seconds, it shuts down but immediately reboots. The only solution I found is to wait until the battery is dead but it's not really a viable solution. Do you see any other way I can turn this computer off? Do you have any idea what could force the reboot of the laptop?

I'm using Mac OS Catalina 10.15.7 and I'd like to open some apps after boot with a cron tab. I use the following cron tab: @reboot /bin/bash /Users/x/script.sh if I run the script, it works as I want to, but cron executions fails with the following error: LSOpenURLsWithRole() failed with error -610 for the file ... because, as noted in this answer , GUI apps can't be run before an user is logged to the GUI. Is there anything I can do? I was thinking about the possibility of a keyword that ran after login, not after boot. How may I achieve this?