Hi
I have some trouble with the Spindown/Spinup using HD-Idle.
I used this Guide for install hd-idle ->
[How-To] Spin-down hard drives with hd-idle
hdparm is disabled.
Every time after a reboot of the Raspberry Pi 4 the spindown works fine but after 20-30 minutes the HDD's, 2x 2TB Seagate Barracuda
ST2000DM008 in an Icy Box IB-RD3621U3, have a spinup on its own without any access at the HDD's from my site,
but in the status is most showing still spindown
(the -i 320 is just for trying)
Status after reboot and the HDD's are correctly in the spindown:
pi@raspberrypi:~ $ sudo service hd-idle status
● hd-idle.service - hd-idle - spin down idle hard disks
Loaded: loaded (/lib/systemd/system/hd-idle.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-07-29 14:28:13 CEST; 23min ago
Docs: man:hd-idle(8)
Main PID: 699 (hd-idle)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/hd-idle.service
└─699 /usr/sbin/hd-idle -i 320 -l /var/log/hd-idle.log
Jul 29 14:28:13 raspberrypi systemd[1]: Started hd-idle - spin down idle hard disks.
Jul 29 14:28:14 raspberrypi hd-idle[699]: symlinkPolicy=0, defaultIdle=320, defaultCommand=scsi, debug=false, logFile=/v
Jul 29 14:35:31 raspberrypi hd-idle[699]: sdb spindown
Jul 29 14:35:32 raspberrypi hd-idle[699]: sda spindown
Alles anzeigen
Status show sda in spinup and sdb in spindown but both are in spinup on its own
pi@raspberrypi:~ $ sudo service hd-idle status
● hd-idle.service - hd-idle - spin down idle hard disks
Loaded: loaded (/lib/systemd/system/hd-idle.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-07-29 14:28:13 CEST; 32min ago
Docs: man:hd-idle(8)
Main PID: 699 (hd-idle)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/hd-idle.service
└─699 /usr/sbin/hd-idle -i 320 -l /var/log/hd-idle.log
Jul 29 14:28:13 raspberrypi systemd[1]: Started hd-idle - spin down idle hard disks.
Jul 29 14:28:14 raspberrypi hd-idle[699]: symlinkPolicy=0, defaultIdle=320, defaultCommand=scsi, debug=false, logFile=/v
Jul 29 14:35:31 raspberrypi hd-idle[699]: sdb spindown
Jul 29 14:35:32 raspberrypi hd-idle[699]: sda spindown
Jul 29 15:00:33 raspberrypi hd-idle[699]: sda spinup
Alles anzeigen
A few minutes later sda is shown as spindown again but its still in spinup
pi@raspberrypi:~ $ sudo service hd-idle status
● hd-idle.service - hd-idle - spin down idle hard disks
Loaded: loaded (/lib/systemd/system/hd-idle.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-07-29 14:28:13 CEST; 39min ago
Docs: man:hd-idle(8)
Main PID: 699 (hd-idle)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/hd-idle.service
└─699 /usr/sbin/hd-idle -i 320 -l /var/log/hd-idle.log
Jul 29 14:28:13 raspberrypi systemd[1]: Started hd-idle - spin down idle hard disks.
Jul 29 14:28:14 raspberrypi hd-idle[699]: symlinkPolicy=0, defaultIdle=320, defaultCommand=scsi, debug=false, logFile=/v
Jul 29 14:35:31 raspberrypi hd-idle[699]: sdb spindown
Jul 29 14:35:32 raspberrypi hd-idle[699]: sda spindown
Jul 29 15:00:33 raspberrypi hd-idle[699]: sda spinup
Jul 29 15:06:33 raspberrypi hd-idle[699]: sdb spinup
Jul 29 15:06:33 raspberrypi hd-idle[699]: sda spindown
Alles anzeigen
My /etc/default/hd-idle:
# defaults file for hd-idle
# start hd-idle automatically?
START_HD_IDLE=true
# hd-idle command line options
# Options are:
# -a <name> Set device name of disks for subsequent idle-time
# parameters (-i). This parameter is optional in the
# sense that there's a default entry for all disks
# which are not named otherwise by using this
# parameter. This can also be a symlink
# (e.g. /dev/disk/by-uuid/...)
# -i <idle_time> Idle time in seconds.
# -c <command_type> Api call to stop the device. Possible values are "scsi"
# (default value) and "ata".
# -s symlink_policy Set the policy to resolve symlinks for devices.
# If set to "0", symlinks are resolve only on start.
# If set to "1", symlinks are also resolved on runtime
# until success. By default symlinks are only resolve on start.
# If the symlink doesn't resolve to a device, the default
# configuration will be applied.
# -l <logfile> Name of logfile (written only after a disk has spun
# up). Please note that this option might cause the
# disk which holds the logfile to spin up just because
# another disk had some activity. This option should
# not be used on systems with more than one disk
# except for tuning purposes. On single-disk systems,
# this option should not cause any additional spinups.
#
# Options not exactly useful here:
# -t <disk> Spin-down the specified disk immediately and exit.
# -d Debug mode. It will print debugging info to
# stdout/stderr (/var/log/syslog if started as with systemctl)
# -h Print usage information.
HD_IDLE_OPTS="-i 320 -l /var/log/hd-idle.log"
Alles anzeigen
the status-all
pi@raspberrypi:~ $ service --status-all
[ + ] alsa-utils
[ - ] anacron
[ + ] avahi-daemon
[ + ] bluetooth
[ + ] chrony
[ - ] collectd
[ - ] console-setup.sh
[ - ] cpufrequtils
[ + ] cron
[ + ] dbus
[ + ] dphys-swapfile
[ + ] fake-hwclock
[ + ] hd-idle
[ - ] hwclock.sh
[ - ] keyboard-setup.sh
[ + ] kmod
[ - ] loadcpufreq
[ - ] lvm2
[ - ] lvm2-lvmpolld
[ - ] mdadm
[ - ] mdadm-waitidle
[ + ] monit
[ + ] networking
[ - ] nfs-common
[ + ] nfs-kernel-server
[ + ] nginx
[ - ] nmbd
[ - ] paxctld
[ + ] php7.3-fpm
[ - ] postfix
[ + ] procps
[ - ] proftpd
[ - ] quota
[ - ] quotarpc
[ + ] raspi-config
[ ? ] rng-tools
[ + ] rpcbind
[ - ] rrdcached
[ - ] rsync
[ + ] rsyslog
[ - ] salt-minion
[ - ] samba-ad-dc
[ + ] smartmontools
[ - ] smbd
[ + ] ssh
[ - ] sudo
[ + ] sysstat
[ + ] triggerhappy
[ + ] udev
[ + ] watchdog
[ - ] wd_keepalive
Alles anzeigen
Installed in OMV are the extras (enable) and autoshutdown (disable), only NFS and SSH is activ.
APM is also disabled.
After going in the spinup, no matter whether it is displayed or not, they never go in the spindown again until
I make a reboot of the Raspberry.
Why are the system going on its own in the spinup? Whats wrong?
Regards
Holger