pappaq Posted February 14, 2021 Share Posted February 14, 2021 Hey there, by investigating the high powerdraw of my system I stumbled upon a very bad quirk in my system. The system shows all disks as spun down but they are actually spun up! I can feel them vibrating or spinning back up, after I forced them to spin down. That is a HUGE difference of nearly 40W!!! Not to talk about the always running disks that should be spun down to enhance their lifespan. Here my diagnostics. dringenet-ms-diagnostics-20210214-1144.zip Quote Link to comment
pappaq Posted February 14, 2021 Author Share Posted February 14, 2021 Updated to RC2 and the behavior is gone. Going to test some more. Quote Link to comment
pappaq Posted February 14, 2021 Author Share Posted February 14, 2021 I'm settling with RC2 right now. I hope it runs relatively smooth. I've got the next problem though. My HDDs are held spun up by somthing, I can't tell what. Does anyone can take a look at the diagnosis? Thanks. dringenet-ms-diagnostics-20210214-1551.zip Quote Link to comment
ChatNoir Posted February 14, 2021 Share Posted February 14, 2021 It is a known bug of 6.9RC2, should be fixed for RC3. Quote Link to comment
pappaq Posted February 16, 2021 Author Share Posted February 16, 2021 On 2/14/2021 at 7:13 PM, ChatNoir said: It is a known bug of 6.9RC2, should be fixed for RC3. This was not the case for me. I've restarted my dockers one by one and it looks like that "telegraf" is keeping the disks spun up. Trying to figure out now why though. Quote Link to comment
ChatNoir Posted February 16, 2021 Share Posted February 16, 2021 Whoops, my bad you are right, I got confused with the startup temp issue. If memory serve*, the issue with telegraph is that some components are either not up-to-date or missing. I think It can be fixed with post arguments in the docker template. * recent experience show that my memory is not always to be trusted. Quote Link to comment
pappaq Posted February 16, 2021 Author Share Posted February 16, 2021 5 hours ago, ChatNoir said: Whoops, my bad you are right, I got confused with the startup temp issue. If memory serve*, the issue with telegraph is that some components are either not up-to-date or missing. I think It can be fixed with post arguments in the docker template. * recent experience show that my memory is not always to be trusted. I've disabled the plugin "HDDTemps" in the telegraf config. It would be awesome to get the functionality back up to monitor the HDD temps via grafana. But unti that I am happy that the HDDs stay spun down. I am tackling the issue in the next few days, if I find the time for it. Maybe you could explain the "post agrument" idea a little further? Thanks! Quote Link to comment
ChatNoir Posted February 16, 2021 Share Posted February 16, 2021 I am certainly not an expert here, but I think I read about it on one of the numerous topics about the spin issue on RCs (in Bug reports / Prerelease). From what I get, you can have any docker container run a set of command at startup with the post arguments (available in Advanced View). I am certainly not a Linux guy so I just run the recommended commands from UUD, I did not dig too much on what specific command can help for spin down. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.