1 hour ago, alturismo said:

before you go this way deeper

 

- when you manually stop the docker before you "sleep"

- when you manually start the docker after "sleep"

 

and then it works, then a script could resolve your issue

I have actually tried it buy putting docker stop name of container in dynamix s3 plugin before sleep command box and docker start name of container in after wake up command box but this is hit or miss , sometimes the server sleeps without even stopping the docker container than upon wake up the docker container fails to see the gpu , is there any way to introduce a time delay like example the server sleeps at 12am so just 30seconds before the docker container should automatically stop and and 30 secs after the server wakes up the docker container should automatically start , is there a way to introduce time delay

53 minutes ago, drmetro said:

I have actually tried it buy putting docker stop name of container in dynamix s3 plugin before sleep command box and docker start name of container in after wake up command box but this is hit or miss

so does it actually work if you stop the docker before sleep and wake after sleep ?

 

or may, even when you just restart the docker after wake ...

2 hours ago, alturismo said:

so does it actually work if you stop the docker before sleep and wake after sleep ?

 

or may, even when you just restart the docker after wake ...

It only works if that particular docker container is stopped before the served sleeps and starting it again after server wakeup , this way the docker container doesn’t know that server actually slept

Edited November 20, 20241 yr by drmetro

I just wanted to say thanks for the sleep plugin, we are having sever blackouts in my country, I have a power station, but not big enough to sustain my server, so I wanted some way to shut it down gracefully.

 

With this plugin I can monitor my smart lights to check if they are up, if they are not I can initiate a shutdown.

Thanks a lot!.

 

I'm using actual shutdown instead of S3 because it boots fast enough for it not to be an issue.

Now I have to figure a way to turn it back on when power is back. Time to get one of those RPIs working I guess.

On 11/8/2024 at 5:24 PM, spl147 said:

CPU Fan should ONLY be controlled by the BIOS! controlling your cpu fan from a plugin is insane!

 

CPU Fan = Bios

Array Fan = Plugin

 

The plugin should display a warning and/or allow to use the CPU temp for fan control (I did not expect that it only uses the disk temps). For me it absolutely does not make sense to control the array fan only as it covers the incoming and outgoing air. If the BIOS sets the CPU fan to maximum, it does not make any difference if the hot air is not leaving the case.

 

In addition:

- the obtained speeds are false

- the auto detection does not work correctly (to obtain the minimum pwm value, for me it was a way to low = fan stopped)

- a comment field is missing to name the pwm controller / fan

- it seems not to monitor the parity temp:

 

 

Hello!

I am new to Unraid and am trying to get some way to have more control over cooling. I have installed Autofan but it does not seem to be running anywhere?? I see a new item in the settings for it and have tried enabling it but nothing anywhere else seems to exist. What am I missing? I may also be in the club of my MB does not have any controllable fan controllers (MINISFORUM BD790i MB) could that be why?

1 hour ago, ETHREAL1 said:

Hello!

I am new to Unraid and am trying to get some way to have more control over cooling. I have installed Autofan but it does not seem to be running anywhere?? I see a new item in the settings for it and have tried enabling it but nothing anywhere else seems to exist. What am I missing? I may also be in the club of my MB does not have any controllable fan controllers (MINISFORUM BD790i MB) could that be why?

from terminal run sensors-detect and post output

 

9 minutes ago, spl147 said:

from terminal run sensors-detect and post output

 

I'm guessing by all the "No" that's its not finding anything...

Sensor-Detect Output.txt

Edited December 7, 20241 yr by ETHREAL1

3 minutes ago, ETHREAL1 said:

I'm guessing by all the "No" that's its not finding anything...

Sensor-Detect Output.txt 8.37 kB · 0 downloads

Driver `to-be-written':
  * ISA bus, address 0xa30
    Chip `ITE IT8613E Super IO Sensors' (confidence: 9)

 

