fvdw-sl on WD My Cloud

[matt_max]

I cannot apply patch fvdw-sl-18.1-loginPlugout-v3-04jul2021.zip from this post. Error code:
Current System Status: Error: zip file inconsistent with your NAS

LED light is white after power on, then change color to blue during boot process and then it turns green when NAS is ready.

[Jocko]

I added information directly in the last fvdw's post

[Jocko]

I cannot apply patch fvdw-sl-18.1-loginPlugout-v3-04jul2021.zip from this post. Error code:
Current System Status: Error: zip file inconsistent with your NAS

LED light is white after power on, then change color to blue during boot process and then it turns green when NAS is ready.

Indeed when I built the patch your platform was not handled

So I go to rebuilt the patch (and include the fix for smarttool)

[Jocko]

new version of the patch for version 18.1 and 18.0 is available...

[matt_max]

New patch applied successfully and now I can install minidlna without any problems.
I have noticed one strange behavior: when I turn the nas off (by poweroff) and remove the power cord and then try to power it on again led light turns white for a while and then turns off completly. I have to remove power
cord and reconnect it. Then NAS turns on normally.

[Jocko]

So another point solved but did you try it again :

[*]update smart db cannot be done:
/usr/sbin/update-smart-drivedb: download from trunk failed (HTTP error)

[matt_max]

Ok. After applying patch fvdw-sl-18.1-loginPlugout-v3-16oct2022.zip I can update smarttool database:

Code: Select all

root@fvdwsl-base:/ # /usr/sbin/update-smart-drivedb -v
Download from branches/RELEASE_6_3_DRIVEDB
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  233k    0  233k    0     0   293k      0 --:--:-- --:--:-- --:--:--  306k
/usr/share/smartmontools/drivedb.h is already up to date
root@fvdwsl-base:/ #


[Jocko]

Hi

So this issue is also fixed.

I would like to investigate on led command side.

So can you post these outputs

Code: Select all

ls -alR /sys/class/leds

and also

Code: Select all

grep '' /sys/class/leds/*
grep '' /sys/class/leds/*/*
grep '' /sys/class/leds/*/*/*

and report what is the current led status (on/off; color; blinking; ...)

[matt_max]

Output from ls -alR /sys/class/leds

Code: Select all

root@fvdwsl-base:/ # ls -alR /sys/class/leds
/sys/class/leds:
total 0
drwxr-xr-x   2 root root 0 2022-10-16 22:11 .
drwxr-xr-x  34 root root 0 2022-10-16 22:11 ..
lrwxrwxrwx   1 root root 0 2022-10-16 22:11 system_led -> ../../devices/virtual/leds/system_led
lrwxrwxrwx   1 root root 0 2022-10-16 22:12 wifi_led -> ../../devices/virtual/leds/wifi_led
root@fvdwsl-base:/ #


...and from grep command

Code: Select all

root@fvdwsl-base:/ # grep '' /sys/class/leds/*
root@fvdwsl-base:/ # grep '' /sys/class/leds/*/*
/sys/class/leds/system_led/blink:on
/sys/class/leds/system_led/brightness:0
/sys/class/leds/system_led/color:green
/sys/class/leds/system_led/max_brightness:255
/sys/class/leds/system_led/trigger:[none] nand-disk
/sys/class/leds/wifi_led/blink:on
/sys/class/leds/wifi_led/brightness:0
/sys/class/leds/wifi_led/color:off
/sys/class/leds/wifi_led/max_brightness:255
/sys/class/leds/wifi_led/trigger:[none] nand-disk
root@fvdwsl-base:/ # grep '' /sys/class/leds/*/*/*
root@fvdwsl-base:/ #


Now led is solid green - system is on and working.

[fvdw]

Do not use blink and brightness and trigger. The driver implemented by wd is buggy.
Using blink or brightness will cause kernel crash or oops
Only use color entry. If you echo "off" (without quotes) to /sys/class/leds/system_led/color the led will go out.