Fan control?

[fvdw]

I think this is because disks are spinning in "NAS Standby WOL" state.

:scratch strange they shouldn't spin in WOL state.
Did they not spin before installing fan controller?
(Ps fan controller has no influence on WOL procedure meaning the reason why disk keep spinning must be something else. I must have a closer look to WOL procedure)

[fvdw]

The problem seems to come from modified rcS file that Jocko prepared.
I will talk with him to see how we can correct it and keep the new functionality

[jaker]

The problem seems to come from modified rcS file that Jocko prepared.

@Jocko and @fvdw have you had time to take a look on this rcS file for the reason why disks spin up in standby with wake on lan?

[Jocko]

Hi

Yes we have deepened the issue but we do not understand the behaviour of your nas. It is not my last change which occurs it or it is the fact to run the fan daemon during the WOL standby but this is an old change.

Currently we have a talking how we may check what happens during this standby state. So wait a bit time for next instructions.

[jaker]

Ok thank you. Please let me know if I can provide any further details.

[jaker]

Hi
I just noticed that another Lacie NAS that I have, 1 disk model "Network Space 2" with firmware version 18-2 keeps the blue LED on also in Standby with WOL. That one does not have fan at all and it does keep the disks off/not spinning.

This one with fan and fan control daemon is 2 disk model "Network Space MAX". The MAX with fan has LED off in standby with WOL state.

[Jocko]

Hi Jaker

According with this topic https://plugout.net/viewtopic.php?f=28&t=3383&p=33752#p33752 I am testing a patch which fixes similar issues as yours.
So you have to still wait a bit :whistle

[Jocko]

Hi Jaker

Thank to serram we detected some issues which may prevent the disk from spinning down. By fixing them, my last test when I perform a wol standby on my nwsp2 all works as expected: led off and disk stays down.

Then we have edited the init rcS for trying to have some more information when the nas is in wol standby state. (the file rcS.diskmon)
This version runs a daemon to trace I/O activity and when you wake up the nas the logs are stored in the folder /diskmon.hh-mm-ss (hh-mm-ss is the time where you wake up the nas)

So install the new files:

Code: Select all

plugout download 6523
tar -xf /tmp/fvdw-sl-18-x-fix-noatime-samba-21sep2020.tgz -C /

and you have to reboot the nas for fixing the issues on system partition and samba.
After restarting, please to post the output

Code: Select all

mount
ls -al /usr/samba/private/

(You should see all fs are now mounted with the option 'noatime')
if you run

Code: Select all

ls -al /etc/init.d/rcS*

you should see three files: rcS; rcS.diskmon and rcS.back
Then :
- enable the diskmon daemon on wol standby

Code: Select all

cp -p /etc/init.d/rcS.diskmon /etc/init.d/rcS
chmod 755 /etc/init.d/rcS

- Perform a WoL standby on your nwspmax
- Wait at least one hour for waking-up the nas (note: disk may stay up at the beginning).
You should see now a folder /diskmon.hh-mm-ss and post the folder log1 and log2 if this one is not empty

Warning: if you wake up the nas by pushing the power button, the folder /diskmon.hh-mm-ss won't be created and no information will be available. So you have to wake-up the nas only by sending a wol magic paquet

if later you want to restore the init script (remove the diskmon daemon on WoL standby),

Code: Select all

cp -p /etc/init.d/rcS.back /etc/init.d/rcS
chmod 755 /etc/init.d/rcS

Note: you can also install the patch on your nwps2 if there is no issue with your nwspmax

[jaker]

...
So install the new files:

Code: Select all

plugout download 6523
tar -xf /tmp/fvdw-sl-18-x-fix-noatime-samba-21sep2020.tgz -C /

and you have to reboot the nas for fixing the issues on system partition and samba.
After restarting, please to post the output

Code: Select all

mount
ls -al /usr/samba/private/

(You should see all fs are now mounted with the option 'noatime')
if you run

Code: Select all

ls -al /etc/init.d/rcS*

you should see three files: rcS; rcS.diskmon and rcS.back
...

Here you go

Code: Select all

root@ZENfvdwsl-base:/ # mount
/dev/sda1 on / type ext3 (rw,noatime,data=ordered)
none on /proc type proc (rw,noatime)
none on /sys type sysfs (rw,noatime)
none on /dev/pts type devpts (rw,noatime,mode=600,ptmxmode=000)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,noatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,noatime)
/dev/md0 on /share/1100 type ext4 (rw,noatime,nodelalloc,stripe=256,data=ordered)
/dev/sda7 on /lacie-boot type ext3 (rw,relatime,data=ordered)
root@ZENfvdwsl-base:/ # ls -al /usr/samba/private/
total 0
drwxr-xr-x  3 root root 200 2020-09-22 19:31 .
drwxr-xr-x  3 root root  60 2020-09-22 19:30 ..
lrwxrwxrwx  1 root root  33 2020-09-22 19:30 hkcr.ldb -> /rw_fs/usr/samba/private/hkcr.ldb
lrwxrwxrwx  1 root root  33 2020-09-22 19:30 hkcu.ldb -> /rw_fs/usr/samba/private/hkcu.ldb
lrwxrwxrwx  1 root root  33 2020-09-22 19:30 hklm.ldb -> /rw_fs/usr/samba/private/hklm.ldb
lrwxrwxrwx  1 root root  32 2020-09-22 19:30 hku.ldb -> /rw_fs/usr/samba/private/hku.ldb
drwx------  2 root root 340 2020-09-22 19:31 msg.sock
lrwxrwxrwx  1 root root  36 2020-09-22 19:30 secrets.ldb -> /rw_fs/usr/samba/private/secrets.ldb
lrwxrwxrwx  1 root root  36 2020-09-22 19:30 secrets.tdb -> /rw_fs/usr/samba/private/secrets.tdb
lrwxrwxrwx  1 root root  34 2020-09-22 19:30 smbpasswd -> /rw_fs/usr/samba/private/smbpasswd
root@ZENfvdwsl-base:/ # ls -al /etc/init.d/rcS*
-rwxr-xr-x  1 root root 37656 2020-09-20 19:08 /etc/init.d/rcS
-rwxr-xr-x  1 root root 37656 2020-09-20 19:08 /etc/init.d/rcS.back
-rwxr-xr-x  1 root root 38360 2020-09-20 19:09 /etc/init.d/rcS.diskmon
-rwxr-xr-x  1 root root 35678 2020-08-04 23:17 /etc/init.d/rcS.org
root@ZENfvdwsl-base:/ #


[Jocko]

So all is ok now and you can now check what happens when you perform a wol standy.

So you may overwrite the current file rcS by rcS.diskmon like detailed previously and standby the nas