Note: there is no driver for ITE IT8613E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Edited December 7, 20241 yr by spl147

Hi, I also have a NAS with ITE IT8613E Super IO Sensors, but this seems to be used only for fans - when installing the ITE drivers plugin and restarting, Dynamix Temp now sees fans from IT8613E.

 

But on my Drivers list, k10temp is shown as the temperature sensor, as my NAS uses a Ryzen 7 5825U CPU.

How can I show this CPU temperature?

 

I don't understand why it's so complicated to UnRAID have this by default, other NAS solutions with Linux in the background (like Ubuntu) can show this CPU temp by default.

Edited December 10, 20241 yr by ffleps

Well, found a solution:

 

- manually created /boot/config/plugins/dynamix.system.temp/drivers.conf with

it87
k10temp

 

- edited /boot/config/plugins/dynamix.system.temp/sensors.conf

chip "k10temp-pci-00c3"
label "temp1" "CPU Temp"
chip "it8613-isa-0a30"
label "temp1" "MB Temp"

 

Saved, went to the sensors, it87 k10temp were already on the field, clicked SAVE, then loaded the 2 labeled ones on the "sensors" section for CPU/MB temps. Didn't even needed to restart.

 

Thanks for the plugin, it is TRULLY BIZARRE that in 2024 unRAID doesn't have CPU temp natively like any free HomeNAS/Server tool does and we need to install plugins, runs commands, edit files and all this manually.

15 hours ago, ffleps said:

other NAS solutions with Linux in the background (like Ubuntu) can show this CPU temp by default.

 

Have you checked the installation size of Ubuntu compared to Unraid lately?

4 hours ago, Espressomatic said:

 

Have you checked the installation size of Ubuntu compared to Unraid lately?

 

Somehow fixing sensors implementation OOTB would make Unraid to be as large as Ubuntu?

15 hours ago, ffleps said:

Somehow fixing sensors implementation OOTB would make Unraid to be as large as Ubuntu?

 

I didn't say that, nor imply it. What I'm saying is that it's not a valid comparison, as Ubuntu is a general-purpose desktop distribution (not a NAS) packed with a lot of drivers and other components ready to go, whereas Unraid is a minimal distribution deployed on a small USB key using Plugins to support very specific use cases.

 

 

Edited December 11, 20241 yr by Espressomatic

22 hours ago, ffleps said:

Thanks for the plugin, it is TRULLY BIZARRE that in 2024 unRAID doesn't have CPU temp natively like any free HomeNAS/Server tool does and we need to install plugins, runs commands, edit files and all this manually.

Whats Bizarre is the fact that everyone just expects every board with any config to work. if any/all did any homework on the Fan Speed plugin you would have seen that it is BETA for 1 and for 2 it relies on HWMON support and HWMON is not all encompassing nor is it complete! hense why people have written plugins to add support for chips not yet supported by HWMON.

 

no one bothers to check that the board they build with has the proper driver support for their intended purpose.

1 hour ago, spl147 said:

Whats Bizarre is the fact that everyone just expects every board with any config to work. if any/all did any homework on the Fan Speed plugin you would have seen that it is BETA for 1 and for 2 it relies on HWMON support and HWMON is not all encompassing nor is it complete! hense why people have written plugins to add support for chips not yet supported by HWMON.

 

no one bothers to check that the board they build with has the proper driver support for their intended purpose.

 

My comment was not towards the plugin creators, I think you missed that.

They do an amazing job fixing things the "OS" should have by default.

 

It was towards Unraid team.

 

We shouldn't need a plugin to simple read system sensors in 2024, specially for a Ryzen 5000 series CPU.

And I would argue that be able to read CPU temps on a NAS device is pretty important.

 

This is not a free tool made by some small indie dev that was launched 2 months ago.

It's a paid system with almost 20 years.

 

(the irony: I tested a bunch of these homelab / server systems like CasaOS, ZimaOS, Umbrel, they all read my CPU temp out of the box)

 

