SSD TRIM

 

I'm wondering if it's necessary/desirable/unrecommended to install the SSD TRIM plugin with an SSD that uses RAISE.

 

-- 

Chris

Edited January 1, 20215 yr by bidmead
syntax adjustment

I would always install trim on all SSD's.  I think it's highly worth and and have never had an issue.  I followed your link but it didn't make immediate sense to me what you mean.  Just install trim I reckon.

On 12/31/2020 at 6:39 AM, Pixel5 said:

is there anything i can do on my side when the auto fan plugin doesnt detect any PWM controllers?

 

I know the system has one as every fan header supports PWM and each header can be controlled individually in the BIOS but this plugin doesnt see any sadly.

run sensors-detect from command line, the run modprobe to add the sensors that are detected, then the fan speed plugin will see the headers

2 hours ago, spl147 said:

run sensors-detect from command line, the run modprobe to add the sensors that are detected, then the fan speed plugin will see the headers

its only detecting a sensor shown as unknown device and core temp both of which dont really help me here.

Ive seen many others have the same issue with a driver that is missing for this it8686 chip but so far i didnt find any functional solution yet.

4 minutes ago, Pixel5 said:

it8686

Try this

 

https://forums.unraid.net/topic/100483-z490-vision-g-fan-sensors/

 

Does Dynamix System Temperature break the temp reporting of SSD's? After I installed it, my ssd's no longer report a temperature (understand that it's expected for ssd's to not necessarily report temp, but they were prior to installing System Temp). 

 

Also - I tried uninstalling System Temp, and now I don't see the native temp reporting in the dashboard. Is that expected?  I'm running 6.9.0-rc2.

 

 

6.9 has an issue where no temps are reported until the drives actually get spun up.  Being fixed next rev

18 hours ago, Squid said:

Try this

 

https://forums.unraid.net/topic/100483-z490-vision-g-fan-sensors/

 

sadly this didnt help and im getting 

modprobe: ERROR : could not insert "it87" device or ressource busy

23 hours ago, spl147 said:

run sensors-detect from command line, the run modprobe to add the sensors that are detected, then the fan speed plugin will see the headers

I can't run sensors-detect on this 6.9.0 rc 2 UnRAID as there seems to be no perl available. Any suggestions?

 

-- 

Chris

2 hours ago, bidmead said:

I can't run sensors-detect on this 6.9.0 rc 2 UnRAID as there seems to be no perl available. Any suggestions?

 

-- 

Chris

Install NerdPack and via it install Perl

I've just this minute got that exact tip from @SpaceInvaderOne, logged in here to report it and saw your message. Many thanks. This really should be mentioned in the System Autofan plugin, shouldn't it?

 

-- 

Chris

Edited January 3, 20215 yr by bidmead

Ha! On the advice of @SpaceInvaderOne I've just installed the Dynamix Stats plugin, which has drawn my attention to an anomaly with my boot flash drive.

 

I hadn't noticed before that on the MAIN tab what is supposed to be a 16GB USB stick is reported as only having 2GB capacity. The Stats plugin seems to make this very clear.

 

Is this 16GB CruzerFit a fake? All suggestions welcome.

 

-- 

Chris

 

 

 

 

 

 

 

Edited January 3, 20215 yr by bidmead

2 hours ago, bidmead said:

Ha! On the advice of @SpaceInvaderOne I've just installed the Dynamix Stats plugin, which has drawn my attention to an anomaly with my boot flash drive.

 

I hadn't noticed before that on the MAIN tab what is supposed to be a 16GB USB stick is reported as only having 2GB capacity. The Stats plugin seems to make this very clear.

 

Is this 16GB CruzerFit a fake? All suggestions welcome.

 

-- 

Chris

 

 

 

 

 

 

 

If you back it up first, it should be easy enough to test by seeing if you can successfully write the expected amount of data to the drive and then also read it back intact.   If it IS a fake one of those steps will fail.

Rebooting with Dynamix System Buttons starts a parity check for me in 6.9 RC1. Is this normal/known?

2 hours ago, Glasti said:

Rebooting with Dynamix System Buttons starts a parity check for me in 6.9 RC1. Is this normal/known?

