Red LED. But SSH is on and I have access to my files. How to fix it?


#1

Hello,

I’ve got WD My Cloud (firmware v. 04.04.02-105). I tried to install Transmission torrent client using this tutorial but the installation failed. I rebooted WD My Cloud and got Red LED, no web interface and my Windows 10 refused to access the storage via network. Though SSH was still on and I could log into the storage. I checked the storage with “df –h” and got this –

# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          1.9G  869M  957M  48% /
/dev/root       1.9G  869M  957M  48% /
tmpfs            40M  3.4M   37M   9% /run
tmpfs            40M     0   40M   0% /run/lock
tmpfs            10M     0   10M   0% /dev
tmpfs           5.0M     0  5.0M   0% /run/shm
tmpfs           100M  2.3M   98M   3% /tmp
/dev/root       1.9G  869M  957M  48% /var/log.hdd
ramlog-tmpfs     40M   12M   29M  29% /var/log

Then I went through the forum and found that the following command allows me to get access to all my files –

mount -o noatime /dev/sda4 /DataVolume

Moreover after using the command Windows 10 can access all my files via network again – I can copy them, delete or add new ones. But the LED is still RED and I don’t have access to the storage via the web interface.

After the “mount” command “df –h” shows the following –

# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          1.9G  869M  957M  48% /
/dev/root       1.9G  869M  957M  48% /
tmpfs            40M  3.4M   37M   9% /run
tmpfs            40M     0   40M   0% /run/lock
tmpfs            10M     0   10M   0% /dev
tmpfs           5.0M     0  5.0M   0% /run/shm
tmpfs           100M  2.3M   98M   3% /tmp
/dev/root       1.9G  869M  957M  48% /var/log.hdd
ramlog-tmpfs     40M   12M   29M  29% /var/log
/dev/sda4       2.7T  1.7T 1019G  63% /DataVolume

But after rebooting I can’t access the files again. Is there any way to fix the issue? Is it possible to restore the storage without loosing my files?

Thank you!
Alex


How recover firmware
LED - RED (constant) and i can't see files anymore
#2

If you go to /usr/local/sbind there are three files called ledConfig.sh ledMain.sh ledCtrl.sh.
These three files describe how the led color is set. There are also 4 files in the .tmp directory
that have information about the led status. They are called led_cur_ev,led_cur_st, led_err_ev,led_err_st. Between these file you should be able to determine why the led is red.

RAC


#3

the files from TMP have the following content -

led_cur_ev - LED_EV_VOLUME
led_cur_st - error
led_err_ev - LED_EV_VOLUME
led_err_st - error

What does it mean?


#4

Did you note the warning from Bill_S at the top of the first post?

Using apt-get to install packages from standard Debian repositories is likely to cause problems, since the v4 mycloud firmware is built using a non-standard 64kB page size (vs standard 4kB). That guide dates from v3 firmware days, when it was built with a 4kB page size, so apt-get was possible.

If you go to the last post in that thread, Bill_S gives instructions on how to restore your firmware. Hopefully, this will fix your problem, assuming you still have SSH access. If not, you may need to start thinking about unbricking.


#5

The LED_EV_VOLUME indicates that the DataVolume was not mounted. I would check
the log file in /var/log looking for why the DataVolume did not mount.

RAC


#6

Hello and thank you for your reply!
I’m quite newbie in all this. Bill_S suggests a tutorial “Instructions to rebuild a Debian package”. Could you please tell me, do I need to rebuild all the packages from the firmware or any specific ones?


#7

Thank you for your reply!
Do I have to pay attention to any specific log-file or should I go through all of them?


#8

What are you trying to do? You don’t need to rebuild an packages. Search the forum for
factory reset. You might be able to reset without losing data to get rid of the red light. As
noted above don’t install software unless you understand how to do it. The Linux that the
My Cloud uses if different from the standard Linux release.

RAC


#9

If you want to re-install the firmware, just login via SSH and use the command in the last post:

updateFirmwareFromFile.sh /CacheVolume/updateFile.deb

To install Transmission, search for Nazar_78’s thread.


#10

I tried to update from a file and got this -

updateFirmwareFromFile.sh:05/24/16 16:50:18:new_upgrade_version=2
updateFirmwareFromFile.sh:05/24/16 16:50:18:current_upgrade_version=2
`/tmp/tmp.0s3V0DYLhf/upgrade-version' -> `/CacheVolume/upgrade/upgrade-version'
updateFirmwareFromFile.sh:05/24/16 16:50:19:Newer upgrade scripts in update package, use normal update method
(Reading database ... 26182 files and directories currently installed.)
Preparing to unpack /CacheVolume/updateFile.deb ...
preinst_project-control: begin
/
isImage=true
Master package name: sq
sq-preinst: action=install
currentRootDevice=/dev/md0
forked-daapd: no process found
disable lazy init
root: disable lazy init
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
Prepare for upgrade pkg install...
mdadm: set /dev/sda1 faulty in /dev/md0
mdadm: hot removed /dev/sda1 from /dev/md0
Preparing FW upgrade image on: "/dev/md1"
preinst: currentRootDevice=/dev/md0
preinst: upgradePath=/mnt/rootfs
preinst: upgradePart=/dev/sda1
preinst: upgradeDevice=/dev/md1
send_update_log=200
Unpacking..
Unpacking sq (04.04.02-105) ...
dpkg: error processing archive /CacheVolume/updateFile.deb (--install):
 cannot copy extracted data for './CacheVolume/upgrade/rootfs.img' to '/CacheVolume/upgrade/rootfs.img.dpkg-new': failed to write (No space left on device)
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /CacheVolume/updateFile.deb
Unpack timeout occurred
failed 202 "upgrade download failure"
send_update_log=200
logger: disable lazy init
stopping duplicate md device /dev/md1
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
umount: /nfs/Public: not mounted
umount: /nfs/TimeMachineBackup: mountpoint not found
umount: /nfs/SmartWare: not mounted

As far as I can understand the process stops here -

dpkg: error processing archive /CacheVolume/updateFile.deb (--install):
cannot copy extracted data for './CacheVolume/upgrade/rootfs.img' to '/CacheVolume/upgrade/rootfs.img.dpkg-new': failed to write (No space left on device)

But df -h shows more that 1Tb of free space. What should I do?

Thank you,
Alex


#11

You might try downloading the firmware version cleanly; the updateFile.deb may be corrupted or obsolete. See Bennor’s instructions here:

You might try deleting /CacheVolume/upgrade in case it’s taking up too much space. Have a look to see what’s in it first; I suspect it’s intended to be a temporary folder to hold the update images during the update process, and not hold any other system files, but I don’t know that…


#12

I finally managed to fix the problem. I found the answer in this post. I just bound /DataVolume/cache at /CacheVolume with

mount --bind /DataVolume/cache /CacheVolume

and then started the update process and it worked! Now the storage is working again and I have full access to all my files.

Thank you rac8006 and cpt_paranoia for your time and help!

Alex


How recover firmware