Hello. Looking for some much needed help with my WD My Cloud (MacBook Big Sur M1 chip).
I recently tried to move to OS 5 My Cloud and completed the firmware update via the dashboard (wdmycloud.local) in the hope of being able to make use of My Cloud via Finder. Since the firmware update - which I hope successfully complete - I was able to complete the set up of os5.mycloud.com and was able to connect to My Cloud device fine. However since the device now shows as being offline and/or timeout. I can no longer access the dashboard either (using both wdmycloud.local and the device IP).
I have tried power cycles, 4 & 40 sec reset. The blue power light is solid.
I have read some posts regarding remote access port changes that could be configured on my router, however without being able to access the dashboard this seems pointless?
I am very confused as the My Cloud appears to be online as I have tested the device connectivity via terminal. A port scan of the device shows the following:
PORT STATE SERVICE
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
548/tcp open afp
2049/tcp open nfs
5357/tcp open wsdapi
8001/tcp open vcom-tunnel
8002/tcp open teradataordbms
49155/tcp open unknown
To add to this… I can see “wdmycloud” from Finder > Network. However when I try to connect it reports:
There was a problem connecting to the server “wdmycloud”.
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection and then try again.
Generally remote ports are not needed for local network access to the My Cloud. Generally if one is having trouble immediately after updating to OS5 then it’s likely the dreaded “indexing” issue that is the cause. The indexing immediately after OS5 installation can render the My Cloud inaccessible or very sluggish. There are several WD Knowledge Base ARticles dealing with the indexing issue:
Many more articles on other OS5 issues can be found here including a number of articles on things to try when one cannot access the My Cloud Dashboard:
Also one can try to access the My Cloud Dashboard by using the device’s IP address instead in their web browser. One may need to use a network scanner or access their local network router to see if the My Cloud Dashboard has been issued an IP address and what that address is.
One can attempt to do a 40 second reset which may fix some My Cloud issues however doing so may trigger a re-index of the unit causing the indexing issue.
Thanks Bennor. I will read through all the links you have suggested.
An update response I can provide now however:
Its important to check that one is using the correct name if attempting to access the My Cloud Dashboard by the My Cloud device name or default name. > My device name was never changed. I previously had no issues accessing the Dashboard using the default name.
Also one can try to access the My Cloud Dashboard by using the device’s IP address instead in their web browser. One may need to use a network scanner or access their local network router to see if the My Cloud Dashboard has been issued an IP address and what that address is. > I have done exactly this. I have confirmed the device IP on the LAN via nmap. I have interrogated this by scanning the device ports and that the host is up (results are in my original post). Using the IP I am still unable to access the Dashboard.
One can attempt to do a 40 second reset which may fix some My Cloud issues however doing so may trigger a re-index of the unit causing the indexing issue. > I have tried the 40 sec reset. the 40 sec reset doe not provoke any change to the blue light of the My Cloud; unlike the 4 sec reset which provoked flashing (as if resulting from a power cycle).
Hi Bennor. After reading through the articles you suggested I cannot find anything related to solving (Mac) Finder connectivity to My Cloud, and no connectivity to the Dashboard.
Other troubleshooting steps if they haven’t been tried yet.
Use another computer or device (non apple product too if possible) to see if the issue is confined to that one specific computer.
Connect the My Cloud directly to a computer that has a Ethernet port/adapter and see if it can be accessed directly.
One can always, if they haven’t done so already, open a support ticket with WD via the Support link at the top of the page. And see if WD Support has any workable suggestions.
If the problem is with indexing (and the device’s front LED is blue - single bay/single drive My Cloud model) then one may have to just leave the unit alone for a few hours to a few days to see if the indexing stops or finishes.
The unfortunate reality is that the upgrade to OS5 has not been smooth for a fair number of people as evidenced by the many threads about issues here in these OS5 subforums. Quite a few have had their devices rendered unusable or inaccessible.
In some cases as a last resort users have removed/extracted the hard drive from the My Cloud enclosure to recover their data (using Linux or third party Linux drivers). Some have attempt to push the OS3 firmware back onto the device. One can search for past discussions on how to “unbrick” and OS5 device and or roll back to the OS3 firmware. As always such methods or actions are done at the users own risk and are not supported or recommended by WD. One generally voids their device’s warranty when they extract the internal hard drive from it’s enclosure.
@MacDizzle If you can generate a logs please follow the KBA#18734 . If you are not please perform System Restore Only using the KBA# 29441, then generate a set of logs.
Meanwhile, please create a support case and attach the logs to it.
