megalodon

BradJ did you ever get this working? Im on the latest version of Unraid with the APC SMC1000i-2UC and I can't get any load readings.

No but I appreciate you trying to help.

Im using a Brontastor Server which has an LCD display and buttons which was originally designed for use with open-e (The display and buttons). Can we add support to use this with regards to temperatures, drive status, capacity used/free etc. www.armari.co.uk Thanks Guys The display is a Crystalfontz 631 LCD, so Unraid would have to provide support for it. https://www.crystalfontz.com/product/usblcddriver https://www.crystalfontz.com/product/linuxexamplecode There is a free linux based monitoring tool available here - http://lcdproc.org/ https://sourceforge.net/projects/lcdproc/files/lcdproc/0.5.6/lcdproc-0.5.6.tar.gz/download in unraid allows you to add stuff to it, you could try to install lcdproc

Thanks Leifgg, thats a great help.

I wondered if anyone had the system temp settings for the AsRock E3C226D2I Mini ITX Motherboard. Thanks

This is interesting RobJ as I can recall once when cache_dirs was running after a reboot I watched as chat_dirs read all my disks from 1 to 8 but missed disk7. After reading the disks and them all spinning down I browsed my openelec box and disk7 spun up but not the others. This could be in relation to the problem you have identified.

I don't care how I install cache dirs, either standalone or from Dynamix. But I need to know the correct go file command so it scans all drives and folders 4 deep. Thanks

Okay so I removed cache_dirs and the go file and then installed it from the Dynamix plugins page. I have some errors coming up. All I have done is set the depth to 4 folders deep in the settings. Bonienl sent this message so I really need joeL to look at it. I was quite happy running cache Dirs and the go file but was having problems so my thought was to remove it and run it from Dynamix control panel but Im still having errors. It looks like my original errors were to copying the go file command another user posted as I only wanted to scan 4 folders deep. This is the message Bonienl sent me on the Dynamix forum page and the image of my errors is posted as well: The latest version of "Dynamix Cache Dirs" downloads the cache_dirs script made available here on the forum. The file is unzipped and placed in the /usr/local/sbin folder. This approach ensures that always the latest available version of cache_dirs is used. Dynamix builds a GUI wrapper around it, which allows the user to enter parameters using the browser. Upon execution these are given as the actual CLI options for cache_dirs. Looking at the source code of cache_dirs I see it does a hard coded search in /mnt/disk* and /mnt/cache, which explains the warning messages you get. These are harmless, but you may want to ask Joe to make a correction (e.g. test if Cache drive exists).

No its not. Im going to remove cache dirs and the line from the go file and install it from dynamix, maybe that will work better. Thanks

I found this post to joeL a while ago: --- End quote --- The cache_dirs program will re-schedule itself when it finds no mounted disks. (Or thinks there are no mounted disks) Why would I have or it think there are no mounted disks?

The only thing relating to cache dirs is my go file which is: /boot/cache_dirs -w -d 4

I have attached a log that shows that my cache dirs scheduled a read after a spin down of the disks for no apparent reason. Can anyone explain what is happening please. log.txt

Thanks trurl

Thanks trurl I did read that and could see the -e to exclude but its written like this -e "*Junk*" so I didn't know if you need the Asterisk and or the speech marks. I mean should I just add -e .TemporaryItems to my go file.

JoeL because Im using a Mac to access my unRAID server I always end up with a load of .TemporaryItems folders over my disks and cache dirs always scans them. I don't know if it makes any difference but is there a way to exclude these folders from being scanned or will it make no difference at all.

I have selected the Best bang for buck. I ran the script in safe mode on V5.5 and have 16GB of ram. I would have liked to have selected a higher MB/s but Im worried about lower memory as I run Dynamix, Dynamix Health, Dynamix System Temp, APC UPS and Cache Dirs. I have 5 x 3TB WD Reds, 1 x 4TB WD Red and a 4TB WD Red Parity. I would have expected to be able to run a much higher MB/s with 16GB Ram but it doesn't seem like I can if I want to avoid running out of what I presume is lower Memory? TunablesReport.txt

It was Dynamix Email Notify, I will notify the developer. Thanks Joe.

Thats great thanks Joe, Sorry for the blame. I only have APC UPS, Dynamix and Dynamix system temp installed so I will try and find out which one is causing the problem. With regards to the memory issues on cache_dirs 32bit I presume Im unlikely to have any worries of running out of memory with my four plugins including cache_dirs and 16GB of Ram?

So I have placed cache_dirs in the root of my flash and added /boot/cache_dirs -w to my go script. Now for some reason Im getting error 404 and I can only think it is related to cache_dirs as I have not seen it before. Can anyone tell me if it is and what I can do about it. Thanks

As its always hard to find information about unRAID plugins etc without sometimes reading through loads of forums posts, it maybe a good idea to have a list of motherboards that forum users have already setup with the system temp plugin, sensors.confg information, with a link from each motherboard to the sensors.conf information and the go information. Just a thought but it would make it so much easier to just click a link and have the information to hand.

I didn't get the X9SCM-F working under ESXi, but I did get it working on bare metal using the following steps: My go file addition: modprobe w83627ehf cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf My /boot/custom/sensors.d/sensors.conf file: chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*" label in0 "Vcore" label in2 "AVCC" label in3 "+3.3V" label in7 "3VSB" label in8 "Vbat" label temp2 "CPU Temp" label temp1 "MB Temp" set in2_min 3.3 * 0.90 set in2_max 3.3 * 1.10 set in3_min 3.3 * 0.90 set in3_max 3.3 * 1.10 set in7_min 3.3 * 0.90 set in7_max 3.3 * 1.10 set in8_min 3.0 * 0.90 set in8_max 3.3 * 1.10 Thanks for this Ogi it was a great help to me. As Im using a later version of Dynamix WebGui all I had to do was make a sensors.conf file using a text editor and place your settings in it and just add "mod probe w83627ehf" to my go file using my text editor. The sensors.conf file is in a different place from where it used to be when using the Dynamix system temp plugin from the webGui. For a new user to unRAID like me it helps so much when users post helpful things like you did, so thanks. Im using a Supermicro X9SCM-iF Motherboard but a the temp sensors are very confusing on this board. It says Im getting 29.5 on the motherboard and 35 degree's C on the CPU using your settings in the dynamix webGui with the system temp plugin. But the IPMI says 29c system temp, 35c peripheral temp and CPU temp low. When I spoke to Supermicro Tech support last year they told me the system temp is for the motherboard sensor as correctly shown in the Dynamix WebGui but the 35c is for the peripherals like the HBA cards etc and not the CPU as the CPU just has low, med or high so Im wondering if the CPU temp of 35c showing in the Dynamix webGui is actually for the CPU or not.