Try pushing the OS5 firmware back to the drive. Note that the OS5 will do indexing and when it does it can take a very long time (more than a day) on the single bay My Cloud rendering the device inaccessible or very slow/sluggish. There are various suggestions that can be found in other discussions on what to do if there is a blinking blue front LED.
If you can gain access to the OS5 My CLoud Dashboard you can try to disable the indexing that drags the unit down.
Otherwise, extract the hard drive from the My Cloud enclosure and connect it to a computer running Linux or Linux drivers and copy any user data off the drive (from the user data partition) to another location. Once the data has been backed up one can use one of the unbrick methods that reformats and partitions the drive.
No idea if it works on a second gen single bay My Cloud running OS5 v5.x firmware. But supposedly on OS3 firmware one could run the following to stop the indexing. (comes from this link).
/bin/sh /etc/rc2.d/S85wdmcserverd stop
The indexing will likely start the next time you boot or reboot the My Cloud. On the OS3 My Cloud there was a way to stop the wdmcserverd from being run in the first place. No idea if it works on OS5.
If MyCloud’s WebGUI can’t detect your hard drive or shares while your PC can, it might be due to a GUI issue or outdated firmware. Try restarting the MyCloud device, updating the firmware, or clearing the browser cache. If the problem persists, contact support for further assistance.
If MyCloud’s WebGUI can’t detect your hard drive or shares while your PC can, it might be due to a GUI issue or outdated firmware. Try restarting the MyCloud device, updating the firmware, or clearing the browser cache. If the problem persists, contact support for further assistance.
Can you access the My Cloud Dashboard? If so does it show any errors in the Alert/Notification Icon section or does the diagnostic section indicate an error? The flashing blue LED can mean a number of things from indexing to some other issue.
As previously indicated, because you were apparently following the USB method for unbricking a second gen single bay My Cloud, you may have to try that process again. Sometimes one has to perform the process several times because they didn’t follow the correct procedures the first time.
You may have to copy the user files/data off the drive to another location and follow the full unbrick procedure which involves partitioning and formatting as the directions indicate. https://wd.hides.su/fox_exe/WDMyCloud-Gen2/_Unbricking_en.txt
Or search the subforum for flashing blue LED to see if there are any other suggestions. Seems to be a common issue after one tries to unbrick a My Cloud and the process wasn’t completed properly.
I initially managed to access the drive over the network whilst using the earlier firmware, though the dashboard couldn’t see its own drive. Despite extensive troubleshooting—exploring all available forum suggestions and other resources—I couldn’t find a solution that didn’t involve reformatting the drive. Given that the drive is visible to other devices in the house, reformatting seemed like it should unnecessary.
Following your advice, I updated the drive to the OS5 firmware. However, weeks have passed, and the drive as well as the dashboard remains inaccessible, with the flashing blue light still present, I knew it may take time but this is a long time to be waiting.
I’ve already attempted the USB unbricking process twice, ensuring each step was followed methodically. While I may try it a third time, my confidence in the device is now very low , and I’m more than likely going to purchase a different device.
If none of the suggestions, including those in other topics, work then maybe it’s time to do the full “unbrick” procedure which includes formatting and partitioning the drive. Backing up the user data to some other location before performing the full unbrick process.
Otherwise, you can contact WD Support and see what help, if any, they might provide. Generally, using any of the unbrick procedures typically voids the device warranty. And due to the age of the device it is likely outside of the warranty period anyway.
These sorts of issues, as a search through the subforum indicate, are what they are. Sometimes one can fix them without nuking the entire drive and starting the unbrick from scratch, sometimes not.
