Ok, then why does TrueNAS support apps (namely the “community apps”)? Enterprise users aren’t using that stuff, and that stuff is taking FAR more development resources than making spin-down work correctly would.
5 Likes
Got me there - I could kinda somewhat argue if it was still kubes, but uhh…
2 Likes
I agree that iX is not really consistent when it comes to arguing why certain features are enterprise only, added, not added, or whatever.
With this particular request, I guess it has to do with not wanting to enable an easy way for people to lower the lifespan of their drives. They seem to be very concerned about the image they have when it comes to reliability, understandably so. And from my experience it’s the spin ups/downs that kill drives, not the running of them. But I am just guessing here.
The irony here is that we aren’t even arguing for a complete disable or enable of the feature. We’re arguing about a toggle that the user or admin can decide to use or not.
Even in enterprise environments, there are use cases for drive spindown, such as large cold storage backups that spin up once a week or month.
2 Likes
Actually, we are arguing for merely retaining what was possible with previous versions. No extra engineering work required.
5 Likes
From my experience this is still done on tapes which are rotated. Or the cold storage on spinning rust is warm in the sense of detached but spinning. But yours might be different. Would be interesting to hear from iX if there are business use cases from their customers.
Yes, it is quite curious that this was removed. Again, I can only guess that this was for the lifespan reason I mentioned before. Or maybe there are drives that don’t behave correctly. Or maybe it is because spin down can be prevented by a lot of reasons on a TrueNAS system and they had too many complaints about that? Not defending anything, only guessing.
It was not removed.
There was some changes done in the code about smart tests (probably at the same time as when they removed the GUI), which checks for the state of the disks. However, they used a specific argument and forgot to add an additional one for disks in spin down state. A very simple fix, which is already given a few posts above, which I compiled by the way 
3 Likes
This post
2 Likes
It was effectively removed and stated in two podcast episodes that it will most likely stay that way. That was what I was referring to. But you are right, technically the option still exists in the GUI.
And in the documentation.
I followed the podcast, and I don’t remember mention them about this topic. Only Smart UI removal (which is coming back) and disk health management. I don’t even remember them mentioning that they removed the argument necessary for a good functioning spin down. Just, spin down is not the best with ZFS drives.
I don’t deny that or argue against it.
The latest I could find in this thread is here:
It was about a basic question, not this bug. So not very explicit either here.
Feature request is here: Support HDD standby
Please vote
3 Likes
A voté as we say in French
1 Like
Has anyone tried this under 25.10.2.1? Still working?
Yes.
2 Likes
@ark, thank you for posting the patch.
Ah, so this is why my drives kept waking up. So ix has intentionally added a new feature designed to waste power, increase cost and destroy the drives as early as possible. Great.
Will this be fixed or do users just have to revert back to an older version and use that forever. Cause I’m not leaving my drives spun-up 24/7 since they only have to be active at a fraction of that time.
2 Likes
That’s the issue. It seems to be not Intentional.
By the way, spinning up drives very often is actually what damages them more (what the legend says).