MyCloud Solid Red Light

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

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.

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

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

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

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

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

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

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

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

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

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

MyBookLive:~# e2fsck -b 512000000 /dev/sda4
e2fsck 1.41.12 (17-May-2010)
e2fsck: Invalid argument while trying to open /dev/sda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

Did you try this?

Yes, that’s was the first block I tried…

Because you appear to be using a My Book Live, have you checked and or posted to the My Book Live subforum where there may be users more familiar with that device? It is possible that the commands that work on the My Cloud may not work on the My Book Live due to differences in firmware/Linux OS/hardware.

https://community.wd.com/c/personal-cloud-storage/my-book-live

Hi team,
I can see this is dated some time ago, but I’m having the same problem. I’m pretty new to this, so really don’t understand how you access the drive if its not showing up on the Mac finder? How do I find its IP address?
once there, what and how does one enter these fsk things?
imagine you’re explaining this to a real simpleton!!

Anks

From your router’s device IP table, in the router’s admin UI.

By logging in to the MyCloud Linux OS using an SSH client; the commands listed above are run on the MyCloud. Hopefully, you had SSH access enabled before you got a red light…

Thanks for the info,
I have an AirPort Extreme
I have no idea what Ssh is, therefore could tell you if I had it set up or not!

Anks

Using utilities app on the Mac, the my cloud device does not show up?
previously I had the device connected to the my ISP router. I still have this. This is now connected to my AirPort Extreme. I did this to improve the home wifi network. Initially when I set this up (2 weeks ago) all was well. I unplugged the cycloid device to move position in my apartment…when I plugged it it again… solid red light!
It was initially plugged into a surge protected multi plug. So I changed it back to a wall socket…same red light
I then checked the ethernet connections…
I have tried all 4 ports in the router…no joy
I then changed the ethernet cable… no joy
I then tried a soft reboot, and hard reboot… no joy
I then left unplugged for 2 days… no joy
When I initially set this up( with help of apple support) the my cloud device was working(blue light and in my finder menu)
it was literally after I unplugged it and moved it.
I have moved this device several times before with no issues.
No I’m stuck!!
And help would be appreciated

There are a number of causes of a red light. This thread addresses one of them. Google will help with SSH on a Mac, given suitable search strings.

Search the forums for other red light issues.

Thanks

SSH not enabled on my cloud device.
I just checked how to set it up… I didn’t change any of the settings under network

As I mentioned before
Other causes of red light have been reviewed
over heating-not the cause
resetting did not help
with out access to the dashboard to power off and restart- cannot assess firmware or set up issues
if its not showing up on the network I can’t access it not SSH enabled.
I feel this has become a “brick”?
I shall wait for WD to come back to me

Thanks again

There are other red light causes, but without SSH access, you’re a bit stuck resolving them. The thread above will help you recover data if the HDD is working. If you manage that, you may be able to unbrick the drive; see the guides.

I feel really stupid, my device worked again simply by putting it in a vertical orientation instead of horizontal.

Shame on me as this is covered in the user manual.

Hi. I am having similar problem with my drive. Want to try out your solution. Can you please help with how and where to run the commands? I am on Windows 10 laptop and installed UBUNTU from Windows Store.

The process theagustin used involves accessing the My Cloud drive using SSH. This only works if the My Cloud drive is still accessable via SSH. Using SSH generally means one has to enable it in the My Cloud Dashboard. If you didn’t enable it preivously and cannot access the My Cloud Dashboard then those steps used theaugustin via SSH may not work.

Generally for SSH access in Windows one does not need to use Linux (Ubuntu). Instead one can use a SSH client. Putty (https://www.chiark.greenend.org.uk/~sgtatham/putty/) is one such free popular SSH client.

One runs the commands in the SSH terminal window after they initiate an SSH connection to the My Cloud.

Thanks Bennor. I could enable SSH on My Cloud Dashboard.

Will try to follow the instructions.

Cheers!

Finally my drive is fixed!! :slight_smile:

Thanks all! :pray: