Flashing red led after power loss

Hi I have a problem with my cloud 4tb
My mother accidentally pulled out the power cable and now the disk is blinking red light for many hours 10+ and I can’t find it on my network or ping it. The disk is working because it slowly vibrates. What to do?

Thanks in advance

Have you initially tried the 40-second reset?

If it a V2 mycloud , red can also signify no network connectivity.

Since you have not stated which generation of My Cloud you have, 1st or 2nd, I suggest you use this link, determine the generation you have and read the correct User Manual for yours.

1st generation has firmware version 4.xx.xx
2nd generation has firmware version 2.xx.xx

https://support.wdc.com/product.aspx?ID=904&lang=en

i have done it nothing happens, red led keeps flashing no restarting

i can’t access to the disk but i believe is 2nd gen because when it was working fine red light was showing when was no network connectivity

What are the LED’s on the rear doing? Are they working? If they appear normal then I suggest you shut it down for a while, long enough to cool, and then plug it back in and see what happens.

i left for a couple of hours to “rest” but when i plugged it still the same situation
back the leds from the lan are active orange and green seems that working

http://anionix.ddns.net/WDMyCloud/WDMyCloud-Gen2

404 Not Found
but i think if i do this i will lost warranty

https://wdnas.ml/fox_exe/WDMyCloud-Gen2/

You already lost any warranty because it broke for your fault (or your mother’s). Anyway this procedure doesn’t need to dismantle the case, what it does is to boot a recovery from a usb stick and then it allows you to part the hd and upload a recovery into it, then you’ll upload the firmware and begin from scratch. I don’t see why it should break the warranty. Anyway it can even be that you broke the internal hd so if it doesn’t work (it worked perfectly for me) you will have to extract the hd, fix it or put in another one. You’ll know if your nas is gen 2 (v2 firmware) if its sn ends with 10

something went wrong

/ # mkdir -p /mnt/usb /mnt/root
/ # mount /dev/sda3 /mnt/root
mount: mounting /dev/sda3 on /mnt/root failed: No such file or directory
/ # mount /dev/sdb1 /mnt/usb
mount: mounting /dev/sdb1 on /mnt/usb failed: No such file or directory
/ # cp -r /mnt/usb/boot /mnt/root/
cp: can’t stat ‘/mnt/usb/boot’: No such file or directory
/ # cd /mnt/root/boot
/bin/ash: cd: can’t cd to /mnt/root/boot
/ # rm uImage uRamdisk
rm: can’t remove ‘uImage’: No such file or directory
rm: can’t remove ‘uRamdisk’: No such file or directory
/ # mv uImage-wdrecovery uImage
mv: can’t rename ‘uImage-wdrecovery’: No such file or directory
/ # mv uRamdisk-wdrecovery uRamdisk
mv: can’t rename ‘uRamdisk-wdrecovery’: No such file or directory
/ # parted /dev/sda
GNU Parted 3.1
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) mklabel gpt
mklabel gpt
Warning: The existing disk label on /dev/sda will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? yes
yes
(parted) mkpart primary 1049kB 2149MB
mkpart primary 1049kB 2149MB
(parted) mkpart primary 8591MB -1MB
mkpart primary 8591MB -1MB
(parted) mkpart primary 7517MB 8591MB
mkpart primary 7517MB 8591MB
(parted) mkpart primary 2149MB 3222MB
mkpart primary 2149MB 3222MB
(parted) mkpart primary 3222MB 4296MB
mkpart primary 3222MB 4296MB
(parted) mkpart primary 4296MB 6443MB
mkpart primary 4296MB 6443MB
(parted) mkpart primary 6443MB 7517MB
mkpart primary 6443MB 7517MB
(parted) q
q
Information: You may need to update /etc/fstab.

/ # mkswap /dev/sda1
Setting up swapspace version 1, size = 2147479552 bytes
UUID=b65781dc-a363-453f-887b-44f76a7be89f
/ # mkfs.ext4 /dev/sda3
mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: ef6ad2fd-fe1c-4a10-9586-5276f15d19a1
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

/ # mkdir -p /mnt/usb /mnt/root
/ # mount /dev/sda3 /mnt/root
/ # mount /dev/sdb1 /mnt/usb
mount: mounting /dev/sdb1 on /mnt/usb failed: No such file or directory
/ # cp -r /mnt/usb/boot /mnt/root/
cp: can’t stat ‘/mnt/usb/boot’: No such file or directory
/ # cd /mnt/root/boot
/bin/ash: cd: can’t cd to /mnt/root/boot
/ # rm uImage uRamdisk
rm: can’t remove ‘uImage’: No such file or directory
rm: can’t remove ‘uRamdisk’: No such file or directory
/ # mv uImage-wdrecovery uImage
mv: can’t rename ‘uImage-wdrecovery’: No such file or directory
/ # mv uRamdisk-wdrecovery uRamdisk
mv: can’t rename ‘uRamdisk-wdrecovery’: No such file or directory
/ # cd /
/ # umount /mnt/root /mnt/usb
umount: can’t unmount /mnt/usb: Invalid argument
/ # sync
/ # reboot -f

Post the result of a blkid command

blkid

Anyway I can’t see why you were not able to create the two directories.

Try to do again all the steps, is the light flashing yellow/red?

/ # blkid
/dev/sda1: UUID=“CAB5-0E13”

fdisk -l

Disk /dev/sda: 8053 MB, 8053063680 bytes
16 heads, 60 sectors/track, 16384 cylinders
Units = cylinders of 960 * 512 = 491520 bytes

Device Boot Start End Blocks Id System
/dev/sda1 6 16384 7861760 b Win95 FAT32 => my usb where is my disk 4TB?

Well, I’m not an expert but it looks like you fu**ed up the hd. Try the warranty card or you have to dismantle the box and see what happened. Connect the hd to a pc and see if it shows up, if it works, you broke the mainboard. But, I repeat, I’m not an expert.

ok man thanks for your help
i will take to the shop that i bought it
i hope that warranty covers me because i have it only 8 months :cold_sweat:

I have a dumb question? If the disk is not listed. How is it that he can run blkid?

i had the usb flash drive that i booted the drive

Are you saying that you booted a PC using a USB flash drive that booted up windows? How was the
My Cloud device connected to the PC? I ask because if the My Cloud is not accessible from the PC
running windows it won’t be accessible from the PC running Linux. On Linux /dev/sda is always the boot disk.

read this
https://wdnas.ml/fox_exe/WDMyCloud-Gen2/_Unbricking_en.txt

OK So you booted the My Cloud from a USB drive.