You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

maplevshoney Author

Level 1

46 points

Computers Won't Shut Down After Connecting To Server

Hello Geniuses,

I am having a strange issue and I know it's not going to be easy to diagnose but let's give it a shot. I have two iMacs in my studio, a 4k and a 5k, both with El Capitan 10.11.2, and both connected to an ethernet network and talking to a server on a Mac Mini (latest OS and OS X Server).

I mention the server because I think it may be relevant, but that's just a guess.

Basically both of these computer have a strange inability to shut down. You choose Shut Down and they go through the motions all the way to the black screen with the spinning cogwheel, and then it just lingers there. Forever. Well, at least for 24 hours because that's the longest it went unnoticed once. Typically I wait a few minutes and then do a force shutdown. (I wait a few minutes because sometimes, not very often, but sometimes, the computers will successfully shut down.)

Both machines are wired to the server and frequently use fire sharing (SMB and AFP) to load files off of networked drives. Again, I mention this because this is the common thread between these machines that seems to be the outlier from typical usage, and I'm wondering if the connection to the server is the process that keeps the computers from shutting down properly.

If anyone can help point me in the right direction that would be awesome.

Thanks!

iMac (Retina 5K, 27-inch, Late 2015), OS X El Capitan (10.11.2), null

Posted on Jan 6, 2016 11:53 PM

28 replies

Dimme

Level 2

291 points

Jun 4, 2016 4:00 PM in response to luckman212

I have this problem with my macs and mac mini server. Turning off SMB is not a option for me because I have other os's on the network. For now I am just unmounting my drives before shutdown,

Jun 4, 2016 4:31 PM in response to Dimme

There are times that unmounting from the client still doesn't work and shutdowns fail. If the computer goes to sleep, then awake, then unmount, it seems to work fine. Or, I can unmount that client from the server software and then shutdown always works too.

Jun 28, 2016 6:42 PM in response to brycesteiner

This is a common issue and have more than two medium size companies where this is occurring. I was having issues shutting down without connection to the server and solved these by fixing permission in Mac HD/System/Cache, by forcing apply to enclosed items,

Jun 29, 2016 4:07 AM in response to Geniecommands

Not that repair permissions has been removed (unless booting into safe mode, which my Mac won't do for some reason), how do you fix permissions in that folder alone?

Thanks!

Jun 29, 2016 5:49 PM in response to Geniecommands

Turning off SMB fixed shut down delays thank you, hoping one day that SMB will be fixed but it has such a controversial history on Mac for so many years that I am not surprised this was the culprit. Also managed to solve permission issues but this maybe because I setup an new permission group rather than use the built in group Staff.

Jun 29, 2016 5:58 PM in response to brycesteiner

I used the common (command i ) on the Systems/Cache folder, then click the arrow next to Sharing & Permissions.

Unlocked the padlock bottom right with password.

Then used the gear icon and selected "Apple to enclosed items.." in the pop up

Cant remember if this was before update to El Cap but update still did not fix shut down after opening files on server.

Turning off SMB on server fixed shut down issues and I did not see a file list slow down as I have caching on in Server.app 5.1.5

ps. I still use Onyx third part tool for osx and El Cap, as this still does a permissions fix.

Jul 31, 2016 2:13 PM in response to maplevshoney

I have pointed Apple to this thread for further evidence that this is a real issue. Received nothing but canned responses marking it as a "duplicate". I filed the first report of this bug in NOVEMBER 2015, under 10.11.1 and I find it totally unacceptable that there have been FIVE OS X updates and NINE months gone by and not even so much as an acknowledgement of this serious bug.

Quality control has really suffered since the loss of Steve. RIP Steve. I hope Apple gets their s--t together soon.

Jul 31, 2016 2:40 PM in response to luckman212

I posted my original bugreport to OpenRadar, in case anyone else filing reports wants to link to it etc.

http://www.openradar.me/23684301

It would be really nice if whoever filed bugreport #19742550 could post to OpenRadar as well, since mine was marked as a duplicate of that bug.

Jul 31, 2016 4:43 PM in response to luckman212

Thanks for posting that open radar link. This is still a serious issue and Apple needs to get it fixed since we are being forced away from AFP. I'm still not sure if it's client or server and it doesn't really matter. It's a fix that would probably take less than two lines of code.

Manually drop the client from the server software and the computer will then shutdown.

It's the same issue that causes the spinning beachball of death in Finder.

Aug 2, 2016 6:03 AM in response to luckman212

Well Apple Support closed my original case #23684301. They said it was "too old" and asked me to file a fresh one. Which I have done, new case #27656700. Just keeping notes here. Also created a new openradar so it can be publicly tracked- http://www.openradar.me/27656700

Aug 2, 2016 10:35 AM in response to luckman212

I read your report and that looks very identical to my experiences.

I see things that might bring this together that match my experiences causing the non-stop shutdown/reboot:

1. it must be a admin user on the client and remote machine and logged in with a mounted share.

2. It must be SMB 3 (Apple's implementation)

3. Remote machine must be a Mac running El Capitan 10.11.x (I think the client is too)

I can get it to reboot every time IF I disconnect the user from the server. Disconnecting or unmounting from the client computer does not work consistently allowing successful reboot. I've noticed that, for me anyway, it does not have to be a root drive.

Thanks for the update!

El Cap

Level 1

8 points

Oct 3, 2016 10:01 AM in response to maplevshoney

I have what sounds like a nearly identical setup (2 iMacs connecting to a Mini). I experienced the shut-down problem in both El Capitan and then Sierra - always and only after accessing the Mini from my iMac. After disabling smb connection (leaving afp), the problem went away and my iMac now shuts down correctly (restarts correctly as well).

Thanks for the tip.

Celeblue

Level 1

8 points

Feb 3, 2018 1:21 AM in response to Celeblue

Spell checking and auto-replacing is sometime annoying! Please replace "disunited" above with "distnoted".

Computers Won't Shut Down After Connecting To Server