I have two machines running OSX 10.11 beta 7 and neither will shut down and restart cleanly. I have to power them off then back on. One is a MacBook Pro (mid 2010), the other is a Mac Mini (late 2012).
Anyone else see this issue?
Thanks,
Charles
I have two machines running OSX 10.11 beta 7 and neither will shut down and restart cleanly. I have to power them off then back on. One is a MacBook Pro (mid 2010), the other is a Mac Mini (late 2012).
Anyone else see this issue?
Thanks,
Charles
Hi Charles,
Booting up in Verbose Mode (cmd + V) also causes a verbose shut down / restart to occur. This may provide a clue as to what is causing the hang.
Max.
happens on one mac here, but since this is a beta, I dont care much abut that state. The machine is sending bugreports already and and we see about it when we arrive at rc or gm.
Seems to be related to Finder connecting to another machine running beta 7. Cmd-V on shutdoen hangs after it displays "unmount of /home failed" and "unmount of /net failed".
If I never try to connect to a share on the other beta 7 machine, but connect to another machine running Mavericks, either beta 7 machine will shutdown normally.
Also, Finder will fail to reconnect in some cases to the other beta 7 machine after having connected and successfuly disconnected. The message "cannot connect because the original object cannot be found" is displayed. A relaunch of Finder fixes that issue.
Seems a lot needs fixing before this is released.
I did the SMC reset on all three machines (have added an iMac 5K to the group), and still have the issue of shutdown hanging with the spinning wait symbol if a connection and file transfer is made to another machine. Now running the GM on all machines, so this issue has not been addressed, it seems. A relaunch of Finder prior to shutdown seems to fix it almost every time, but I did not notice this issue until beta 7. I have filed a bug report, but no reply on that. At this point, I'd suspect there will be no changes made before general release.
Ideas anyone?
Charles.
This is still an issue with GM and 10.11.1 beta 1. Also, relauching Finder does NOT always fix the issue. Apple Development has asked for more information on this, so maybe they'll give it a serious look.