sillywalks

I finally found the culprit. I was using a home assistant integration to connect to the unraid api and that was for whatever reason keeping the disks constantly spun up.

I think I will once again start with a fresh install and keep it as minimal as possible adding services one by one. Bit of a pain but I really want the drives to stay spun down what with electricity prices being high. It's still pretty strange that at one point it just started happening without me doing anything to the system. I can even see th exact moment in the power readout of the smart plug, and I was in bed at that time :)

That was indeed the first one to go but still the issue persists.

Spin up groups are disabled. So unfortunately not the issue. File activity plugin shows nothing whatsoever writing to the disk. Open files also draws a blank Installed plugins are: Community Apps Dynamix system temp File activity 2 GPU stats Intel GPU top Nvidia driver Tailscale Un-get Powertop (via un-get) Unraid connect User scripts That's it. I'll try disabling them one by one and see if one of them is the cause.

Unfortunately not. It's just one data drive an one parity drive. That's all. And both spin up immediately after being spun down. Docker and VM completely disabled and it still happens.

ok so after a few days without issues it has returned. I am still running a minimal setup and I have no idea why this issue is back. Here is the part of the log where it suddenly starts: Aug 30 12:11:17 Tower kernel: usb 1-7: reset low-speed USB device number 5 using xhci_hcd Aug 30 12:11:18 Tower kernel: usb 1-1.1: reset full-speed USB device number 4 using xhci_hcd Aug 30 12:11:18 Tower kernel: usb 1-1.3.1: reset full-speed USB device number 8 using xhci_hcd Aug 30 12:11:18 Tower kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd Aug 30 12:11:58 Tower kernel : x86/split lock detection: #AC: CPU 8/KVM/73515 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:58 Tower kernel: x86/split lock detection: #AC: CPU 2/KVM/73509 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:58 Tower kernel: x86/split lock detection: #AC: CPU 9/KVM/73516 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:58 Tower kernel: x86/split lock detection: #AC: CPU 0/KVM/73507 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:58 Tower kernel: x86/split lock detection: #AC: CPU 7/KVM/73514 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:58 Tower kernel: x86/split lock detection: #AC: CPU 10/KVM/73517 took a split_lock trap at address: 0x6199f100 Aug 30 12:11:59 Tower kernel: x86/split lock detection: #AC: CPU 1/KVM/73508 took a split_lock trap at address: 0x6199f100 Aug 30 12:12:02 Tower kernel: x86/split lock detection: #AC: CPU 13/KVM/73520 took a split_lock trap at address: 0x6199f100 Aug 30 12:12:02 Tower kernel: x86/split lock detection: #AC: CPU 4/KVM/73511 took a split_lock trap at address: 0x6199f100 Aug 30 12:12:03 Tower kernel: x86/split lock detection: #AC: CPU 12/KVM/73519 took a split_lock trap at address: 0x6199f100 Aug 30 12:12:04 Tower kernel: x86/split lock detection: #AC: CPU 11/KVM/73518 took a split_lock trap at address: 0x6199f100 Aug 30 12:22:30 Tower kernel: usb 1-7: reset low-speed USB device number 5 using xhci_hcd Aug 30 12:22:33 Tower kernel: usb 1-1.1: reset full-speed USB device number 4 using xhci_hcd Aug 30 12:22:33 Tower kernel: usb 1-1.3.1: reset full-speed USB device number 8 using xhci_hcd Aug 30 12:22:41 Tower kernel: ata8.00: Enabling discard_zeroes_data Aug 30 12:22:41 Tower kernel: sde: sde1 Aug 30 12:22:41 Tower kernel: br0: port 2(vnet0) entered disabled state Aug 30 12:22:41 Tower kernel: vnet0 (unregistering): left allmulticast mode Aug 30 12:22:41 Tower kernel: vnet0 (unregistering): left promiscuous mode Aug 30 12:22:41 Tower kernel: br0: port 2(vnet0) entered disabled state Aug 30 12:22:41 Tower kernel: usb 1-7: reset low-speed USB device number 5 using xhci_hcd Aug 30 12:22:42 Tower kernel: input: SZH usb keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:C0F4:04C0.0007/input/input16 Aug 30 12:22:42 Tower kernel: hid-generic 0003:C0F4:04C0.0007: input,hidraw0: USB HID v1.10 Keyboard [SZH usb keyboard] on usb-0000:00:14.0-7/input0 Aug 30 12:22:42 Tower kernel: input: SZH usb keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:C0F4:04C0.0008/input/input17 Aug 30 12:22:42 Tower kernel: input: SZH usb keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:C0F4:04C0.0008/input/input18 Aug 30 12:22:42 Tower kernel: hid-generic 0003:C0F4:04C0.0008: input,hidraw1: USB HID v1.10 Device [SZH usb keyboard] on usb-0000:00:14.0-7/input1 Aug 30 12:22:42 Tower elogind-daemon[1904]: Watching system buttons on /dev/input/event2 (SZH usb keyboard Consumer Control) Aug 30 12:22:42 Tower elogind-daemon[1904]: Watching system buttons on /dev/input/event1 (SZH usb keyboard) Aug 30 12:22:42 Tower elogind-daemon[1904]: Watching system buttons on /dev/input/event3 (SZH usb keyboard System Control) Aug 30 12:22:42 Tower kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd Aug 30 12:22:42 Tower kernel: usb 1-1.3.1: reset full-speed USB device number 8 using xhci_hcd Aug 30 12:22:42 Tower kernel: input: Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:04F2:0978.0009/input/input19 Aug 30 12:22:42 Tower kernel: hid-generic 0003:04F2:0978.0009: input,hidraw2: USB HID v1.11 Keyboard [Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard] on usb-0000:00:14.0-1.3.1/input0 Aug 30 12:22:42 Tower kernel: input: Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.4/0003:04F2:0978.000A/input/input20 Aug 30 12:22:42 Tower kernel: input: Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.4/0003:04F2:0978.000A/input/input21 Aug 30 12:22:42 Tower kernel: hid-generic 0003:04F2:0978.000A: input,hiddev96,hidraw3: USB HID v1.11 Device [Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard] on usb-0000:00:14.0-1.3.1/input4 Aug 30 12:22:42 Tower elogind-daemon[1904]: Watching system buttons on /dev/input/event4 (Thermaltake Tt eSPORTS Challenger Ultimate gaming keyboard) Aug 30 12:22:43 Tower kernel: usb 1-1.1: reset full-speed USB device number 4 using xhci_hcd Aug 30 12:22:43 Tower kernel: input: Logitech Gaming Mouse G502 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C332.000B/input/input23 Aug 30 12:22:43 Tower kernel: hid-generic 0003:046D:C332.000B: input,hidraw4: USB HID v1.11 Mouse [Logitech Gaming Mouse G502] on usb-0000:00:14.0-1.1/input0 Aug 30 12:22:43 Tower kernel: input: Logitech Gaming Mouse G502 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:046D:C332.000C/input/input24 Aug 30 12:22:43 Tower kernel: hid-generic 0003:046D:C332.000C: input,hiddev97,hidraw5: USB HID v1.11 Keyboard [Logitech Gaming Mouse G502] on usb-0000:00:14.0-1.1/input1 Aug 30 12:22:43 Tower elogind-daemon[1904]: Watching system buttons on /dev/input/event8 (Logitech Gaming Mouse G502 Keyboard) Aug 30 12:22:44 Tower kernel: ata8.00: Enabling discard_zeroes_data Aug 30 12:22:44 Tower kernel: sde: sde1 Aug 30 12:22:44 Tower kernel: vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none Aug 30 12:22:44 Tower kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none Aug 30 12:22:44 Tower kernel: ata8.00: Enabling discard_zeroes_data Aug 30 12:22:44 Tower kernel: sde: sde1 Aug 30 12:23:59 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/nvidia powersave hourly/script Aug 30 22:25:41 Tower webgui: Successful login user root from 10.10.10.116 Aug 30 22:27:11 Tower monitor_nchan: Stop running nchan processes Aug 30 23:12:28 Tower kernel: usb 1-1: USB disconnect, device number 2 Aug 30 23:12:28 Tower kernel: usb 1-1.1: USB disconnect, device number 4 Aug 30 23:12:28 Tower acpid: input device has been disconnected, fd 13 Aug 30 23:12:28 Tower kernel: usb 1-1.3: USB disconnect, device number 6 Aug 30 23:12:28 Tower kernel: usb 1-1.3.1: USB disconnect, device number 8 Aug 30 23:12:29 Tower acpid: input device has been disconnected, fd 11 Aug 30 23:12:29 Tower kernel: usb 2-1: USB disconnect, device number 2 Aug 30 23:12:29 Tower acpid: input device has been disconnected, fd 12 Aug 30 23:36:50 Tower monitor_nchan: Stop running nchan processes Aug 30 23:40:02 Tower emhttpd: read SMART /dev/sdb Aug 30 23:40:09 Tower emhttpd: read SMART /dev/sdc Aug 30 23:54:57 Tower emhttpd: spinning down /dev/sdb Aug 30 23:54:59 Tower emhttpd: read SMART /dev/sdb Aug 30 23:55:04 Tower emhttpd: spinning down /dev/sdc Aug 30 23:55:37 Tower emhttpd: read SMART /dev/sdc Aug 31 00:10:00 Tower emhttpd: spinning down /dev/sdb Aug 31 00:10:28 Tower emhttpd: read SMART /dev/sdb Aug 31 00:10:32 Tower emhttpd: spinning down /dev/sdc Aug 31 00:11:09 Tower emhttpd: read SMART /dev/sdc Aug 31 00:25:23 Tower emhttpd: spinning down /dev/sdb Aug 31 00:25:24 Tower emhttpd: read SMART /dev/sdb Aug 31 00:26:04 Tower emhttpd: spinning down /dev/sdc Aug 31 00:26:36 Tower emhttpd: read SMART /dev/sdc Aug 31 00:40:25 Tower emhttpd: spinning down /dev/sdb Aug 31 00:40:52 Tower emhttpd: read SMART /dev/sdb Aug 31 00:41:31 Tower emhttpd: spinning down /dev/sdc Aug 31 00:42:06 Tower emhttpd: read SMART /dev/sdc Aug 31 00:55:47 Tower emhttpd: spinning down /dev/sdb Aug 31 00:55:48 Tower emhttpd: read SMART /dev/sdb Aug 31 00:57:01 Tower emhttpd: spinning down /dev/sdc Aug 31 01:10:49 Tower emhttpd: spinning down /dev/sdb Aug 31 01:11:16 Tower emhttpd: read SMART /dev/sdb The complete log is in the attachment. Any idea whats going on? error log unraid

