After frequent power outages, my WDMYCLOUD (Gen1) (04.x) stopped working. The LED at the front is SOLID WHITE. I can sense the hard drive running when I touch the device. I did the basic checks, such as replacing the ethernet cable, connecting directly to my laptop using a patch ethernet cable, trying the 4 second reset and 40 second reset but nothing worked.
Going over the some of the threads I assumed my device was bricked. I opened the case and connected the hard drive directly to my laptop.
My laptop runs CentOS 8 and was able to detect the hard drive automatically. I opened GParted and see that it’s unallocated.
Please help how to proceed further. Is the hard drive bricked? The steps to unbrick were for Windows. Are they any guides for CentOS 8?
There are a number of unbrick methods. Some use Linux commands. One can use the forum search feature (magnifying glass icon upper right) to find them if one hasn’t done so already.
One example of how to unbrick a first gen v4.x firmware single bay My Cloud that some of us have used with success. Typically requires the use of the Linux terminal window to issue the appropriate commands.
If one gets a red front LED after running the unbricking procedure try accessing the My Cloud Dashboard anyway and if successful, go to Settings > Utilities > System Factory Restore and perform a System Only restore.
At Step 8 of user Fox_exe’s first gen directions, one may get an error. The command ‘mdadm -A /dev/md0 /dev/sdb1 /dev/sdb2’ sometimes throws an error. I typically just ignore the error and continue to the next entry command in step 8.
And at Step 12 one may get another error. When using the original_v04.01.02-417.tar.gz file, I get a out of space error when running the command ‘dd if=kernel.img of=/dev/sdb5’. I typically ignore this error and proceed to the next entry command in step 12. When using the original_v03.04.01-230.tar.gz extracted files I do not get the out of space error message on sdb5.
My initial thought is the partition table on your HDD got corrupted.
Try re-declaring the factory partition structure (and raid configuration) first, without “flashing” any images to any partition. The links posted previously have specifics I’m sure. If you have trouble, let us know.
parted /dev/sdb
GNU Parted 3.2
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /dev/sdb: unrecognised disk label
Model: Mass Storage Device (scsi)
Disk /dev/sdb: 4001GB
Sector size (logical/physical): 4096B/4096B
Partition Table: unknown
Disk Flags:
(parted) mklabel gpt
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4828M 100%
(parted) mkpart primary 4624M 4724M
(parted) mkpart primary 4724M 4824M
(parted) mkpart primary 4824M 4826M
Warning: You requested a partition from 4824MB to 4826MB (sectors
1177734..1178222).
The closest location we can manage is 4824MB to 4826MB (sectors
1177856..1178222).
Is this still acceptable to you?
Yes/No? Yes
(parted) mkpart primary 4826M 4828M
Warning: The resulting partition is not properly aligned for best performance:
1178223s % 256s != 0s
Ignore/Cancel? Cancel
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.
It seems you declared only seven partitions - you need to declare the final one, even if it complains about “alignment” problems. If you are using the info from @fox_exe, the eighth one ought to be (parted) mkpart primary 4826M 4828M. It will slot nicely into the space marked unpartitioned when viewed in gparted
Also, it appears that the second screenshot you posted of gparted shows your raid device being called /dev/md127. Your WD MyCloud will not be happy with that and get stuck in a "[SOLVED] Solid White Light (not blinking) Boot Loop Every 42 Seconds". You must re-declare the raid configuration specifying /dev/md0 as described in that post under The Fix.
Don’t flash new images just yet. Your device may still come back to life without performing that step.
.