Time Machine WD My Cloud issues

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
Just updated to MacOS Sierra (Public Beta 1), and now am unable to select my WD My Cloud as my time machine. It says its trying to connect then fails with "The operation couldn't be completed (OSStatus error 65.)

Anyone else had the same issue and manage to find a solution?

I've tried to use terminal to select the drive, but fails.

I can connect to any shares directly, so know it's not a problem with the drive

Edit: Just updated to PB 2 and still not working :mad:
 
Last edited:

Stuey3D

macrumors 6502
Jul 8, 2014
412
383
Northamptonshire, United Kingdom
Mine has just started doing this too, was working through Dev Beta 1 and Public Beta 1, but had to restore from a backup due to the broken iTunes update when Public Beta 2 installed and now it refuses to connect giving me the same error as you.

Also to note when I restored I had to use internet recovery and old fashioned Mavericks Time Machine app to restore the backup, Sierra recovery disk refused to connect to the backup.
 
  • Like
Reactions: ajsobay

grahamperrin

macrumors 601
Jun 8, 2007
4,946
627
Maybe there should be an update from Western Digital. Have either of you checked the support pages?

Maybe the Time Machine Server Requirements (Time Machine Network Interface Specification (TMNIS)) for releases of the operating system are no longer valid for pre-release Sierra. Defocusing from Time Machine: consider Apple's shift away from AFP to SMB.
 

Stuey3D

macrumors 6502
Jul 8, 2014
412
383
Northamptonshire, United Kingdom
Maybe but that wouldn't explain why it was working with dev beta 1 and public beta 1 and suddenly not now.

Also if Apple did change the standards like that then I can imagine a huge backlash from those of us who use 3rd party solutions for Time Machine of which I imagine there are many given that Time Capsules are hugely expensive.

Hoping its just a little glitch that will be fixed soon, I have submitted some feedback to Apple.
[doublepost=1469131131][/doublepost] Screen Shot 2016-07-21 at 20.57.06.png

Also it still sees the drive the problems come when trying to connect to it to use it.
 

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
Maybe but that wouldn't explain why it was working with dev beta 1 and public beta 1 and suddenly not now.

Also if Apple did change the standards like that then I can imagine a huge backlash from those of us who use 3rd party solutions for Time Machine of which I imagine there are many given that Time Capsules are hugely expensive.

Hoping its just a little glitch that will be fixed soon, I have submitted some feedback to Apple.
[doublepost=1469131131][/doublepost]View attachment 641247

Also it still sees the drive the problems come when trying to connect to it to use it.
I agree. It sees the drive not an issue as I can mount folders. The issue seems to be when it try's to connect, MacOS doesn't bring up the username/password dialog.

I've submitted feedback to apple too
 

MrGimper

macrumors 603
Sep 22, 2012
6,101
6,383
Andover, UK
I think something has changed in Time Machine on this beta.... My MBP has an encrypted disk and I just got a warning telling me Time Machine is backing up an encrypted disk to a non-encrypted disk (a time capsule). Never had this before.
 

576316

macrumors 601
May 19, 2011
4,062
2,477
My MyCloud device has never played well with Time Machine. I stopped using it because I'd get the 'You need to start a new Time Machine back up' error message every few weeks and I got sick of doing those huge initial back ups, it just wasn't worth it. I thought Apple's official word was that Time Machine doesn't officially support 3rd party network drives.
 
  • Like
Reactions: adib

grahamperrin

macrumors 601
Jun 8, 2007
4,946
627
I thought Apple's official word was that Time Machine doesn't officially support 3rd party network drives.
Nope.

It may help to consider these three points:
  1. Apple publishes a specification, and third party solutions may conform to that specification, but (seriously) not all equally conformant solutions are equally reliable
  2. Apple's implementation of its own specification, in products such as Time Capsule, may be more troublesome than third party implementations
  3. we should not expect Apple to support a third party solution that is not sold by Apple.
The combination of those three points may be understandably difficult for a customer to grasp/believe.
 

576316

macrumors 601
May 19, 2011
4,062
2,477
Nope.

It may help to consider these three points:
  1. Apple publishes a specification, and third party solutions may conform to that specification, but (seriously) not all equally conformant solutions are equally reliable
  2. Apple's implementation of its own specification, in products such as Time Capsule, may be more troublesome than third party implementations
  3. we should not expect Apple to support a third party solution that is not sold by Apple.
The combination of those three points may be understandably difficult for a customer to grasp/believe.
So are you agreeing with me or saying I'm wrong?
 

Stuey3D

macrumors 6502
Jul 8, 2014
412
383
Northamptonshire, United Kingdom
PB4 still hasn't fixed the issue :( looking less and less likely this will be fixed.
[doublepost=1470782317][/doublepost]Well OMG I've got it working, it took a bit of faffing about but its completing a backup now :)
[doublepost=1470782380][/doublepost]Connect to the drive in finder then go to time machine settings then it fails to connect but then lists 2 mycloud drives click the 2nd one and it then brings up the username and password dialog and then it connects and works as normal.
 

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
PB4 still hasn't fixed the issue :( looking less and less likely this will be fixed.
[doublepost=1470782317][/doublepost]Well OMG I've got it working, it took a bit of faffing about but its completing a backup now :)
[doublepost=1470782380][/doublepost]Connect to the drive in finder then go to time machine settings then it fails to connect but then lists 2 mycloud drives click the 2nd one and it then brings up the username and password dialog and then it connects and works as normal.
I shall upgrade and try later. Thanks for the tip. Still working ok?
 

Stuey3D

macrumors 6502
Jul 8, 2014
412
383
Northamptonshire, United Kingdom
Don't rely on that glitch i can't replicate it, the backup was taking forever as it was going slow it was able to find the old backup and continue from that but wasn't working well. I tried to remove the drive and re set it up again and now I can't get it to find the drive again.
[doublepost=1470849823][/doublepost]Ok I've just replicated the glitch, it seems to be a case of interacting with it enough in finder for time machine to give you the 2nd listing then you are able to log in as normal.
 

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
Don't rely on that glitch i can't replicate it, the backup was taking forever as it was going slow it was able to find the old backup and continue from that but wasn't working well. I tried to remove the drive and re set it up again and now I can't get it to find the drive again.
[doublepost=1470849823][/doublepost]Ok I've just replicated the glitch, it seems to be a case of interacting with it enough in finder for time machine to give you the 2nd listing then you are able to log in as normal.
Did you mount any shares or just connect to it in finder?
 

Stuey3D

macrumors 6502
Jul 8, 2014
412
383
Northamptonshire, United Kingdom
Yes mount the shares and have a look in them and then eventually the 2nd TimeMachine listing pops up.

However my MyCloud is on a major go slow I can't access anything on it so I'm getting rather concerned.
 

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
Has today's release of a new beta sorted the issue with initially setting up as time machine?
 

Jamie-30

macrumors member
Original poster
Oct 7, 2011
72
3
Yes mount the shares and have a look in them and then eventually the 2nd TimeMachine listing pops up.

However my MyCloud is on a major go slow I can't access anything on it so I'm getting rather concerned.
Have tried as you suggested and just cannot get it to work, mounted shares even the TM shares and still same error message