A couple of years ago I purchased a WD My Cloud 2 TB. Due to a change of plans and our moving to a new house, this My Cloud 2 TB drive has never been used, so new out of the box.
Today 2025-02-04, I’d like to start using it and see to what use I can make it.
So here’s what I did:
connected to network
plugged in power
Indeed after a while the white led was constantly on, so I wanted to go the next step: connect to mycloud.com, set up an account and enter the 9-digit code to find my My Cloud drive.
The drive was not found, and the code was not accepted. I then started searching internet, learned that the code is also on the label on the bottom of the drive, indeed, the code was the same as on the card.
Further searching revealed two reset modes, I went for the 40 second reset. So unplugged power, waited for a couple of minutes, then pressed the reset with a pin, then while keeping the reset pressed, plugged the drive in to power and held for at least 40 seconds.
Now the drive is still connected and already bravely flashing for approx. 2 hours, but the white led will only flash…
I can see the drive is present on my network, but I can not seem to log into it?
What am I doing wrong?
Has support for these WD My Cloud drives stopped?
Ok, small update…
After approx 2 hours of waiting while the white led was flashing, I again unplugged the power and rebooted…
This time the white led is blinking, but in a very slow rythm…
You should refer your device as the My Cloud Home or MCH to avoid confusion with the other ‘My Cloud’ OS3 and OS5 series of devices as they are completely different in hardware and software.
Your situation is typical of an old stock device that requires firmware update(s) before you can use or reuse it. Please refer to the pinned thread in this MCH subforum.
You should have the patience to wait up to a week with the device plugged in and internet enabled before the firmware can be completely updated multiple times to the current state.
Thanks for replying - will wait as long as required and take it from there…
Also thanks for the link to the post re: March 22, 2023 - indeed not illogical and good to know!
Please bear with me:
Question to point 2: Could you please post a link to the “pinned thread” being refered here? Did a search, but outcome is inconclusive.
Question to point 3:
We are now Sunday 16th of February 2025, at this point the MCH has been up and running approx 11 / 12 days, and still the white led is blinking in a slow rythm.
Is / are there any other ways to check what is currently happening on the device?
For what it’s worth:
right after me going through the reset, I could see two network instances referring to the MCH (I guess it’s a SMB server running on the MCH?), one of those two (Capitals), has a TimeMachineBackup folder. I can access that folder without any password, and also I can create folders and put files in them, so that part works.
The other mycloud network instance, is smallcaps and can not be accessed at all
I have also tried to access the MCH using ssh, but it seems that connection is refused on port 22.
Any way to do something with tools like e.g. Wireshark or some other tool?
First of all, congratulations for winning a badge of patience, but unfortunately nothing for following the other direction.
A pinned thread is simply a thread pinned by the administrator on an important subject on top of the other threads; you can’t search for a pinned thread because it is just pinned on top of a list, attracting readers. The link has already been provided for you above and now below as well:
If your device is unable to update to the latest firmware, please backup your data and contact support at the following:
We the readers have no idea how your internet is set up and how the local Western Digital servers your MCH is attempting in order to access the update(s). In many parts of the world, the internet is firewalled and many servers will appear off line to the MCH.
Or simply the router used is now blocking the MCH from updating until such time UPnP is enabled on the router to allow access.
These are all the questions WD support will ask you to provide.
A few final notes regarding your questions:
No one, not even the owner or administrator for the MCH has free SSH access to the underlying OS4 running on the MCH.
The only SSH command avaiable is http://IPaddress:33284/cgi-bin/logs.sh which will download the debuglogs.zip container among others the state of the MCH and what OTA stage and firmware version it contains.
Sometimes WD support will ask for the debuglogs.zip file as part of support.
Using your SSH command above, I put in my MCH’s IP address and was able to indeed download the debuglogs allright
I then had a quick browse through them to see if I could identify something, unforunately it’s rather Chinesish-English Nevertheless, I noticed somehting mentioning upnp.
Now I’m not a UPnP specialist, but I may be able to do more checking of e.g. free ports. Wikipedia tells me that UDP port 1900 may be the one, can you confirm that? Or are others also important.
Then another point: I’m using a Pi-hole, so one thing I can do is plug the MCH directly in my internet provider router. I suppose it would also be handy to check if UPnP is open on my internet router and
Next idea: I think I have some cellular modem around, and it might be an idea to set up a smallish network using a cellular modem and see if this way I can circumvent UPnP being blocked by my Internet Provider (Telenet here in Belgium).
last update: The Pi-Hole story and your UPnP remark got me thinking…
Here’s what I did:
got an old 100 Mb switch out of the cupboard
connected it directly to my network modem (Not entirely sure, but I think I passed UDP/TCP port 1900 through to the MCH, will see later if I can do some test to see if the port is really open)
added an additional network cable so that from time to time I can quickly connect and check the status of things
As for now, I’ll just set another timer for a next wait of 7 to 10-ish days and see if the MCH has updated and if accessability is fixed.
Not sure if the MCH needs rebooting, using fing I can see that it has a new IP address.
Will keep you posted!
Thanks for keeping helping to push towards solutions!