I updated the OS and was able to access the drive only on my PC, though it was slow because it was indexing. It’s been weeks and it was still indexing a few days ago, but yesterday I was not even able to access it to see how far along indexing was going. I also couldn’t access the files on the drive. I did nothing to it afaik, and it is in the same spot as always, it is on, and it is running (I can hear and feel it).
Any suggestions on how to fix this? I dare not unplug it and plug it back in as I am worried this will corrupt the files on the drive or worse.
Well - - - OS/5 won’t (or at least it shouldn’t) install on a Gen 1 device.
And if it was loaded onto a Gen2 device. . .the Firmware would show a 5.xx.xxx number, right?
That assumes you could still access the dashboard. . .which you can’t, right?
The only way at this point would be to look at the part number to distinguish. . . .but for goodness sake. . .DON’T POWER DOWN THE UNIT.
If it’s truely Gen1. . . it probably will be stuck “forever” and choke on the indexing task.
If it’s Gen2. . . .it’s gonna be doing indexing for a long, long, long time. Turning it off will risk bricking the unit on reboot.
I would recommend waiting a full week and see if it comes back to life.
Put a cooling fan on it if it starts to run hot.
I hope you have backups… . .
If something bad happens. . . . .Look at the various “unbricking” threads in the OS/3 forum. There are ways to reload the operating system and save the device.
If you do unbrick it. . . . .for goodness sake. . . .don’t load OS/5 on the device. Reload with OS/3.
If it does come to life without doing an unbrick. . . . .go in and TURN OFF CLOUD ACCESS. This is what triggers indexing. . .and sooner or later. . . .indexing will happen again.
If data is not backed up. . .and data is important. . . .consider shucking the drive, loading it into a USB enclosure. . .and using a Linux reader program to access the data from a standard PC.
What are the ending numbers in the P/N? “-00” or “-10”?
First gen single bay ends with “-00”
Second gen single bay ends with “-10”
First gen single bay My Cloud (v4.x firmware) does not support OS5, while the second generation My Cloud (v2.x firmware) does support OS5.
If one has a second generation single bay My Cloud that has been updated to OS5 and which is now crippled by the “indexing” feature, one can access the My Cloud Dashboard and turn off Remote Access/Cloud Access and turn off Twonky (if it is installed as an App). See the following WD Knowledge Base Articles on OS5 Indexing for more information.
That’s typically where I would log in, but since the update I can’t. I tried yesterday again and after a long while it finally loaded the login screen, but it would not let me actually log in.
I was finally able to log in and yes it looks just like that. Indexing at 59%. Shows a firmware update is available, but I assume I should wait for indexing to finish before any updates.
If I turn off cloud access can I still access the files from other devices on my network? I don’t need to access anything via the internet, but I want to be able to access media on my Xbox and smart TV. It all worked just fine until the 5.x update.
Your home network will play just fine without cloud access.
The only thing “Cloud Access” does is enable the WD MyCloud App to function (and the WebApp on your PC).
If you need to access remotely. . then you would VPN into your network. . . .
Twonky Indexing (which is needed for DLNA access) is a seperate task in the new OS/5.
I was finally able to get into it and turn off the cloud access. Now I just need to figure out how to get my xbox and TV to see the files again. I have twonky on but not sure of the correct settings.
