HDD spinning up every few seconds when Bluetooth device is connected

I am encountering a quite strange behavior on my HTPC/Storage-System running on Manjaro:
Whenever my Dualshock 4 Controller is connected via Bluetooth, one of the HDD spins up every few seconds. With the exact same conditions (same programs running, same hardware connected, etc.), but the controller disconnected, the issue does not happen.

Example from journalctl:

Mär 30 21:00:24 minimoose kernel: sd 0:0:0:0: [sda] Stopping disk
Mär 30 21:00:24 minimoose kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mär 30 21:00:05 minimoose kernel: sd 0:0:0:0: [sda] Starting disk
Mär 30 21:00:05 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 21:00:05 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 21:00:03 minimoose kernel: ata1.00: failed to enable DIPM, Emask 0x4
Mär 30 21:00:03 minimoose kernel: ata1.00: qc timeout (cmd 0xef)
Mär 30 20:59:58 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:59:58 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 20:50:24 minimoose kernel: sd 0:0:0:0: [sda] Stopping disk
Mär 30 20:50:24 minimoose kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mär 30 20:49:58 minimoose kernel: sd 0:0:0:0: [sda] Starting disk
Mär 30 20:49:58 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:49:58 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 20:40:24 minimoose kernel: sd 0:0:0:0: [sda] Stopping disk
Mär 30 20:40:24 minimoose kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mär 30 20:39:58 minimoose kernel: sd 0:0:0:0: [sda] Starting disk
Mär 30 20:39:58 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:39:58 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 20:30:24 minimoose kernel: sd 0:0:0:0: [sda] Stopping disk
Mär 30 20:30:24 minimoose kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mär 30 20:29:58 minimoose kernel: sd 0:0:0:0: [sda] Starting disk
Mär 30 20:29:58 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:29:58 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 20:20:24 minimoose kernel: sd 0:0:0:0: [sda] Stopping disk
Mär 30 20:20:24 minimoose kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mär 30 20:20:05 minimoose kernel: sd 0:0:0:0: [sda] Starting disk
Mär 30 20:20:05 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:20:05 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mär 30 20:20:03 minimoose kernel: ata1.00: failed to enable DIPM, Emask 0x4
Mär 30 20:20:03 minimoose kernel: ata1.00: qc timeout (cmd 0xef)
Mär 30 20:19:58 minimoose kernel: ata1.00: configured for UDMA/133
Mär 30 20:19:58 minimoose kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

When I first saw these messages, I assumed it could be an issue with the SATA xable, but there have been no changes in the cabling (or touching it) for the last year and there never was an issue with the HDD either. There were no active applications accessing the drive at the time of the log, eventhough there is a swap partition on the drive, swapping off did not change anything. (The swap on the drive was empty at the time)
Also, the HDD works fine with the Bluetooth device detached, smartctl does not show any issues with the drive either.

Full System information (with Bluetooth device detached):
inxi:

System:
  Kernel: 5.15.28-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=4685225b-83f7-4a5b-a0a6-2664a497097f rw iommu=pt quiet
    apparmor=1 security=apparmor udev.log_priority=3
  Console: pty pts/2 DM: GDM v: 41.3 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B450M-A v: Rev X.0x
    serial: <filter> UEFI: American Megatrends v: 2803 date: 01/15/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 17.47 GiB used: 2.99 GiB (17.1%)
  Array-1: capacity: 128 GiB slots: 4 EC: None max-module-size: 32 GiB
    note: est.
  Device-1: DIMM_A1 size: 8 GiB speed: 2133 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: Kingston part-no: KHX2133C14/8G
    serial: <filter>
  Device-2: DIMM_A2 size: 8 GiB speed: 2133 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: Kingston part-no: KHX2133C14/8G
    serial: <filter>
  Device-3: DIMM_B1 size: No Module Installed
  Device-4: DIMM_B2 size: 4 GiB speed: 2133 MT/s type: DDR4
    detail: synchronous unbuffered (unregistered) bus-width: 64 bits
    total: 64 bits manufacturer: G-Skill part-no: F4-2800C15-4GVRB serial: N/A
