MyCloud Solid Red Light

Theagustin · October 21, 2015, 6:58am

My MyCloud is displaying a solid red light and its complaining it has a critical error and that the content status is “not mounted”. Short of ripping the drive out and running SpinRite does anyone have any ideas as to how I can go about this? I think it might be a corrupted block thats making the RAID array fail but am not sure how to proceed.

I obviously still have WEBUI and SSH access.

cat0w · October 21, 2015, 10:59am

What have you tried since this started? Have you looked at the user manual, (see Table of Contents, LED’s)?

cat0w
USA

Theagustin · October 21, 2015, 2:36pm

There is nothing on page 10 thats of any help.

Fault/action required Red Solid The following faults trigger this state:
• Disk SMART failure ← I’m not getting any smart warnings.
• Data volume does not exist ← it exists the array is just not mounting.
• System volume does not exist ← system volume is fine I have ssh and web access.
• System thermal shutdown (75° C) ← There are no thermal warnings and yes I tried giving it a cool down it did nothing

Which brings me back to I think theres a corrupted block thats causing the array to fail. Do you know how I can rebuild the array?

Theagustin · October 21, 2015, 3:25pm

Wow, okay just an update this worked, I have all my data again and I’m in the middle of backing it up.
Now I’m not sure on whether I should continue using this drive or replacing it.

"1. Log onto the drive, root and welc0me are the default username/password combo.
2. Make sure your paritions are intact. # parted -l will tell you this.
3. Type # mke2fs -n /dev/sda4. This will get you the filesystem, but more importantly at the end give you the superblock backup locations by block location.
4. Pick one, then enter this command.
e2fsck -b blocknumber /dev/sda4

It will look for bad blocks and ask for your confirmation to continue/ignore then write over any corrupted ones. Yes to ignore, yes to rewrite.

It will do up to five passes of diagnostics, prompting if it finds anything out of the ordinary such as file countes and errant inodes. I answered yes to everything.

When it is complete it will either report “Killed” or a summary. Type # reboot and let the drive rebuild its library. 30-ish minutes later (depending on how much data you had on it) you should have access to your files."

Ralphael · October 30, 2015, 2:13am

you confirmed my worst fears but yet you assuage them.

My worst fear is just the standard fsck’ing “Blinking White LED” can go awry and thus the cloud is a brick. However the fact that you can still SSH into the drive, do a manual e2fsck on the drive and then reboot is a blessing.

I always had this theory that the red light is actually e2fsck waiting for you to answer “yes”.

Good Job Theagustin!!

Andy_Denis · November 8, 2015, 6:24pm

Hi Theagustin, i have exactly the same problem as you have and read youre solution and wondered if you could simplify it so that a simpleton could do the same to access to the drive. Ive never SSH into anything before and realise that warranty is void if i do so butive already open up the box in desperation to get the info offthe drive and have a solid red light. Do i assume you plugthe box into the mains and directly plug the etherenet cable directly into the mac do ssh, how do i find the ip address is if the box has a a red light as it wont initiliseoram i missing something? Thanks for any reply or help

Theagustin · January 27, 2016, 8:12pm

Andy I’m so very sorry I didn’t reply truth is I forgot to check the forums after I found a solution. I can however still assist you if you still require the help. Let me know.

wongkokchuan · May 10, 2016, 3:51pm

Hi, Theagustin,

Thanks for posting a solution. I had the same problem (red LED, data volume failed to mount). Contacted WD support but they couldn’t help further after doing full test show no error.

I tried the “mke2fs” then “e2fsck” but was getting message superblock cannot be read. Have tried a few but still same problem (see below).

Any further advice? anyone?

MyBookLive:~# mke2fs -n /dev/sda4
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=1 blocks, Stripe width=0 blocks
182861824 inodes, 731437568 blocks
36571878 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
22322 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544

MyBookLive:~# e2fsck -b 32768 /dev/sda4
e2fsck 1.41.12 (17-May-2010)
e2fsck: Bad magic number in super-block while trying to open /dev/sda4