Hey good afternoon everyone, I have a quest(ion) about HDD spindowns and spinups.
What I want to achieve: spin-down specific Hard Disk Drives (preferbly with mounted filesystems), which are only woken up when there is read/write activity to them (this is how it works on regular Linux servers).
So I've configured a Debian system with Proxmox to spin down specific HDD's (easily done via hdparm). While monitoring the situation, I noticed a spin-up occurred for no visible reason, so I went to investigate. And yes, forcing a drive to spindown with "hdparm -Y /dev/sdX" sped up the discovery process of this challenge. No VM's were active on this hypervisor yet. Actions I took:
- unmounted the directory which was mounted from the spun down HDD, but still spin-ups occurred
- had a look if SMART checks were requested perhaps, they did not seem to be.
- pvestatd is running, but didn't seem to have anything about this in its logfile. Still haven't completely dismissed this daemon, but stopped looking into it, for now.
- sifted through other logfiles, but didn't find anything useful.
- then I went around and clicked through the GUI and the HDD spin up occurred when I accessed the tab "Datacenter -> Host -> Disks".
Is this normal behaviour? Is there a way to achieve my goal? Any advice is welcome, even if we're just throwing around ideas.
P.S. yes I have read other topics about HDD spindowns etc.
P.S. 2: please let's not deviate into a discussion into why someone would or wouldn't want to do this (wear & tear etc.)
What I want to achieve: spin-down specific Hard Disk Drives (preferbly with mounted filesystems), which are only woken up when there is read/write activity to them (this is how it works on regular Linux servers).
So I've configured a Debian system with Proxmox to spin down specific HDD's (easily done via hdparm). While monitoring the situation, I noticed a spin-up occurred for no visible reason, so I went to investigate. And yes, forcing a drive to spindown with "hdparm -Y /dev/sdX" sped up the discovery process of this challenge. No VM's were active on this hypervisor yet. Actions I took:
- unmounted the directory which was mounted from the spun down HDD, but still spin-ups occurred
- had a look if SMART checks were requested perhaps, they did not seem to be.
- pvestatd is running, but didn't seem to have anything about this in its logfile. Still haven't completely dismissed this daemon, but stopped looking into it, for now.
- sifted through other logfiles, but didn't find anything useful.
- then I went around and clicked through the GUI and the HDD spin up occurred when I accessed the tab "Datacenter -> Host -> Disks".
Is this normal behaviour? Is there a way to achieve my goal? Any advice is welcome, even if we're just throwing around ideas.
P.S. yes I have read other topics about HDD spindowns etc.
P.S. 2: please let's not deviate into a discussion into why someone would or wouldn't want to do this (wear & tear etc.)