I don't use that plugin since many of these buttons are already on the Dashboard page. Are you sure you don't have a problem with flash being read-only or disconnected? You get unclean shutdown if flash can't be written to update the started/stopped status of the array before shutting down.

2 hours ago, Glasti said:

Rebooting with Dynamix System Buttons starts a parity check for me in 6.9 RC1. Is this normal/known?

I have not had the same problem with the System Buttons as you BUT I have observed that the Folding@Home docker does not shutdown (within the period of time that I waited).  In the case of this Docker (since it does not write to the array), there was a clean shutdown of the array (hence no parity check on restart) but it did require that I reboot the server manually to complete the reboot.  You might try stopping any Dockers before trying the button and see if that 'fixes' the problem.  (Of course, that would still leave a 'bug' to be resolved but the cause is now more isolated...)

23 hours ago, trurl said:

I don't use that plugin since many of these buttons are already on the Dashboard page. Are you sure you don't have a problem with flash being read-only or disconnected? You get unclean shutdown if flash can't be written to update the started/stopped status of the array before shutting down.

Shutting down or restarting from the dashboard works fine. Permissions is something I checked and confirmed after posting here.

I changed my usb to a Cruzer recently so I can not disconnect it as easily, by bumping against it when like moving my case a little. Something I have done in the passed accidentally with other usb sticks. 

 

23 hours ago, Frank1940 said:

I have not had the same problem with the System Buttons as you BUT I have observed that the Folding@Home docker does not shutdown (within the period of time that I waited).  In the case of this Docker (since it does not write to the array), there was a clean shutdown of the array (hence no parity check on restart) but it did require that I reboot the server manually to complete the reboot.  You might try stopping any Dockers before trying the button and see if that 'fixes' the problem.  (Of course, that would still leave a 'bug' to be resolved but the cause is now more isolated...)

I deleted the plugin for now. Don't have the time/feel like troubleshooting right now. When I have time it will be a fun little project to see if it's a docker issue. It's a good point, could very well be. 

Edited January 5, 20215 yr by Glasti

30 minutes ago, Glasti said:

Permissions is something I checked

I didn't really say anything about permissions. If flash has corruption Unraid will mount it read-only so no further damage is done. And that would prevent clean shutdown since the status couldn't be written.

I need some help where I should add the following for sensors.conf so I can detect more sensors from the NCT6683D chip.

options nct6683 force=1

 

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

 

The above line is for Linux but I need to add it systemp plugin or UNRAID somwhere

 

I added it to /etc/sensors.d/sensors.conf but it is not persistent after reboot.

Add the command to the "go" file (/config/go on the flash drive)

1 hour ago, Squid said:

Add the command to the "go" file (/config/go on the flash drive)

do I add

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

 

or

 

options nct6683 force=1

 

??

18 minutes ago, mikeyosm said:

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

 

There is a word on the forum that if your running Dynamic Fan Control, which I do fans will not shut down using 6.9-RC2. My Drives do not shutdown on their own. I reverted back to 6.9-Beta35 and they do. Is there a Plugin Mod we can do or is it a sensor issue that trips it up?

is there any way to configure the fan speed plugin to only control my case fans but completely ignore my CPU fan?

 

right now my case fans are correctly controlled base don HDD temp but the CPU fan is at 100% constantly even when i disabled auto fan for it.

I apologize if this is in the wrong thread, just let me know and I'll move it to general support or somewhere, but I am following the official wiki for setting up CPU temperature monitoring with the Dynamix System Temp plugin. I've installed NerdPack GUI, installed PERL, then installed and hit "DETECT" in Dynamix System Temp. It finds my driver as "k10temp nct6775", but the options for "Processor temperature" and "Motherboard temperature" are set to "not used" and do not show any other options. I've hit save, redetected, rescanned, and done all the research I could find. I even tried some alternatives to Dynamix, but I can't seem to get anything working. For more info, my motherboard is the MSI Meg X570 Unify and I have a Ryzen 3950X. Everything else is up and running, so far I'm loving Unraid and it's working great, I just can't get CPU temperature readings.

 

I'm very new to Unraid (on trial day 3 now), I like it a lot, but am still unexperienced in it. If someone could please help me with the next troubleshooting steps or if anyone knows a solution to this issue, please let me know.

 

Here is the link to the tutorial I am following:

https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing

 

Screenshot attached if it helps any.