Hi everyone!
Can you please help me?
After having connected my MyCloud, the blue light is continuously blinking.
I’ve made a reset (40 seconds) and even it remains blinking.
Impossible to connect via my PC.
My cable from my Mycloud is directly connected to the router.
Have you some piece of advice?
Thanks a lot!
Have a nice day
Bern64
Note: MyCloud is a WDBCT … - 10 if it helps
Because you have a second gen (P/N ends with -10) single bay My Cloud, has your device been updated to the v5.x (OS5) firmware? A continuously front LED blinking blue seems to be a common problem after a v5.x firmware update.
http://wdstagingsplit.staged-by-discourse.com/search?q=blinking%20blue%20%23os5%3Amy-cloud-os5
See the various posts in the OS5 subforum to see if there are any suggestions by others who have experienced the front blinking blue LED issue.
Best case scenario, it’s just taking a long time to index all the files. Worst case scenario, your NAS is bricked. Look up flashing blue light on this forum.
Thanks a lot. Would it be possible to create a USB bootable in order to try to unbrick my wd Mycloud 2 To? Who would be kind to helping me please?
If you are asking about the USB drive used to unbrick a second generation single bay My Cloud then see user Fox_exe’s directions for unbricking a second gen single bay My Cloud:
https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/_Unbricking_en.txt
https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/usbrecovery.tar.gz
Alternate method unbrick files:
https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/Developing/uImage-wdrecovery
https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/Developing/uRamdisk-wdrecovery
Thank you Bennor. I will try it and come to it later on. It will take some days I think because it seems not so easy to do for me …
@Bennor
I followed all the instruction. Telnet to MyCloud. But got stock at command
“umount /mnt/root /mnt/usb”, it’s just sitting, frozen there.
Did I mess it up? I would appreciate your help. Thank you
What specific My Cloud device do you have? What are you attempting to do? Unbrick a second generation single bay My Cloud or something else? Try rebooting and trying the process again if you haven’t done so already.
I have a single 3TB WD MyCluod NAS, with the P/N: WDBCTL0030HWT - 10. I was trying to survive the “blue blinking light”.
After the first freeze, a couple of times I tried it rebooting, and follow the same process again. It would reboot, I would get the yellow & red lights. I would type the lines of code, but as soon as I got to and typed “umount /mnt/root /mnt/usb”, and pressed “enter”, the cursor would jump to the next line and just stay there, with no “/ #” prompt. After the last attempt, I could not Telnet to the NAS box anymore, so I gave up.
Today I rebooted again, I rescanned the IPs and saw “Marvel Semin Conductor, Inc.” on different IP, with a different MAC address. Got happy and tried to Putty, Telnet again to the box, but it would not let me in!
But after about 5-15 minutes (not sure about the exact timing), I tired Telnet again and I am now in the Box’s OS, and don’t know what to do next. As of now, I have not started trying to start the process again till I get some kind of a guidance.
FYI, I can browse via telnet the OS’s file system, directories and files. I think it is fully functional! BTW, I am not a Linux expert, just know a little commands from the MSDOS days.
Is there a way to know the existing firmware version of the box now?
Any ideas what to do next?
Have you tried accessing the My Cloud IP address via a web browser to see if the recovery GUI is available/shown?
Did you initially do all the steps indicated including partitioning and formatting the drive per the instructions (the whole “mkpart” section)?
Yes. I get:
It This site can’t be reached", 192.168.68.XX refused to connect.
Try:
ERR_CONNECTION_REFUSED
No. I thought I should not, since I am trying to recover the data, and that might, will delete the data! So I skipped the following step:
5. Format HDD if need:
parted /dev/sda
mklabel gpt
mkpart primary 1049kB 2149MB
mkpart primary 8591MB -1MB
mkpart primary 7517MB 8591MB
mkpart primary 2149MB 3222MB
mkpart primary 3222MB 4296MB
mkpart primary 4296MB 6443MB
mkpart primary 6443MB 7517MB
q
mkswap /dev/sda1
mkfs.ext4 /dev/sda3
Is there any way to avoid deleting the data?
Try the “alternate method” indicated in the instructions if you haven’t done so already. The alternate method doesn’t rely on telnetting into the My Cloud. Instead it requires one to extract the hard drive and connect it to a PC running Linux via a USB to SATA powered adapter or a spare SATA port.
When using the “alternate method”, would I be able to retain the data?
If not, can I, should I go back to original method without taking out the hard drive, using the following via Telnet?
3. Plug this USB drive to WD MyCloud, turn on power. Wait yellow-red (blinking) light.
4. Connect via Telnet (Search IP in your router, unde DHCP section.)
5. Format HDD if need:
parted /dev/sda
mklabel gpt
mkpart primary 1049kB 2149MB
mkpart primary 8591MB -1MB
mkpart primary 7517MB 8591MB
mkpart primary 2149MB 3222MB
mkpart primary 3222MB 4296MB
mkpart primary 4296MB 6443MB
mkpart primary 6443MB 7517MB
q
mkswap /dev/sda1
mkfs.ext4 /dev/sda3
6. Install original WD recovery and reboot:
mkdir -p /mnt/usb /mnt/root
mount /dev/sda3 /mnt/root
mount /dev/sdb1 /mnt/usb
cp -r /mnt/usb/boot /mnt/root/
cd /mnt/root/boot
rm uImage uRamdisk
mv uImage-wdrecovery uImage
mv uRamdisk-wdrecovery uRamdisk
cd /
umount /mnt/root /mnt/usb
sync
reboot -f
You should have backed up the data on the My Cloud prior to trying the various “unbrick” methods. If you can still access the My Cloud using Telnet you can still try to issue the commands at step 6. You can try a different computer, preferably one running Linux to eliminate any possible issues running Windows might introduce.
But if you have somehow corrupted the hard drive layout then you likely will have to start from the beginning and partition/format the drive properly exactly as the directions indicate.
You may also want to remove the My Cloud hard drive and connect it to a computer to check its health status. Could be the drive is failing. If it is, no amount of trying to fix the blue LED will solve a bad or failing hard drive.
@Bennor One last thing.
I read somewhere on this forum that the command “e2fsck /dev/sda3” is missing just before “reboot -f” command. Is “e2fsck /dev/sda3” necessary?
sync
e2fsck /dev/sda3
reboot -f
Thank you very much for your help. I will keep you posted.
Couldn’t hurt to try. All that command does is scan the drive or partition(s) for errors and fixes them.
@Bennor Here to report with some good news, I am progressing with 2 issues.
I restarted the whole process again from step 5 via telnet, everything went well up to “mkpart primary 8591MB -1MB”, it produced the following:
Issue 1 - Warning
(parted) mkpart primary 8591MB -1MB
mkpart primary 8591MB -1MB
*Warning: The resulting partition is not properly aligned for best performance.*
*Ignore/Cancel?*
*Ignore/Cancel? ignore*
ignore
I clicked ignore. I don’t know what this warning might cause in the future. I am thinking, if and when I am logged into the dashboard, it gives me a chance to reformat!
After that every command executed properly, without any warnings or errors, the box reboot, I unplugged the power plug and the USB, and re-plugged the power, it went to blinking blue, after about a minute it went to red, IP had changed, Once I went to the browser with the new IP, it produced the following window:
Issue 2 - Firmware update:
Is my current Firmware Version is 1.01.007, based the screen capture above?
Finally, what firmware update do I use.
The above firmware versions are found here on this page, at the very bottom of the page.
Download Free Setup From Here:white_check_mark:.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
That safe mode page where you install the firmware is what you are supposed to get. Start by installing the latest (last) 2.42.115 firmware. After flashing check the My Cloud Dashboard to see if it is working properly and if there are any diagnostic errors. It is usually recommended that one do a 40 second pin reset after successfully flashing the initial v2.x firmware after getting that safe mode page.
Once you verify the My Cloud is operating normally you can, if you so choose, update to v5.x firmware from the v2.42.115 firmware. Note that more than a few have chosen not to update a singe bay second gen My Cloud to v5.x firmware due to various performance issues that model suffers under the v5.x firmware. Search the subforums (including My Cloud OS5 subforum) to see the issues and complaints about OS5 v5.x firmware.
@Bennor I’ll do it right away.
| Forums | News and Announcements | Register | Help | Forum Guidelines |
Copyright © 2021 Western Digital Technologies, Inc. All rights
reserved.
|
Trademarks
|
Privacy
|
Community Terms of Service
|
Site Terms of Use
|
Copyright
|
Contact WD
|
