- Closed
Issue Description
As I understand it, a ZFS pool must have all its disks spun up when in use. Likewise, when not in use, all disks can be spun down.
While using Unbalanced to move data to a ZRAID2 6-drive pool (single VDEV), while doing its discovery/check process, I noticed 3 disks in the UI marked as spun down. They sat like this for a couple of minutes as I waited to see if the other 3 would spin down. I spun them back up manually using the dot/circle next to the drive labels in the Main tab.
As I'm writing this post, I notice those 3 disks are still spun up, but the other three disks are now spun down.
Expectation
Spinning up and down of the pool looks like it allows the disks to get out of sync. I understand the need/desire for staggered spin-up, but I expected the sequence within a pool to be managed tightly - and for spin-down no staggering.
The WebUI allows disks within a single VDEV RaidZ2 to be spun up/down individually as mentioned, and this seems counter intuitive and that it might possibly lead to issues. I'd expect the entire pool to have a single spin up/down control and Unraid to take care of the staggering sequence automatically.
Testing
This has been more observation than testing, as described above.
I have a general 30 minute spin-down delay in the Unraid settings as I have had for years.