Standby Mode NSA325

[derminator]

Hello,

at the moment I am using the following Kernel 3.16.7-1-ARCH. I have measured the power consumption, which is
about 18W all the time. Nobody is accessing the server. But the NSA325 did not enter the standby mode.

Is it possible to configure the NSA325 so, that after a certain time the standby mode is entered.

Here these processes are running:

root 1 0 0 15:46 ? 00:00:02 /sbin/init
root 2 0 0 15:46 ? 00:00:00 [kthreadd]
root 3 2 0 15:46 ? 00:00:00 [ksoftirqd/0]
root 5 2 0 15:46 ? 00:00:00 [kworker/0:0H]
root 7 2 0 15:46 ? 00:00:00 [rcu_preempt]
root 8 2 0 15:46 ? 00:00:00 [rcu_sched]
root 9 2 0 15:46 ? 00:00:00 [rcu_bh]
root 10 2 0 15:46 ? 00:00:00 [khelper]
root 11 2 0 15:46 ? 00:00:00 [kdevtmpfs]
root 12 2 0 15:46 ? 00:00:00 [netns]
root 13 2 0 15:46 ? 00:00:00 [khungtaskd]
root 14 2 0 15:46 ? 00:00:00 [writeback]
root 15 2 0 15:46 ? 00:00:00 [ksmd]
root 16 2 0 15:46 ? 00:00:00 [crypto]
root 17 2 0 15:46 ? 00:00:00 [kintegrityd]
root 18 2 0 15:46 ? 00:00:00 [bioset]
root 19 2 0 15:46 ? 00:00:00 [kblockd]
root 20 2 0 15:46 ? 00:00:00 [ata_sff]
root 21 2 0 15:46 ? 00:00:00 [khubd]
root 22 2 0 15:46 ? 00:00:00 [kworker/0:1]
root 25 2 0 15:46 ? 00:00:00 [kswapd0]
root 26 2 0 15:46 ? 00:00:00 [fsnotify_mark]
root 39 2 0 15:46 ? 00:00:00 [scsi_eh_0]
root 40 2 0 15:46 ? 00:00:00 [scsi_tmf_0]
root 41 2 0 15:46 ? 00:00:00 [scsi_eh_1]
root 42 2 0 15:46 ? 00:00:00 [scsi_tmf_1]
root 43 2 0 15:46 ? 00:00:00 [kworker/u2:1]
root 45 2 0 15:46 ? 00:00:00 [kworker/u2:3]
root 50 2 0 15:46 ? 00:00:00 [deferwq]
root 51 2 0 15:46 ? 00:00:00 [jbd2/sda2-8]
root 52 2 0 15:46 ? 00:00:00 [ext4-rsv-conver]
root 53 2 0 15:46 ? 00:00:00 [ipv6_addrconf]
root 63 2 0 15:46 ? 00:00:00 [kworker/0:1H]
root 68 2 0 15:46 ? 00:00:00 [kworker/0:2]
root 78 1 0 15:46 ? 00:00:00 /usr/lib/systemd/systemd-journal
root 93 1 0 15:46 ? 00:00:00 /usr/lib/systemd/systemd-udevd
root 109 2 0 15:46 ? 00:00:00 [mv_crypto]
root 127 1 0 15:46 ? 00:00:00 /usr/bin/crond -n
root 129 1 0 15:46 ? 00:00:00 /usr/lib/systemd/systemd-logind
dbus 130 1 0 15:46 ? 00:00:00 /usr/bin/dbus-daemon --system --
root 131 1 0 15:46 ? 00:00:01 /usr/bin/haveged -w 1024 -v 1
systemd+ 132 1 0 15:46 ? 00:00:00 /usr/lib/systemd/systemd-network
systemd+ 138 1 0 15:46 ? 00:00:00 /usr/lib/systemd/systemd-resolve
root 141 1 0 15:46 ? 00:00:00 /usr/bin/sshd -D
root 142 1 0 15:46 tty1 00:00:00 /sbin/agetty --noclear tty1 linu
root 143 1 0 15:46 ttyS0 00:00:00 /sbin/agetty --keep-baud 115200
ntp 144 1 0 15:46 ? 00:00:00 /usr/bin/ntpd -g -u ntp:ntp
root 146 1 0 15:46 ? 00:00:00 /usr/bin/nmbd -D
root 148 1 0 15:46 ? 00:00:00 /usr/bin/smbd -D
root 150 148 0 15:46 ? 00:00:00 /usr/bin/smbd -D
avahi 151 1 0 15:46 ? 00:00:00 avahi-daemon: running [NSA325.lo
avahi 152 151 0 15:47 ? 00:00:00 avahi-daemon: chroot helper
root 155 1 0 15:47 ? 00:00:00 /usr/bin/perl /opt/webmin/minise
root 175 141 0 15:49 ? 00:00:00 sshd: root@pts/0
root 177 1 0 15:49 ? 00:00:00 /usr/lib/systemd/systemd --user
root 178 177 0 15:49 ? 00:00:00 (sd-pam)
root 180 175 0 15:49 pts/0 00:00:00 -bash
root 239 2 0 16:02 ? 00:00:00 [kworker/0:0]
root 259 180 0 16:04 pts/0 00:00:00 ps -ef

The operating system is installed on sda. Maybe it will work to install the OS on USB stick?

[WarheadsSE]

I know that it can be configured to spin down, and WOL. I know this is working, but I have no documentation on that other than you need to make sure that the eth0 MAC is matching the one on the box.

[derminator]

So now I have monitored the HD activity

sudo iotop -Pao

Total DISK READ : 0.00 B/s | Total DISK WRITE : 0.00 B/s
Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s
PID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
51 be/3 root 0.00 B 232.00 K 0.00 % 0.13 % [jbd2/sda2-8]
78 be/4 root 0.00 B 4.00 K 0.00 % 0.00 % systemd-journald
146 be/4 root 0.00 B 16.00 K 0.00 % 0.00 % nmbd -D

Does anyone have an idea?

[summers]

If I had to guess, its becuase the OS is isntalled on the HDD. Probably means that the HDD is accessed enough that it never gets the chance to spin down.

IIRC the is a hdparm command that will instruct the HDDto spin down, but usually if you issue that to the disk with the OS on it - the OS crashes.

So yes, having the OS on a memory stick I guess would improve things.

Guess any easy way to test would be to copy the root fs to a usb stick, then to switch_root, then issue an hdparm -S whatever. Think if you do it this way, even if it goes wrong, you can easilly recover ... hmm maybe not - IIRC switch_root deletes the old rootfs - which is what you want when moving from an initramfs, but not in this case ....

[WarheadsSE]

Question for the OP:
Are we talking about actually going into standby, or just HDD spindown?