Is it just me or is everyone unable to vote / comment on that issue? I can hit the button but then get a network error. Do you have to promote your account in some way to be able to vote?
Can you link to the Feature Request? Searching ‘spindown’ in that category only brought up a Closed request
It is the issue discussed in this thread. I’m sadly unable to post links in this forum, but it is this one: NAS-137887
That’s a Jira trouble ticket. You can only vote on open items in the Feature Request category.
Link for the Jira https://ixsystems.atlassian.net/browse/NAS-137887
Patch still applies clean to 25.10.2, without it my spare hdd stays spun up
any additional config needed on truenas ui after applying this patch?
Not really, I have the spinning disks set to ‘1’ power setting for standby and standby time set to 5m
Which patch, or patch which post #? Link?
Thanks!
I replied to it, just click the name/arrow and it should scroll up to the post
Should be this:
It should be noted this issue is affecting 25.10.x series, not 25.04. My main box is still on 25.04.x and will remain there for the foreseeable future. Good to know there’s an option for bringing back this functionality to 25.10.x.
For info, I posted a message in the bug report. But I think it is still not followed.
To create an account for Jira, you have to create a bug report from Truenas itself, there you will find the way to create it.
Since noone seems to be working on the jira issue, shall we add a feature request such that people could vote on it?
I think this will be necessary.
So, problem solving, and suggestion a spin down mode as well.
For info, I found my server with discs not spinning. I have not seen since when, but my settings is to spin them down by default after 60min.
And I am on the last stable Truenas version 25.10.1 or something.
One closed
One still open
They are a bit to specific aren’t they ?
shouldn’t we do one more generic instead ? There is a basic bug, and only this one needs to be fixed.
I think it is beneficial that my feature request is fairly specific because it outlines a specific, clear problem and provides an easy solution that would be easy to implement OOTB.
Yes, but it describes a different problem: your report focusses on controlled unload when shutting down the system, specifically on LSI controllers.
This thread is looking for a generic possibility to spin down disks on idle conditions, and keep them spun down until the next access to the regarding disk/pool happens. I think that should go into a separate feature request to keep things clear and specific.
Im sorry but i do not understand why this is such an issue. Let us spin down our disk for the love of God.
I also cannot accept the “enterprise users don’t need this feature” argument.
This is like saying “Sorry, you cannot turn off your TV, since commercial users need their TVs on all the time for signage.” What is even this argument?
While I agree that disk spin down should be allowed, I disagree with your reasoning. Enterprise is where the money comes in & spending money for a feature that us in the community want for free is development hours on good will at best - time wasted because it doesn’t work with “random drive model” at worst & is now a new point of friction.
Difference in product segmentation - you still pay $x for consumer grade TV with y features. I’ve had to source commercial grade tvs with z features for broadcast testing in 24/7 environment & it is $20x. We get TrueNAS for free, but it comes with (most) features & (all) limitations of enterprise flavour. ![]()
Not saying it is right/wrong, but I get the accounting for why it is an ignored request. A few things in the thread a spindown script has been mentioned which imo fits with the theme of working around built-in limitations & getting what you want.