CPU:
  Info: model: AMD Ryzen 5 3400G with Radeon Vega Graphics socket: AM4
    bits: 64 type: MT MCP arch: Zen/Zen+ note: check family: 0x17 (23)
    model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
    desc: 1x4 MiB
  Speed (MHz): avg: 1400 min/max: 1400/3700 boost: enabled
    base/boost: 3700/4200 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.5 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400
    5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 59115
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb cpuid
    cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid
    fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm
    mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc
    nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse
    pse36 rapl rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni skinit smap
    smca sme smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock
    syscall tce topoext tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme
    vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 09:00.0
    chip-ID: 1002:15d8 class-ID: 0300
  Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.0
    compositor: gnome-shell driver: X: loaded: amdgpu gpu: amdgpu tty: 105x47
  Monitor-1: HDMI-A-1 model: Samsung serial: <filter> built: 2017
    res: 3840x2160 dpi: 76 gamma: 1.2 size: 1872x1053mm (73.7x41.46")
    diag: 1477mm (58.2") ratio: 16:9 modes: max: 3840x2160 min: 720x400
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Digital Devices GmbH Cine V7 driver: ddbridge v: 0.9.33-integrated
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: dd01:0006
    class-ID: 0480
  Device-2: AMD Raven/Raven2/Fenghuang HDMI/DP Audio
    vendor: ASUSTeK PRIME B450M-A driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK PRIME B450M-A
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 09:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.28-1-MANJARO running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: JACK v: 1.9.20 running: no
  Sound Server-4: PulseAudio v: 15.0 running: yes
  Sound Server-5: PipeWire v: 0.3.48 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 3-3.3:3 chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Supported mdraid levels: raid6 raid5 raid4
  Device-1: md127 maj-min: 9:127 type: mdraid level: raid-5 status: active
    state: clean size: 10.9 TiB
  Info: report: 4/4 UUUU blocks: 11706009600 chunk-size: 512k
    super-blocks: 1.2 algorithm: 2
  Components: Online:
  0: sda1 maj-min: 8:1 size: 3.63 TiB state: active sync
  1: sdb1 maj-min: 8:17 size: 3.63 TiB state: active sync
  4: sdc1 maj-min: 8:33 size: 3.63 TiB state: active sync
  5: sdd1 maj-min: 8:49 size: 3.63 TiB state: active sync
Drives:
  Local Storage: total: raw: 14.67 TiB usable: 11.04 TiB used: 10 TiB (90.6%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix
    model: HFM128GDHTNG-8510B size: 119.24 GiB block-size: physical: 512 B
    logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
    rev: 80010C00 temp: 43.9 C scheme: GPT
  SMART: yes health: PASSED on: 19d 5h cycles: 148
    read-units: 21,873,064 [11.1 TB] written-units: 8,483,064 [4.34 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000VN008-2DR166
    family: IronWolf size: 3.64 TiB block-size: physical: 4096 B logical: 512 B
    sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5980 serial: <filter> rev: SC60
    temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 27d 1h cycles: 131
    read: 57.22 TiB written: 19.22 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000VN008-2DR166
    family: IronWolf size: 3.64 TiB block-size: physical: 4096 B logical: 512 B
    sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5980 serial: <filter> rev: SC60
    temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 38d 12h cycles: 137
    read: 65.23 TiB written: 22.85 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
  ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000VN008-2DR166
    family: IronWolf size: 3.64 TiB block-size: physical: 4096 B logical: 512 B
    sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5980 serial: <filter> rev: SC60
    temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 38d 4h cycles: 141
    read: 57.56 TiB written: 27.86 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
  ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST4000NE0025-2EW107
    family: IronWolf Pro size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 7200
    serial: <filter> rev: EN02 temp: 34 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 2y 286d 8h cycles: 86
    read: 40.73 TiB written: 13.05 TiB Old-Age: g-sense error rate: 7097
    Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 27.94 GiB size: 27.38 GiB (97.98%) used: 20.19 GiB (73.8%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: 4685225b-83f7-4a5b-a0a6-2664a497097f
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 5.4 MiB (1.0%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1 label: N/A uuid: 7D94-F125
  ID-3: /home raw-size: 90.8 GiB size: 88.88 GiB (97.88%)
    used: 18.95 GiB (21.3%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p3
    maj-min: 259:3 label: N/A uuid: 606dfa0c-25e4-4c09-b055-1af6d663efbd
  ID-4: /store raw-size: 10.9 TiB size: 10.82 TiB (99.20%)
    used: 9.96 TiB (92.1%) fs: ext4 block-size: 4096 B dev: /dev/md127
    maj-min: 9:127 label: md1 uuid: ef218f40-5035-4f0f-9e6f-d7dfc97797ee
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4.66 GiB used: 3.8 MiB (0.1%)
    priority: -2 dev: /dev/sdc2 maj-min: 8:34 label: N/A
    uuid: 518e8d44-83bf-46de-8e0e-a5c6583dc0ca
  ID-2: swap-2 type: partition size: 4.66 GiB used: 0 KiB (0.0%)
    priority: -3 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: 4cae06bb-2b07-4ad2-bd1b-a577fdc4dde7
  ID-3: swap-3 type: partition size: 4.66 GiB used: 0 KiB (0.0%)
    priority: -4 dev: /dev/sdd2 maj-min: 8:50 label: N/A
    uuid: 00a6ed3f-3cdf-4a1f-b8bc-831f91596a5c
  ID-4: swap-4 type: partition size: 4.66 GiB used: 0 KiB (0.0%)
    priority: -5 dev: /dev/sdb2 maj-min: 8:18 label: N/A
    uuid: a79bd9e8-1709-4f3c-abee-5517293938f9
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-2:2 info: American Power Conversion Uninterruptible Supply
    type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
    power: 2mA chip-ID: 051d:0002 class-ID: 0300 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 3-3:2 info: VIA Labs VL813 Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    chip-ID: 2109:2813 class-ID: 0900
  Device-1: 3-3.3:3
    info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: Bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 0a12:0001 class-ID: e001
  Hub-5: 3-3.4:4 info: VIA Labs VL813 Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    chip-ID: 2109:2813 class-ID: 0900
  Device-1: 3-3.4.1:5 info: Future Devices FT232 Serial (UART) IC
    type: <vendor specific> driver: usbfs interfaces: 1 rev: 2.0 speed: 12 Mb/s
    power: 90mA chip-ID: 0403:6001 class-ID: 0000 serial: <filter>
  Device-2: 3-3.4.2:6 info: Future Devices FT232 Serial (UART) IC
    type: <vendor specific> driver: usbfs interfaces: 1 rev: 2.0 speed: 12 Mb/s
    power: 90mA chip-ID: 0403:6001 class-ID: 0000 serial: <filter>
  Device-3: 3-3.4.3:7 info: QinHeng CH340 serial converter
    type: <vendor specific> driver: ch341,ch341-uart interfaces: 1 rev: 1.1
    speed: 12 Mb/s power: 98mA chip-ID: 1a86:7523 class-ID: ff00
  Device-4: 3-3.4.4:8
    info: Shenzhen Rapoo E9260 Wireless Multi-mode Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 24ae:1813 class-ID: 0301
  Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 4-3:2 info: VIA Labs VL813 Hub ports: 4 rev: 3.0 speed: 5 Gb/s
    chip-ID: 2109:0813 class-ID: 0900
  Hub-8: 4-3.4:3 info: VIA Labs VL813 Hub ports: 4 rev: 3.0 speed: 5 Gb/s
    chip-ID: 2109:0813 class-ID: 0900
  Hub-9: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-10: 6-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 43.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 308 Uptime: 6d 16h 30m wakeups: 6 Init: systemd v: 250
  tool: systemctl Compilers: gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1468
  lib: 374 flatpak: 0 Shell: Bash (sudo) v: 5.1.16 running-in: pty pts/2
  inxi: 3.3.14

mhwd:

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI


Warning: No installed USB configs!

mhwd-kernel:

5.15.28-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux513
   * linux514
   * linux515

lsb_release:

ManjaroLinux 21.2.5 Qonos

lsblk:

NAME        FSTYPE     FSVER LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0                                                                                         
loop1                                                                                         
loop2                                                                                         
loop3                                                                                         
loop4                                                                                         
loop5                                                                                         
loop6                                                                                         
loop7                                                                                         
sda                                                                                           
├─sda1      linux_raid 1.2   debian-nas:1 8571c7ca-38c1-5d86-8be8-8ccf0ee16be8                
│ └─md127   ext4       1.0   md1          ef218f40-5035-4f0f-9e6f-d7dfc97797ee  320,1G    92% /store
└─sda2      swap       1                  4cae06bb-2b07-4ad2-bd1b-a577fdc4dde7                [SWAP]
sdb                                                                                           
├─sdb1      linux_raid 1.2   debian-nas:1 8571c7ca-38c1-5d86-8be8-8ccf0ee16be8                
│ └─md127   ext4       1.0   md1          ef218f40-5035-4f0f-9e6f-d7dfc97797ee  320,1G    92% /store
└─sdb2      swap       1                  a79bd9e8-1709-4f3c-abee-5517293938f9                [SWAP]
sdc                                                                                           
├─sdc1      linux_raid 1.2   debian-nas:1 8571c7ca-38c1-5d86-8be8-8ccf0ee16be8                
│ └─md127   ext4       1.0   md1          ef218f40-5035-4f0f-9e6f-d7dfc97797ee  320,1G    92% /store
└─sdc2      swap       1                  518e8d44-83bf-46de-8e0e-a5c6583dc0ca                [SWAP]
sdd                                                                                           
├─sdd1      linux_raid 1.2   debian-nas:1 8571c7ca-38c1-5d86-8be8-8ccf0ee16be8                
│ └─md127   ext4       1.0   md1          ef218f40-5035-4f0f-9e6f-d7dfc97797ee  320,1G    92% /store
└─sdd2      swap       1                  00a6ed3f-3cdf-4a1f-b8bc-831f91596a5c                [SWAP]
nvme0n1                                                                                       
├─nvme0n1p1 vfat       FAT32              7D94-F125                             505,6M     1% /boot/efi
├─nvme0n1p2 ext4       1.0                4685225b-83f7-4a5b-a0a6-2664a497097f    5,8G    74% /
└─nvme0n1p3 ext4       1.0                606dfa0c-25e4-4c09-b055-1af6d663efbd   65,4G    21% /home

free:

              gesamt       benutzt     frei      gemns.  Puffer/Cache verfügbar
Speicher:      17893        2616         168          76       15107       14858
Swap:          19071           4       19067

Has anyone experienced similar situations? How do I solve this other than not using a bluetooth device? I find it highly confusing that a bluetooth device influences a HDD.

Hi,

I had a similar behaviour, where /dev/sda went to sleep after a few seconds and spinned up after not long time again.

I found, that the value of auto-suspend delay only of /dev/sda was set to a low value of 15 seconds.
With this setting the disk was stopped after short time of running and led to a lot of disk spin ups.

The actual setting for auto-suspend delay can be found here:

cat /sys/block/sda/device/power/autosuspend_delay_ms

Other HDDs had greater suspend values and I never found, where the initial small value for /dev/sda has been set from.
I created a udev rule for changing auto suspend value of HDDs, but actual it seems that another setting disabled power management for all HDDs.
Because of home directory on this disk disabling of power management this is fine for me. For me it was important, to avoid the often start/stop cycle of the HDD.

Maybe you want to have, that your disks are more in sleeping state, but then I don’t understand, why you have also a swap partition on every of your sd? disks.

From my point of view this also can be a reason, why the disk does avoid sleeping state.

At following links information is available regarding power management of hdds, also for creating of udev rules for changing settings:
Power Management
hdparm - power management
Runtime Device Power Management

1 Like

Thank you very much for that input. I checked, and indeed, sda has a autosuspend_delay_ms of 15000 while all the other drives are set at -1. I do not know what set this. I will try your suggestions on adjusting the power settings.
Also, digging deeper into this, it seems that for /dev/sda, the advanced power management feature is set to 254, so does not allow spindown. the other drives are configured to 128.

I have reconfigured this so all drives have the same settings and will keep a watch on it. from a quick test at least, the drive seems to do what it should now, though. Fingers crossed.

What I still do not understand is the connection to the bluetooth device since I do not see this behaviour at all when the no bluetooth device is connected. This is really strange, but perhaps the bluetooth connection interfers with the power states somehow and influences the HDD behaviour?

Regarding your question about the swap, simply put, I do not want to put swap on the SSD. When I initially set up the RAID5 on the 4 disks, I kept some space for backups, but never ended up actually using it as such so I decided to use it as swap instead after I ran into some out of memory issues when working without swap. I also upgraded the RAM since, but just to be save, I kept the swap partitions enabled.

setting the autosuspend_delay_ms indeed solves the problem. Now I only have to figure out how to make that permanent.

Still, the connection between the bluetooth device and the HDD is not clear to me. Maybe it is coupled to the battery charge of the BT device that somehow influences the power management system, making it think we are running on battery? But the system is running with an UPC so already sees another battery and does not hot have any issues with that. Very strange behavior.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.