Raid 5 Laufwerke gehen nicht in denn Energiesparmodus / Raid 5 drives do not go into energy-saving mode

Other Languages Deutsch
1

Ich habe neulich 3 Hdd Festplatten in einem Raid 5 zusammen gepackt und ich habe nun fest gestellt das sie nicht in denn Standbye zustand fallen. Es läuft darauf kein Betriebssystem und ist für mich einfach ne Speicher Erweiterung. Laut Systemmonitor wird der Raid 5 immer wieder gelesen. Wenn ich aber mit lsof | grep Raid5_HDD auslesen lasse, kommt nichts. Erst wenn ich eine Datei von dort aus öffe. Auch wenn ich denn befehl gebe
sudo hdparm -S 30 /dev/md127
schlägt das leider fehl
/dev/md127:
setting standby to 30 (2 minutes + 30 seconds)
HDIO_DRIVE_CMD(setidle) failed: Inappropriate ioctl for device

Wichtig noch, der Rad 5 ist via Software erstellt worden, nicht via BIOS.
Wie kann ich dafür sorgen das sie in denn Standbye Modus gehen und nur dann starten wenn sie benötigt werden?

Raid Info:
Version : 1.2
Creation Time : Sat Nov 22 08:57:00 2025
Raid Level : raid5
Array Size : 46875267072 (43.66 TiB 48.00 TB)
Used Dev Size : 23437633536 (21.83 TiB 24.00 TB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Tue Nov 25 19:10:37 2025
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : resync
Name : Nanachi:MyRAID5Array (local to host Nanachi)
UUID : fe2507fe:41956e15:9fbee352:02e8182b
Events : 131240
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
3 8 49 2 active sync /dev/sdd1

EN
I recently put three HDD hard drives together in a RAID 5 array and have now noticed that they do not go into standby mode. There is no operating system running on them and they are simply a storage expansion for me. According to the system monitor, the RAID 5 is being read repeatedly. However, when I run lsof | grep Raid5_HDD, nothing comes up. Only when I open a file from there. Even when I enter the command sudo hdparm -S 30 /dev/md127, it unfortunately fails /dev/md127: setting standby to 30 (2 minutes + 30 seconds) HDIO_DRIVE_CMD(setidle) failed: Inappropriate ioctl for device

Importantly, the RAID 5 was created via software, not via BIOS. How can I ensure that they go into standby mode and only start when they are needed?

Raid Info:Version:
1.2 Creation Time: Sat Nov 22 08:57:00 2025 Raid Level: raid5 Array Size: 46875267072 (43.66 TiB 48.00 TB) Used Dev Size: 23437633536 (21.83 TiB 24.00 TB) Raid Devices: 3 Total Devices: 3 Persistence: Superblock is persistent Update Time: Tue Nov 25 19:10:37 2025 State: clean Active Devices: 3 Working Devices: 3 Failed Devices: 0 Spare Devices: 0 Layout: left-symmetric Chunk Size: 512KConsistency Policy: resync Name: Nanachi:MyRAID5Array (local to host Nanachi) UUID: fe2507fe:41956e15:9fbee352:02e8182b Events: 131240 Number Major Minor RaidDevice State 0 8 17 0 active sync /dev/sdb1 1 8 33 1 active sync /dev/sdc1 3 8 49 2 active sync /dev/sdd1

2

Das Problem habe ich auch mit meinen Datengräbern.

Ich nutze zur Zeit deswegen eine udev Regel

/etc/udev/rules.d/69-hdparm.rules

ACTION=="add|change", KERNEL=="sd[c-e]", ATTRS{queue/rotational}=="1", RUN+="/usr/bin/hdparm -S 60 /dev/%k"

Heißt alle Laufwerke die rotieren ( ATTRS{queue/rotational}==“1”) und die mit sd(x) (sd[c-e] bei mir /dev/sdc-/dev/sde) gehen nach 5 Minuten nach dem Start in den Standby ( -S 60 ) (60 = 5min)

Ob das jetzt die perfekte Lösung ist, weiß ich nicht. Aber sie funktioniert. Vor allen laufen die Platten nicht wieder an wenn der Controller abgefragt wird.

Über Dolphin kann ich die Platten erwecken. qbittorrent schafft es nicht.

Wer eine bessere Lösung kennt, immer her damit.

4

Leider hat das nicht bei mir funktioniert.

5

Hast du es über die uuid versucht ?

hdparm -S 60 /dev/disk/by-uuid/fe2507fe:41956e15:9fbee352:02e8182b
6

what kind/brand of discs are you using ? nas-discs are special and you must know how they want to be treated. an example: wd-red discs are not designed to spin down. they have to be always powered cause they need the temperature. spinning down will cool down the plates causing a shrinking of the plates and metal parts by lower temperatures. the effect is that it will cause read/write errors. this is already described in the manual but i’ve seen users that don’t care and wonder why they will cause trouble. for that reason different types of discs will ignore any action/command to spin down and users start asking:

7

These are Seagate Exos 24TB drives.

8

well that’s an information to work with. please search the internet for “linux seagate exos sleep mode”. you’ll find links like the one i will post at the end. please check the manual for this drives/brand. keep in mind that this drives have their own modes. as example the wd-red drives have their own energy-save modes running independent from any operating system. as example they use a special “parking-mode” to reduce power consumption. i’m convinced that seagate will use similar tricks. as i mentioned this is a hardware-related thing you have to sort out. but “seagate exos linux sleep mode” is a good search term to get more informations.

please pay attention: nas-drives are designed to run 24/7 but they aren’t designed to be used as ordinary drives with sleep-modes. it’s against their nature of design.

as example (not the solution):