After rebooting, the files on my My Cloud 3 TB drive (same as the 6 TB drive) are easily accessible, however the homepage http://[networkname]/UI no longer responds and remains stuck on “Reading configuration information …”.
The page is displayed well but remains on this message, therefore impossible to authorize to configure the NAS. Seems to have appeared after switching off and on, following latest firmware. Tested on Edge, Chrome, Firefox, IE (Windows XP in VM Ware)…
Note: I have the version of the NAS that will not migrate to OS5…
What color is the front LED? Blue or some other color?
Can you access the My Cloud Dashboard by it’s IP address?
Can you access the My Cloud Dashboard by the My Cloud device name? (ex: http://wdmycloud/)
Have you tried a 4 second reset or a 40 second reset?
What color is the front LED? => Blue
Can you access the My Cloud Dashboard by it’s IP address? => Not anymore (message “reading configuration file” still remains on screen without asking for credentials)
Can you access the My Cloud Dashboard by the My Cloud device name? (ex: http://wdmycloud/ ) => same as with IP.
Have you tried a 4 second reset or a 40 second reset? => yes, same problem.
As I said, I can see the homepage http://[mycloudname]/UI, but the first page waits with the message "Reading configuration information …”, but no credentials are asked to me, so I cannot go further.
I don’t have any USB attached to mycloud drive, and ssh was already disabled.
When MyCloud drive make a long time for scanning media files at first boot, the led is not blue until it finishes… but mine is blue… and I have waited many hours… This is the first time for me that it doesn’t asks for credentials… And I have exactly the same problem for my second MyCloud 6 TB as my 3TB, in the same time after rebooting, this is why I suggest a problem with the last firmware…
@skysky
Below is an image of my 1st generation WDMYCLOUD Firmware v04.05.00-353. I do not have to enter any credentials to open the dashboard or get to any other tabs. My front blue LED burned out several years ago. I have a static address.
There doesn’t seem to be a general fix for the issue. At least one person apparently resorted to using one of the “unbrick” procedures to restore access to their My cloud. And it doesn’t seem to be a wide spread issue at this time either. Don’ t see any other recent posts with the latest firmware being the obvious culprit. Have not seen this issue on a first gen single bay running v04.06.00-111 (current/latest) firmware.
I didn’t made any changes neither official or not official changes.
The firmware version is… : I cannot tell you because I am not connected to mycloud… , but last time, this year, I think it was the last firmware for v1 that don’t migrate to Cloud OS5 and remains in OS3…
Perhaps some system file is in bad cluster ? Is there a way to recover the system without deleting all the files ?
Yes, as previously mentioned there is the option to try and “unbrick” the drive. It involves extracting the hard drive from the My Cloud enclosure, connecting that drive to a computer (using a spare SATA port or a powered USB to SATA adapter) running Linux or a Linux boot disc/boot USB flash drive. And pushing/copying several several “.img” files to several of the partitions on the hard drive. It is wise to backup the user data from the data partition (generally /sda4) from the extracted My Cloud hard drive as a safety precaution.
There are a number of directions people have used over the years, the following link has one set some have successfully used on a first generation single bay My Cloud that has a P/N number on the bottom on the unit that ends with “-00”. https://wd.hides.su/fox_exe/WDMyCloud-Gen1/Replace%20HDD%20-%20English.txt
That procedure involves using one of the two following older files to extract older firmware to the hard drive, once booted to the older firmware one can update to the current/newer v4.x firmware.
Around step 9 of those directions has the procedure to use on of the above files and pushing three “.img” files to the various partitions. Typically one will get a red front LED after unbricking, one should try to access the My Cloud Dashboard > Settings and if they can, perform a System Only reset to fix the front red LED and fix several other issues that may be present after initial boot of an unbricked drive.
Standard Warning: You proceed at your own risk when unbricking!!! Backup your data before unbricking!!!