Mine is a MacBook Pro 6,2 model (mid-2010) Very surprising difference for the Recovery boot volume but some of that might be due to different install methods (mine was a clean install on a new external disk not an upgrade - what's the history of your Sierra upgrade? From what version before Sierra?) or different hardware models and who knows what else. I get 46276 lines for the "find" command, not 44462.
If it does or doesn't work suggest turning SIP back on with the "csrutil enable" in Recovery mode when you finish the test.Īfter updating to Sierra, Mac won't connect to ReadyNAS device This isn't a solution - just want to eliminate a possibility. Just for grins how about disabling SIP and seeing if all your SMB problems go away? You need to boot up in Recovery mode and issue the command "csrutil disable" (no quotes) in a Terminal window. I came across a couple of things about SMB problems when Sierra developer edition first came out last summer that talked about permissions differences with SIP that was causing problems - basically the permissions of the /Volumes folder had changed and writes were no longer allowed by anyone other than "root" without some hokey commands that had to be repeated frequently with a cron job. Just to be more clear - what is the "network drive" you're having problems with? Is it a NAS type device or a drive on another computer (Windows or Mac) or what? Could something have changed on it's end, like username or password or something else like it's IP or ? If it's a NAS device have you checked with vendor to see about if they know about any Sierra issues or have some suggestions?
0 kommentar(er)