Sweet that worked. Drives stay spun down on the fresh system. Where do I go from here. Should I manually rebuild my setup? Because restoring the flash backup might reintroduce the problem?

Thanks. I'll try that and report back.

Yes I did that. Quite a few files open but none on the drives. All on the cache. :(

I rolled back to 6.12 and the issue persists. Can this somehow be related to hardware? So maybe the mainboard is not allowing spindown? I updated the bios to the latest version alread so that was no help. Any ideas how I can further debug this issue?

Thanks for the heads up. Here is the diagnostics. Edit: just checked, even in safe mode the drive spins up right after spindown. ministry-diagnostics-20250826-1558.zip

I just moved my small setup to a new machine (MSI H610m-e with i5 14600) and I'm having the issue that my drives immediately spin up after spinning down. Docker, VMs, appdata etc are all writing to the cache. Looking at file activity nothing is writing or reading to the disks. The log shows clearly that they immediately spin up. Even if I manually spin them down they spin right back up with no delay. I tried turning off docker and VMs but no change. I rarely write to the array (more archival nature) and would really love to keep it spun down to save energy. Any idea what could be going on here? Logs: Aug 26 07:53:05 ministry emhttpd: spinning down /dev/sdd Aug 26 07:53:06 ministry emhttpd: read SMART /dev/sdd Aug 26 07:53:44 ministry emhttpd: spinning down /dev/sde Aug 26 07:53:49 ministry emhttpd: read SMART /dev/sde Aug 26 08:06:47 ministry emhttpd: spinning down /dev/sdb Aug 26 08:06:48 ministry emhttpd: read SMART /dev/sdb Aug 26 08:08:07 ministry emhttpd: spinning down /dev/sdd Aug 26 08:08:09 ministry emhttpd: read SMART /dev/sdd Aug 26 08:08:48 ministry emhttpd: spinning down /dev/sde Aug 26 08:09:31 ministry emhttpd: read SMART /dev/sde

Just to go exploring I set the unassigned drive back to the incorrect read/write state (not slave read write) Currently its still running.

did you check the logs of your container? Is something strange going on (like with mine)

2022-06-26 21:37:04 Coral Temp: 39.80C 2022-06-26 21:37:19 Coral Temp: 39.80C 2022-06-26 21:37:34 Coral Temp: 39.80C 2022-06-26 21:37:49 Coral Temp: 39.80C 2022-06-26 21:38:04 Coral Temp: 39.80C 2022-06-26 21:38:19 Coral Temp: 39.80C 2022-06-26 21:38:34 Coral Temp: 39.80C 2022-06-26 21:38:49 Coral Temp: 40.05C 2022-06-26 21:39:04 Coral Temp: 39.80C 2022-06-26 21:39:19 Coral Temp: 40.05C 2022-06-26 21:39:34 Coral Temp: 39.80C 2022-06-26 21:39:49 Coral Temp: 40.05C 2022-06-26 21:40:04 Coral Temp: 40.05C Mostly around 40*C Even when detection is active. I thought that maybe it was trying to read a file and couldn't access it correctly due to my wrong mounting of the unassigned drive and this crashed the process?