Unbrick mycloud 1 bay gen 2

#21

OPk I have toc download these files to hard disk, but hard disk have some partitions, and tutorial should explain with clarity WHERE these files have to be extracted.

I will probe alternative procedure and expalin here with detail everything I do.

#22

I used a Ubuntu boot USB stick when unbricking (using Fox’s 1st gen directions) my first gen My Cloud. Did the same. Files copied to the Linux environment, unpacked then copied them to the My Cloud hard drive as the directions indicaed. Had the My Cloud hard drive attached to the PC via a SATA to USB adapter. Done it numerous times, on a variety of different hard drive sizes, with no problems.

I don’t have a gen 2, which uses a different unbrick procedure, so I’m not sure exactly how it would work.

#23

Generally the files would be downloaded into the working directory one is in when using the terminal/command line window. Then one would unpack those files in the same directory. Then one would follow the rest of the directions.

#24

OK I applied second procedure and could arrive to this screen

Safe Mode

Your device firmware appears to be corrupted and your device is currently running in Safe Mode.

Please download the latest firmware from the WD Support website at http:\www.support.wdc.com and upload the firmware file below:

Firmware Version: 1.01.007


First of all posiible firmware for this device can be 2.xxx or 0,4xxxx - I do not know what version i have- Have to tried to update first last official firmware 2.xxx and light goes blue blinking for few seconds and then red solid and shows 0% … and nothing el se. i have tried with last 0,4 firmware and even that. I have read in other post the same situation, but nobody gave a solution

I am near to sucess but,…

I have WDBCTL0030HWT -10 means this is gen 2 with 2xxx firmware so why shows Firmware Version: 1.01.007

#25

No. You cannot load the first gen v3.x or v4.x firmware to the second gen v2.x My Cloud. Doesn’t work like that. Nor can one load the v2.x firmware to a first gen v3.x/v4.x My Cloud. Each generation has slightly different hardware and use different firmware versions.

Try, if you haven’t done so already, downloading and using the initial firmware 2.10.302 (10/7/2015) for the second gen v2.x single bay My Cloud units. Links to most single bay My Cloud units can be found at this link:

Also as a troubleshooting step, after uploading the My Cloud firmware to the unit, try a 40 second reset.

#26

OK I have tried with first firmware before posting. I will try a 40 second reset

#27

Nothing

#28

At the end I WAS ABLE to unbrick with first procedure, 40 sec reste and loading last firmware. I was able to do it with 2 Tb and 1 Tb hard disks. everything seems to be ok. This woluld not have been possible without your support. thank you very much

#29

One of the 4096-705698-000 boards is solid red + blue and ethernet lights does not light. I understand board is dead?

#30

You should be able to test each board using the good disk.

#31

all boards are ok except one, with solid red-blue light.

#32

It’s possible to have a dead board. But just to make sure, check the P/N number on the bottom of the enclosure (if you haven’t already) to ensure it ends with “-10” (2nd gen). If the board is dead may want to contact the seller to complain or swap with another enclosure.

#33

Hi, I have same my cloud as tiomiguel (WDBCTL0030HWT -10). I’m do not have any knowledge in Linux, using commands, etc. I just would like to unbrick my mycloud.

I tried to follow the first procedure and managed to install telnet on windows 10, but I just do not know how to connect to the Mycloud as I don’t know how to do that and understood I have to know the IP of the Mycloud which I do not see in the rooter page.

I installed a Linux like thing to have a terminal, SystemRescueCd, on which I boot via USB stick. I connected the HDD in an icy box via USB. I tried second procedure, but there I guess I’m blocked on step 6. I have message “cp: cannot stat ‘uImage-wdrecovery’: No such file or directory”.

I think uImage, uImage-wdrecovery, uRamdisk and uRamdisk-wdrecovery must be downloaded somewhere but don’t know where/how. I have them in a “root” file on a USB stick.

USB stick is “sdd” and my cloud is “sdb”.

Can someone be so kind and help a very beginner to fix that?

Thanks a lot in advance.

Below list of “commands” I entered:

[root@sysresccd ~]# parted /dev/sdb
GNU Parted 3.2
Using /dev/sdb
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) mklabel gpt
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? Y
(parted) mklabel gpt
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? Yes
(parted) mkpart primary 1049kB 2149MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 8591MB -1MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 7517MB 8591MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 2149MB 3222MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 3222MB 4296MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 4296MB 6443MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 6443MB 7517MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) q
Information: You may need to update /etc/fstab.

[root@sysresccd ~]# mkswap /dev/sdb1
mkswap: /dev/sdb1: warning: wiping old swap signature.
Setting up swapspace version 1, size = 2 GiB (2147946496 bytes)
no label, UUID=e9cd9070-f6ca-4e08-9e67-883a4aa422df
[root@sysresccd ~]# mkfs.ext4 /dev/sdb3
mke2fs 1.44.5 (15-Dec-2018)
/dev/sdb3 contains a ext4 file system
last mounted on /mnt/root on Sat Apr 20 11:01:18 2019
Proceed anyway? (y,N) y
Creating filesystem with 262144 4k blocks and 65664 inodes
Filesystem UUID: 68c672e9-d08e-431f-9ffa-2d35ab04f8b5
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

