plugout.net

Confirming the bug.
I just updated the firmware on my Network Space 2 (2TB) and

Code: Select all

fvdw-sl firmware version 17-0

patched with

Code: Select all

fvdw-sl-17.0-patch07-01aug2018.zip(17-0-patch07.sh)

and

Code: Select all

fvdw-sl-17.0-update-kernel-21mar2018.zip(17-0-update-kernel.sh)

starts with "Power LED On" even though "Status: LED Off at next boot" is set (and vice versa).

Hi

Thank you for your feedback
I did not yet notice this topic...

I tried to reproduce your bug on my nwsp2 but without success : fvdw-sl 17.0 not patched and patched, with the regular kernel version 4.6.6#7 and also 4.6.6#26
In all case LED commands work right on my nwsp2 :scratch

But I noticed on the dmesg output it is a LaCie Network Space Lite v2 and my nwsp2 is a classic subversion.
Can you check if you have also a LaCie Network Space Lite v2 (https://plugout.net/viewtopic.php?f=11&t=213)

As when we work on versions 4.3.3/4.6.6, we need to fix an issue with LED on the nwsp2 maybe the fix it is not valid for the Lite subversion :scratch

Can you post also the output

Code: Select all

ls -Rl /sys/devices/platform/leds*/leds

Possibly I was wrong as now it simply stays on independently of the "LED On/Off at boot" setting.
I tried rebooting 6 times, 3 with "LED Off at next boot" and 3 with "LED On at next boot" and it always stayed on.
The "Power LED On"and "Power LED Off" switches work correctly.

I'd say, based on the images, that my Network Space 2 is the classic V2 version as I can clearly see an heat sink and not a nude chip.

After a reboot with "Status: LED Off at next boot" set , the LED is on and the output of the command is:

Code: Select all

root@fvdwsl-base:/ # ls -Rl /sys/devices/platform/leds*/leds
/sys/devices/platform/leds-gpio/leds:
total 0
drwxr-xr-x  3 root root 0 2018-10-10 01:36 ns_v2:red:fail

/sys/devices/platform/leds-gpio/leds/ns_v2:red:fail:
total 0
-rw-r--r--  1 root root 4096 2018-10-10 01:37 brightness
lrwxrwxrwx  1 root root    0 2018-10-10 01:38 device -> ../../../leds-gpio
-r--r--r--  1 root root 4096 2018-10-10 01:38 max_brightness
drwxr-xr-x  2 root root    0 2018-10-10 01:38 power
lrwxrwxrwx  1 root root    0 2018-10-10 01:38 subsystem -> ../../../../../class/leds
-rw-r--r--  1 root root 4096 2018-10-10 01:38 trigger
-rw-r--r--  1 root root 4096 2018-10-10 01:36 uevent

/sys/devices/platform/leds-gpio/leds/ns_v2:red:fail/power:
total 0
-rw-r--r--  1 root root 4096 2018-10-10 01:38 autosuspend_delay_ms
-rw-r--r--  1 root root 4096 2018-10-10 01:38 control
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_active_time
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_status
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_suspended_time

/sys/devices/platform/leds-ns2/leds:
total 0
drwxr-xr-x  3 root root 0 2018-10-10 01:36 ns_v2:blue:sata

/sys/devices/platform/leds-ns2/leds/ns_v2:blue:sata:
total 0
-rw-r--r--  1 root root 4096 2018-10-10 01:37 brightness
lrwxrwxrwx  1 root root    0 2018-10-10 01:38 device -> ../../../leds-ns2
-r--r--r--  1 root root 4096 2018-10-10 01:38 max_brightness
drwxr-xr-x  2 root root    0 2018-10-10 01:38 power
-rw-r--r--  1 root root 4096 2018-10-10 01:38 sata
lrwxrwxrwx  1 root root    0 2018-10-10 01:38 subsystem -> ../../../../../class/leds
-rw-r--r--  1 root root 4096 2018-10-10 01:37 trigger
-rw-r--r--  1 root root 4096 2018-10-10 01:36 uevent

/sys/devices/platform/leds-ns2/leds/ns_v2:blue:sata/power:
total 0
-rw-r--r--  1 root root 4096 2018-10-10 01:38 autosuspend_delay_ms
-rw-r--r--  1 root root 4096 2018-10-10 01:38 control
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_active_time
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_status
-r--r--r--  1 root root 4096 2018-10-10 01:38 runtime_suspended_time


Hi

type-a1pha wrote:Possibly I was wrong as now it simply stays on independently of the "LED On/Off at boot" setting.
I tried rebooting 6 times, 3 with "LED Off at next boot" and 3 with "LED On at next boot" and it always stayed on.
The "Power LED On"and "Power LED Off" switches work correctly.

Then it is not the same issue and maybe it is a known bug related with old fvdw-sl console versions when you installed the firmware
So open a shell terminal and do

Code: Select all

mkdir /tmp/sda7
mount /dev/sda7 /tmp/sda7
cat /tmp/sda7/etc/fvdwversion
cat /etc/boot.log
cat  /tmp/sda7/etc/boot.log


Now I assume you set the option "led off at next boot and you did manually a 'Power LED on', then do still on the shell terminal

Code: Select all

ls -l /rw_fs/etc/ledoffatboot
/etc/leds_bootup
/etc/leds_switch off    <----Here blue LED should be off
/etc/leds_switch on     <----Here blue LED should be on

So post all asked output and also the LED behaviour on the last commands

Code: Select all

root@fvdwsl-base:/ # mkdir /tmp/sda7
root@fvdwsl-base:/ # mount /dev/sda7 /tmp/sda7
root@fvdwsl-base:/ # cat /tmp/sda7/etc/fvdwversion
fvdw-sl 16.0
root@fvdwsl-base:/ # cat /etc/boot.log
cat: /etc/boot.log: No such file or directory
root@fvdwsl-base:/ # cat  /tmp/sda7/etc/boot.log
cat: /tmp/sda7/etc/boot.log: No such file or directory

Executing:

Code: Select all

/etc/leds_switch off    <----Here blue LED should be off
/etc/leds_switch on     <----Here blue LED should be on

works as intended.

Hi

I am sorrry, I made an error about the path to boot.log files.

So you have version 16.0 on sda7. Then I assume you have this know bug: https://plugout.net/viewtopic.php?f=7&t=2314

Should try to install the related patch

Jocko wrote:So you have version 16.0 on sda7. Then I assume you have this know bug: https://plugout.net/viewtopic.php?f=7&t=2314
Should try to install the related patch

Don't I have the 17.0 installed?

What is the purpose of version 16.0 on sda7?

Is it fine to install the patch for version 16.0 even though I have

Code: Select all

fvdw-sl firmware version 17-0

installed?

Yes you use 17.0 but:
-this version is installed on another partition sda1 or sda2
-sda7 contains the firmware version on the first install
-sda7 is required by the boot-loader to run the init script which later loads the firmware from sda1 or sda2

There is a known bug on the init script with version 15.3 and 16.0 which reproduces your issue.

As you have fvdw-sl 16.0 on sda7 and I think you did not install this patch when you used this version, you should try to install this patch which fixes the bug on the init script on sda7.

---edit---
I have splitted the topic as it is not the same issue as reported in http://plugout.net/viewtopic.php?f=11&t=2921which is related to a kernel issue on nwsp2 Lite platform

I confirm that the patch fixed the issue.
I should have checked the bugs section better.
Thank you for the support.