thomask77 / raid-sleep

Power down RAID disks after a specified timeout

Power down RAID disks after a specified timeout

This script can handle drives that don't work with hdparm -S because they lack power management features (like the popular WD RED series).

Also, all drives are powered up at the same time when an access to one of the drives is detected. This makes wake-up from standby a lot faster for RAID arrays, where the drives would wake up in sequence with normal hdparm power-down.

Requirements

• Tested on Debian 8.11 (jessie):
  • python3 >= 3.4.2
  • hdparm >= 9.43

Install

1. Edit raid-sleep.conf:
   • Use find /dev/disk/by-id and blkid to find out your disk IDs
2. Read(!) and Execute sudo ./install.sh
   • This will set up a systemd service to start the program

raid-sleep's Issues

Spindown / Spinup loop

Hello Thomas,

i'm using your tool on my tiny self-made nas. It worked very well, until i did a upgrade to bullseye. I'm not sure if only the update causes the issue, but i did not changed much.

The tool began to spinup the disks immediately after spindown. So i got a spindown/spinup loop on every timeout-cycle. I checked /proc/disktats and i could watch diskstats changing while hdparm did the spindown. I could not figure out, what service/tool did the access, maybe its my mdraid.

I build a simple workaround to prevent the spindown/spinup loop by simply adding a spinup delay to your code. Every time the tool detects a spinup event (on disktat change), it checks if the spindown was performed within the configured delaytime (defaulting to 3 secs, which seems to be enough) and skips any action in this case.
It contionously get the stats, so after this delay time it will check again if disktstats changed.

I'm not sure if it is good fix, but maybe other people have the same issue and can get helped with this

regards
Andreas

spinup-delay.patch.txt