Edited December 11, 20241 yr by ffleps

1 hour ago, ffleps said:

We shouldn't need a plugin to simple read system sensors in 2024,

 

I understand your comments weren't targeted at plugin developers. But your opinions about Unraid in this regard are misplaced and simply incorrect. You don't need a plugin to read sensors. lmsensors is built in. Sensor-detect is built-in. Drivers for ALL sensors are not built in.

 

So here's an idea. How about posting a suggestion to have the Fan Control and Sensors plugin(s) installed and available by default in Unraid? Plenty of other built-in functionality originally required manually installing a plugin.

 

Some similar suggestions already exist, I've ever posted a few myself, asking for very specific plugins to be standard/default. It seems like most people prefer an a-la-cart solution like we have now.

 

  

1 hour ago, ffleps said:

(the irony: I tested a bunch of these homelab / server systems like CasaOS, ZimaOS, Umbrel, they all read my CPU temp out of the box)

Now it sounds like you're taking the piss. If those solutions offered what Unraid does, then I argue that you wouldn't be here. Now, maybe they include some additional drivers and defaults, but what they lack compared to Unraid can fill a canyon.

 

Unraid is getting more turn-key, but until it's "all the way there" it takes very little effort to install the necessary plugin.

Edited December 11, 20241 yr by Espressomatic

I am currently running a trial for a 3rd backup option for my data. An important part of this setup is that it is able to sleep between backups (power is very expensive at the location), so I use the s3sleep.

 

When using the plugin, the machine will go to s3 sleep, even when parity calculations are under way. Is this intended behaviour?

 

Unraid: 6.12.14 2024-11-26

S3sleep: 2023.03.23

 

3 hours ago, ph0ton said:

I am currently running a trial for a 3rd backup option for my data. An important part of this setup is that it is able to sleep between backups (power is very expensive at the location), so I use the s3sleep.

 

When using the plugin, the machine will go to s3 sleep, even when parity calculations are under way. Is this intended behaviour?

 

Unraid: 6.12.14 2024-11-26

S3sleep: 2023.03.23

 

 

There's a bug in the current detection mechanism. You need to put your disks in the "Monitor disks outside array" tab. 

4 hours ago, foo_fighter said:

When using the plugin, the machine will go to s3 sleep, even when parity calculations are under way. Is this intended behaviour?

The activity checker is broken and the dev is MIA.  I don't think the "monitor disks outside array" setting fixes it.  But try and see. 

 

If it doesn't, someone has created a fork of the sleep add on that should work.  I haven't tested it.

 

https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/159/#findComment-1364337

 

 

Edited December 13, 20241 yr by Marc_G2

When running "fix common problems" it mentioned I should switch to a fork of the Cache directories plugin due compatibility issues with current unRAID.  Is it in the store?  I didn't see it.

On 12/10/2024 at 8:40 PM, Espressomatic said:

 

Have you checked the installation size of Ubuntu compared to Unraid lately?

It's not 2005 anymore, it doesn't matter the slightest if an OS takes 1GB or 20, it's becoming difficult to even find drives <64GB. 

Even "Unraid runs entirely from RAM" has sailed away a while ago already. 

 

19 hours ago, Kilrah said:

it doesn't matter the slightest if an OS takes

 

It's obviously that you've never written, let alone (and more importantly) tested, a single line of code.

 

If the requirement to perform a 60 second installation of a plugin and/or fan control driver is the biggest complaint against a project/product, I'd say it's a certified winner.

 

What I find truly amazing, and staggering, is that I haven't noticed requests for the inclusion of thee drivers mentioned in the future features thread(s).

 

Edited December 14, 20241 yr by Espressomatic

21 hours ago, Marc_G2 said:

Is it in the store?  I didn't see it.

Ok so it was that plugin.  I thought the one there was literally the one I just removed since the name didn't change