Hard disk is still running through

  • I have already discussed this topic under How do I prevent hard drives from running when they are not needed? .


    It still does not work.

    I have set my 6 element hard disks under "Data storage => File systems=> Edit" from Advanced Power Management = 127 to 255 and the disks are still running through.


    The spin down time is 10 minutes and the smart check interval is 4500 and the power mode is on standby.



    Here is my system:


    inxi -Fxxxz


    System:

    Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 console: pty pts/0

    Distro: openmediavault 7.0.2-2 (Sandworm) Base: Debian GNU/Linux 12 (Bookworm)

    Computer:

    Type: Desktop System: WYSE Product: Z CLASS v: Rev 1 serial: <Superuser required>

    Chassis: Inventec Type: 15 v: A serial: <Superuser required>

    Mobo: Inventec Model: Z CLASS v: A02 serial: <superuser required> UEFI: Phoenix v: F3.0B

    Date: 29/10/2012

    CPU:

    Info: Dual-core model: AMD G-T56N Bits: 64 type: MCP smt: <unsupported> arch: Bobcat rev: 0

    Cache: L1: 128 KiB L2: 1024 KiB

    Speed (MHz): avg: 1354 high: 1646 min/max: N/A Cores: 1: 1646 2: 1062 bogomips: 6585

    Flags: ht lm nx pae sse sse2 sse3 sse4a ssse3 svm

    Graphics:

    Device-1: AMD Wrestler [Radeon HD 6320] Driver: radeon v: kernel arch: TeraScale-2 Ports:

    active: DVI-D-1 empty: DP-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:9806 class-ID: 0300

    Display: Server: No display server data found. Headless machine? tty: 185x26

    Monitor-1: DVI-D-1 Model: LG (GoldStar) L226WTQ serial: <filter> res: 1680x1050 dpi: 87

    Size: 474x296mm (18.66x11.65") diag: 585mm (23") Modes: max: 1680x1050 min: 720x400

    API: N/A Message: No display API data available in the console. Headless machine?

    Audio:

    Device-1: AMD Wrestler HDMI Audio Driver: snd_hda_intel v: kernel bus-ID: 00:01.1

    Chip ID: 1002:1314 Class ID: 0403

    API: ALSA v: k6.1.0-18-amd64 status: kernel-api

    Network:

    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:

    speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200

    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>

    IF-ID-1: cni-podman0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>

    IF-ID-2: vethdb11d118 state: up speed: 10000 Mbps duplex: full mac: <filter>

    Drives:

    Local Storage: total: 32.97 TiB used: 13.5 TiB (40.9%)

    ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB speed: 3.0 Gb/s

    type: SSD serial: <filter> rev: 04RL scheme: GPT

    ID-2: /dev/sdb type: USB vendor: Western Digital model: WD40EZRX-00SPEB0 size: 3.64 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1065 scheme: GPT

    ID-3: /dev/sdc type: USB vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1030 scheme: GPT

    ID-4: /dev/sdd type: USB vendor: Western Digital model: WD40EZRZ-22GXCB0 size: 3.64 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1019 scheme: GPT

    ID-5: /dev/sde type: USB vendor: Western Digital model: WD80EDAZ-11TA3A0 size: 7.28 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1030 scheme: GPT

    ID-6: /dev/sdf type: USB vendor: Western Digital model: WD80EMAZ-00WJTA0 size: 7.28 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1021 scheme: GPT

    ID-7: /dev/sdg type: USB vendor: Western Digital model: WD40EZRZ-22GXCB0 size: 3.64 TiB

    type: HDD rpm: 5400 serial: <filter> rev: 1021 scheme: GPT

    Partition:

    ID-1: / size: 217.57 GiB used: 10.47 GiB (4.8%) fs: ext4 dev: /dev/sda2

    ID-2: /boot/efi size: 511 MiB used: 148 KiB (0.0%) fs: vfat dev: /dev/sda1

    Swap:

    ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3

    Sensors:

    Src: /sys System Temperatures: cpu: 64.2 C mobo: N/A gpu: radeon temp: 67.0 C

    Fan Speeds (RPM): N/A

    Info:

    Processes: 182 Uptime: 6d 4h 16m wakeups: 1 Memory: 7.36 GiB used: 757 MiB (10.0%) Init: systemd

    v: 252 target: graphical (5) default: graphical Compilers: N/A Packages: pm: dpkg pkgs: 678

    Shell: sh running-in: pty pts/0 (SSH) inxi: 3.3.26


    Does anyone have any idea what could be causing the hard disks to cycle?


    Yours sincerely, R.Lehmeier



    Translated with DeepL.com (free version)

  • I've done everything I can think of, but I still have the same problem. The discs are still running.


    Now I found solutions for this in older postings. E.g. here :




    Now my question is whether this problem still exists or whether it has been solved in the meantime, or whether I really have to carry out these procedures for each disc.

  • Forget hdparm and just use hd-idle. Only hd-idle spins down harddrives reliably.


  • These postings were about hdparm and hd-idle getting in each other's way and therefore the parameters in the disks have to be switched off.


    Since my disks are constantly running and all previous attempts have failed, this was a possibility I was still considering.

    Why could the disks still be running - is there a way to read out the settings and post them here?


    Translated with DeepL.com (free version)

    • Neu
    • Offizieller Beitrag

    You can download hd-idle here:


    GitHub - adelolmo/hd-idle: Hard Disk Idle Spin-Down Utility
    Hard Disk Idle Spin-Down Utility. Contribute to adelolmo/hd-idle development by creating an account on GitHub.
    github.com


  • votdev

    Hat das Label OMV 7.x hinzugefügt.
  • The OMV changelog reads:

    Code
    openmediavault (7.0.4-2) stable; urgency=low
    
    
    * Replace hdparm with smartctl in UDEV helper script.

    Does this have anything to do with how drive spin downs are handled? If I am using the latest version of OMV and set up spin down times in the web UI, is this still done with hdparm? Or with smartctl? And if it has changed: Is hd-idle still the best option?

    Setting spin down times in the web ui doesn't seem to work with all of my drives...

    • Neu
    • Offizieller Beitrag

    Or with smartctl?

    yes



    Is hd-idle still the best option?

    if drives do not spin down with smartctl, try hd-idle


    however, there are other reasons why a drive does not spin down like access by some service like S.M.A.R.T if not configured properly

  • yes



    if drives do not spin down with smartctl, try hd-idle

    Thanks for confirming! I was going to give an update here: After I posted I found this issue and this commit, that showed that hdparm had been replaced by smartctl.

    I installed hd-idle last night and I am impressed. What had not been working before, works now with hd-idle apparently:

    One old WD drive that almost never gets used and that I couldn't get to spin down before, dropped its temperature from an average of 40° C to 25° C. All other drives are up to 10 degrees colder now. Even my 2 NVME-SSDs are about 3-5 degrees colder, probably because of the lower overall temperature. Everything, foremost the fans, is less noisy. I am very content. :)

    however, there are other reasons why a drive does not spin down like access by some service like S.M.A.R.T if not configured properly

    Thank you. I selected "Standby" in the S.M.A.R.T power settings. This should prevent spun down drives from being woken up, if I understand that correctly?

  • Today I had the chance to test whether the smart settings are responsible for this problem.

    When I turn them off, the disks do not start.

    When I turn them on (1800 seconds and standby) they run, when I turn off the smart settings the disks stay quiet.

    What do I have to set where so that the disks are polled without starting?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!