gfjardim

This one? : Have I missed something here? What plug-in is that? I'm working on it, it's almost done.

Your drivers are k10temp and fam15h_power.

This one? :

unRAID has the following drivers available: asus_atk0110 coretemp f71805f f71882fg f75375s fam15h_power it87 k10temp k8temp nct6775 w83627ehf w83627hf w83781d w83791d w83792d w83793 w83795 w83l785ts w83l786ng You can try with each one of them, specially "f71805f f71882fg f75375s", that are Finteck's drivers.

Try this and post the output: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

That results in finding the 2 drivers, where one is yet to-be-written. ~# yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*" coretemp to-be-written Try again with the svn version: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*"

BRiT, please try this:

Try this and see if it helps: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}' Tried that and it seemed to be roughly the same time-hole which seems to be the following: Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) This bit should only be done once and only once with results cached until told to re-execute again. It should not be executed on each and every page load. I agree. Will make some mods for it. Please try this (install it with installpkg): https://dl.dropboxusercontent.com/u/18726846/dynamix.system.temp.txz

Try this and see if it helps: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}' Tried that and it seemed to be roughly the same time-hole which seems to be the following: Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) This bit should only be done once and only once with results cached until told to re-execute again. It should not be executed on each and every page load. I agree. Will make some mods for it.

Try this and see if it helps: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer. Also inactive/unused probes are removed from the dropdown menu, making the selection easier. Use the plugin manager to update to the new version. I updated to the latest version of Dynamix SystemTemp and now the Web UI went completely rogue and non-responsive for 10 minutes when I tried navigating to "System Temp" Settings via http://tower/Settings/TempSettings . Eventually it came up and allowed me to make selections. Now when I clicked on "Apply" its sitting non-responsive again for at least 5 minutes. The tailing of syslog only showed these relevant entries: Feb 2 21:05:18 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe Feb 2 21:07:19 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe Feb 2 21:09:21 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe I don'r see anything in the code that may trigger this behavior. This is the only command that can be potentially problematic: yes ''|/usr/sbin/sensors-detect 2>&1|awk '/^modprobe/{print $2}' If you can run it successfully, then I don't have any clue about where the bug is....

Some bug fixes, and a new MB icon. dynamix.system.temp.zip

I will search for one. Edit: try the one attached here. dynamix.system.temp.zip

bonienl, attached is some configuration options I made to "System Temp". Thanks for your hard working. dynamix.system.temp.zip

I will investigate this soon, ok?

It's not required. I just backup the flash drive of unRAID.

I don't see in your config a map to /data:

There's no client/server separation with CrashPlan. Every instance works as a possible source/destination to other instance. So if you want to backup your Windows machine to your unRAID, first you must open the "C:/Program Files/CrashPlan-Server/CrashPlanDesktop.exe" and change the "Default backup archive location" to where you wish to store your backups in unRAID: Then, open "C:/Program Files/CrashPlan/CrashPlanDesktop.exe" and select the unRAID server as the backup destination.

Did you set your user account and the inbound backup destination? Take a look: http://support.code42.com/CrashPlan/Latest/Getting_Started#More_Info

Did you configured your unRAID CrashPlan install first?

Ok, this is a hint. Remove Crashplan and reinstall it on your Windows machine. Then go to "c:/program files", and make a copy of the Crashplan folder to, e.g., CrashPlan-Server. In this newly created folder ("c:/program files/CrashPlan-Server"), change the conf/ui.properties following the instructions on the header of this topic. Then, you can create a shortcut to "c:/program files/CrashPlan-Server/CrashPlanDesktop.exe" on your desktop.

Please take a look at the file /path_of_config/conf/my.service.xml and search for these lines: <serviceHost>...</serviceHost> <servicePort>....</servicePort> Post the content here.

Yes, this is the right behavior. If you want to star clean, you should remove the directory you map as /config (usually, /mnt/user/appdata/crashplan)

One of these days I changed my server from one-80mm-fan-per-enclosure to four-120mm-whole-system setup. This was made removing the fans from my enclosures, sealing unused case vents and let four 120mm fans create a negative static pressure environment, so the air is mainly sucked from the enclosures. The case used for this was an old CoolerMaster RC-590. SATA enclosures are two iStarUSA BPN-DE350SS and one Norco SS-500 v3. I couldn't make an environmental controlled test, but clearly the BPN-DE350SS is way less obstructed than the Norco, and the drives are up to 10ºC cooler on the iStarUSA during a parity check. This mean you can use less powerful/more silent fans to keep your drives cool.

There's no webUI available for CrashPlan. Take a look at the first message for further instructions.