This is an automated archive made by the Lemmit Bot.
The original was posted on /r/unraid by /u/ishbuggy on 2023-09-15 12:45:22.
I am running Unraid 6.12.3, and I’m having an issue where file access on an SMB share is causing the disks to spin-up in the array when they shouldn’t. It is happening with multiple shares, but I included an example in the screenshots. The share is set to use the cache first, then move to array. But when I access it via SMB on another windows computer, it will work, but it spins up the disks when filed in the share are edited.
I cannot figure out why the disks are being spun up here. When I check the files on the disk itself, they are not modified. It still contains the old version, as mover has not yet been run. The modification is present in the cache drive as expected.
File activity plugin output, where a test file was edited (moved directory within the share)
Syslog output, showing that immediately the disks were spun up, and SMART read initiated
Configuration of the array, with disk2 and parity drive spun up after the file edit for
Does anyone have any thoughts as to why the disk are being spun up? So far this is negating a lot of power reduction I am trying to accomplish by spinning down disks. This happens for other shares as well, including, very annoyingly, my backup share where I have windows file history backups. This means that almost when I do anything on my desktop, it will inevitably spin up the relevant disk and parity disk.
You must log in or register to comment.