Well I’ve had a super fun time /s recently trying to get my 4tb WDMyCloud device back up and running.
My Device was running os5 quite happily, being the house’s central media storage location.
One morning recently I found that the drive was sat there with a flashing blue LED and was inaccessible both over the network and via the GUI.
I hadn’t done anything different so it wasn’t something I had done, after some research I concluded that it must have been a failed auto-update of the firmware. I later found someone else had made one of the media folders available to the iOS app, so it started indexing the drive which I’m guessing now is what it was doing and why it was unresponsive.
After following guides on here using USB drives I was able to get the device running on OS 2.42.115, but the Web GUI cannot see the hard drive or the shares.
I was able to modify the SMB.conf file so that my PC could see the shares and access the drive, this is great as my data is all there, just the Web Gui can’t, which is a bit of a problem.
So, people, has anyone got a way to get my drive to see that the hard drive is still there and working as it should? It seems like such a small simple step to me.
If you are trying to use the WD web portal (MyCloud.com) to access the My Cloud, note that you cannot do so using the OS3/v4.x or v2.x firmware. WD terminated the web portal access for OS3 My Cloud devices on April 15, 2022.
If you are using OS5 v.5 firmware or have upgraded your My Cloud to use OS5 v5.x firmware then see the OS5 My Cloud support subforum since this subforum (OS3 My Cloud) discusses End of Life/End of Support OS3 devices.
What color is the front LED of the My Cloud unit? Is it blue or some other color. Is it a steady color or flashing.
Have you tried accessing the My Cloud Dashboard by using the local network IP address for the My Cloud?
Which “guide” did you follow to unbrick the My Cloud and install the 2.41.115 firmware?
Have you tried a 40 second pin reset?
The unit has a steady blue colour and as I previously stated I can access the My Cloud Dashboard with no issue, the guide I followed was the usual guide, I believe it’s one of the most popular posts on the forum, where you use a USB key to boot in a recovery mode and then can upload a firmware file.
As I said I’m now at the point where I can access the drive over the network from my computer, but the My Cloud Device cannot see the drive, which is very silly.
I know you have to ask these things but of course I have tried the 40 second pin reset.
Note the first screen shot. Click on the Diagnostics section that says Caution and see what it indicates. It may provide further information on the specific issue.
Others have run into the failed mount issue. For example a search turns up this older discussion:
You may have to adjust any suggestions in that discussion for the second gen single bay My Cloud which may not have the user data partition at the sda4 location.
Yes the second gen single bay My Cloud supports OS5. However, it just doesn’t run very well due to the limited hardware capabilities of the second gen single bay My Cloud. But it can run OS5.
Which is strange as I can access the drive from the PC as I have said and access the files on the shares. It’s just the My Cloud Software that can’t see the drive it’s physically connected to.
I took a look at the suggested link for someone having problems with the drive not mounting, from reading the post it doesn’t seem to be the same issue I’m having as I believe my drives are mounted, hence why I can access them and they are visible when using the “df -h” command.
You could, if you haven’t done so already, click on the bell icon at the top of the My Cloud Dashboard to see if it provides any additional information. Usually errors and the like are listed there.
Another option is to do a Quick Restore in the Dashboard > Settings > Utilities section if you haven’t tried it already and see what happens. It will erase the hard drive and reset the settings. Maybe that will fix the issue.
Its also possible you may need to redo the unbrick procedure following the steps exactly. Wouldn’t be the first time an unbrick didn’t properly unbrick the drive. Note that if following user Fox_Exe’s directions (see this link) to unbrick a second gen single bay My Cloud, follow the steps to partition and format the drives exactly. Do not change any of the values. His directions have two methods of unbricking, one may need to try the other method if the first one they used didn’t work.
I’m trying to sort this without formatting the drives, the data is all there and accessible. It all seems to work EXCEPT the My Cloud Software doesn’t want to. It’s so close to working.
Going back to your first post. What specific “guide” did you follow to reinstall the v2.x firmware to the second gen single bay My Cloud? Did you follow the entire guide or just a portion of it? If the guide had instructions for partitioning and formatting the My Cloud hard drive, did you follow it exactly? Or skip it because you had data still on the drive?
I can’t find the exact forum post with the steps written out but here is the link to the video on YouTube, I’m sure you have come across this many times before, https://www.youtube.com/watch?v=0OrtHp4eGKI.
I also had a look at the unbricking guide by I think it’s fox_exe “_Unbricking_en.txt” that is pretty much the same thing.
Did you only push the firmware to the drive?
Or did you first partition and format the drive first along with create the swap and raid partitions before pushing the firmware to the drive?
If the drive was previously running OS5 and you just pushed the v2.x firmware to the drive without going through the partition and format process it may have created the problem you are now experiencing.
PS: I suppose one could try using the USB method to push the OS5 firmware to the second gen single bay My Cloud.
That is correct, I only pushed the firmware to the drive, I did nothing to the drive that could potentially alter the data on it so no partitioning or formatting etc.
I have previously pushed the OS5 firmware to the drive whilst trying to sort this issue and once uploaded the drive went back to the original problem of being not accessible and flashing blue. After that I started again and am now at this point.
If you think this is what I should try again I will certainly give it another shot.