[root@sysresccd ~]# mkdir /mnt/boot
[root@sysresccd ~]# mount /dev/sdb3 /mnt/boot
[root@sysresccd ~]# mkdir /mnt/boot/boot
[root@sysresccd ~]# cp uImage-wdrecovery /mnt/boot/boot/uImage
cp: cannot stat ‘uImage-wdrecovery’: No such file or directory
[root@sysresccd ~]# cp uImage-wdrecovery /mnt/boot/boot/uImage
cp: cannot stat ‘uImage-wdrecovery’: No such file or directory
[root@sysresccd ~]#

#34

It failed to copy the files from the USB stick to the boot folder.

this is because you are attempting to copy from the /mnt/boot/boot folder context, and no files exist there yet.

You need to mount the USB stick and copy the appropriate files from there.

mkdir /mnt/usb
mount /dev/sdd1 /mnt/usb
cd /mnt/usb/boot
cp uImage-wdrecovery /mnt/boot/boot/uImage
cp uRamdisk-wdrecovery /mnt/boot/boot/uRamdisk
sync
#35

Hi, Thanks a lot for your support. It seems I was able to enter the commands with success. Unfortunately, I still have the flashing red light so I’m lost. I tried 40 sec reboot. Still same issue.

Should I do something else under Gparted? I see I have 5 partitions with warning flag. I would like to do a screenshot but no clue how to do that under SystemRescueCd.

Should I give up as mycloud motherboard is dead?

Below all the commands entered:

[root@sysresccd ~]# parted /dev/sdb
GNU Parted 3.2
Using /dev/sdb
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) mklabel gpt
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? Y
(parted) mklabel gpt
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? Yes
(parted) mkpart primary 1049kB 2149MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 8591MB -1MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 7517MB 8591MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 2149MB 3222MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 3222MB 4296MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 4296MB 6443MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) mkpart primary 6443MB 7517MB
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? Ignore
(parted) q
Information: You may need to update /etc/fstab.

[root@sysresccd ~]# mkswap /dev/sdb1
mkswap: /dev/sdb1: warning: wiping old swap signature.
Setting up swapspace version 1, size = 2 GiB (2147946496 bytes)
no label, UUID=e9cd9070-f6ca-4e08-9e67-883a4aa422df
[root@sysresccd ~]# mkfs.ext4 /dev/sdb3
mke2fs 1.44.5 (15-Dec-2018)
/dev/sdb3 contains a ext4 file system
last mounted on /mnt/root on Sat Apr 20 11:01:18 2019
Proceed anyway? (y,N) y
Creating filesystem with 262144 4k blocks and 65664 inodes
Filesystem UUID: 68c672e9-d08e-431f-9ffa-2d35ab04f8b5
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

[root@sysresccd ~]# mkdir /mnt/boot
[root@sysresccd ~]# mount /dev/sdb3 /mnt/boot
[root@sysresccd ~]# mkdir /mnt/boot/boot
[root@sysresccd ~]# cp uImage-wdrecovery /mnt/boot/boot/uImage
cp: cannot stat ‘uImage-wdrecovery’: No such file or directory
[root@sysresccd ~]# cp uImage-wdrecovery /mnt/boot/boot/uImage
cp: cannot stat ‘uImage-wdrecovery’: No such file or directory
[root@sysresccd ~]# mkdir /mnt/usb
[root@sysresccd ~]# mount /dev/sdd1 /mnt/usb
[root@sysresccd ~]# cd /mnt/usb/boot
[root@sysresccd /mnt/usb/boot]# cp uImage-wdrecovery /mnt/boot/boot/uImage
[root@sysresccd /mnt/usb/boot]# cp uRamdisk-wdrecovery /mnt/boot/boot/uRamdisk
[root@sysresccd /mnt/usb/boot]# sync
[root@sysresccd /mnt/usb/boot]#

#36

you will get the flashing red light, but you will get a web interface to come up if you put the IP in the address bar. It will tell you “looks like your firmware is corrupt, please choose a firmware file to upload” or some such.

This is where you can actually send a real firmware image to it.

#37

Thanks a lot. Indeed now the mycloud is visble in my router page and I’m able to see its IP address. I entered it and saw the safe mode asking to update the firmware. But I’m stuck again. I upload a file “My_Cloud_GLCR_2.31.174.bin” it goes to 100% but seems to be blocked even after one hour waiting. See below screenshot. So frustrating to have issues at all steps. Should I look for other files to update the firmware?
image

#38

I suggest using this firmware for debrick.

http://download.wdc.com/nas/My_Cloud_GLCR_2.21.126.bin

I have tried newer ones, but they fail during the volume setup in various ways.

also-- that screen does not auto-refresh after it reboots… you need to press f5 after it reboots.

#39

Hi, thanks, I tried this one but still same issue, I let it all night long. This morning I tried to redo the whole procedure. I have flashing red light when i plug the device to the router. I started uploading the firmware and it blocks at 0% and solid red light on device. I will wait an hour and try to refresh. But i’m afraid I will again have same issue.

#40

Did you format the other volumes before debricking?

I know that Fox’s instructions dont say to do so, but you should. When the pushed over firmware boots, it tries to mount volume 4 and volume 7 for internal system process scratch and persistent storage purposes. If it fails, it will go into safe mode and tell you that the firmware is corrupt, much like when you push the recovery images over.

Format all the volumes with ext4, then put the recovery uImage and uRamdisk on. the firmware flash should succeed after that. If it doesnt, for whatever reason, hit F5 on your keyboard once you see the solid red light (that indicates that the new firmware booted, but it has a problem) and push the firmware a second time. Shouldn;t be necessary with that older firmware-- I only ran into that with newer ones, but still.