spl147

Members
  • Posts

    488
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by spl147

  1. does that mean that 5.0.5 will not get to benifit from webGUI enhancements from here on? And will 5.0.6 fix this?
  2. here is sensors-detect root@SERVER:/boot/scripts# sensors-detect # sensors-detect revision 6215 (2014-01-26 22:52:57 +0100) # Board: ASRock E3C204 This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors' Success! (address 0x290, driver `nct6775') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... Success! (confidence 4, driver `to-be-written') Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) Module i2c-dev loaded successfully. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca0 Chip `IPMI BMC KCS' (confidence: 4) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (confidence: 9) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. Warning: the required module nct6775 is not currently installed on your system. Check http://www.lm-sensors.org/wiki/Devices for driver availability. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OK
  3. root@SERVER:~# sensors coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +49.0 C (high = +80.0 C, crit = +85.0 C) Core 0: +49.0 C (high = +80.0 C, crit = +85.0 C) Core 1: +48.0 C (high = +80.0 C, crit = +85.0 C) nct6776-isa-0290 Adapter: ISA adapter in0: +0.98 V (min = +0.00 V, max = +1.74 V) in1: +1.87 V (min = +0.00 V, max = +0.00 V) ALARM in2: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM in3: +3.28 V (min = +0.00 V, max = +0.00 V) ALARM in4: +0.08 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM in6: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM in7: +3.47 V (min = +0.00 V, max = +0.00 V) ALARM in8: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) CPU Temp: +55.0 C (high = +0.0 C, hyst = +0.0 C) ALARM sensor = thermistor MB Temp: +45.0 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor AUXTIN: -62.0 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor PCH_CHIP_TEMP: +0.0 C PCH_CPU_TEMP: +0.0 C PCH_MCH_TEMP: +0.0 C cpu0_vid: +0.000 V beep_enable: disabled
  4. root@SERVER:/boot/scripts# pwmconfig # pwmconfig revision 5770 (2009-09-16) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0/device is coretemp hwmon1/device is nct6776 Found the following PWM controls: hwmon1/device/pwm1 hwmon1/device/pwm2 hwmon1/device/pwm3 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon1/device/fan1_input current speed: 0 ... skipping! hwmon1/device/fan2_input current speed: 0 ... skipping! hwmon1/device/fan3_input current speed: 0 ... skipping! hwmon1/device/fan4_input current speed: 0 ... skipping! hwmon1/device/fan5_input current speed: 0 ... skipping! There are no working fan sensors, all readings are 0. Make sure you have a 3-wire fan connected. You may also need to increase the fan divisors. See doc/fan-divisors for more information.
  5. yea, unfortunately niether of those links tell me where/how to install the module u posted, i tried modprobe nct6775 with and without the location, and i get module not found
  6. Yea, but im not gonna run v6 beta for quite some time, 5.05 is damn near perfect, just need that driver or the updated kernel
  7. i recently purchased a ASRock E3C204 MB. great board, i works fine except the super i/o chip for fan control doesnt have a driver in the newest 5.0.5 build, it is supported as of kernel 3.12. i guess my question is can some one add the driver? its here:https://github.com/groeck/nct6775 or recompile unraid 5.0.5 with the 3.12 kernel?
  8. since the new webgui shows non array disks, can we get a mount/umount button as well?
  9. then why is it on the plugin page of the new webGUI?
  10. S.N.A.P. plugin install fails.... /usr/local/emhttp/plugins/webGui/scripts/plugin Install Snap Snap-5.0-1.plg Installing Snap (Snap-5.0-1.plg) installing plugin: Snap-5.0-1 file /tmp/preSnapInstallCleanup.sh: successfully wrote INLINE file contents /bin/bash /tmp/preSnapInstallCleanup.sh ... success file /tmp/prepareForSnapInstall.sh: successfully wrote INLINE file contents /bin/bash /tmp/prepareForSnapInstall.sh ... version is=5.08 Downloading bundle installing plugin: Download_SNAP_bundle file /tmp/snap/snapBundle.tar: downloading from http://unraid-snap.googlecode.com/files/snap-5.08-1.tar ... bad download, deleting failed
  11. does the cache drive have to be formatted to rieserfs? can it be formatted to say fat32 or ntfs with the r/w driver installed?
  12. has anyone got siriproxy up and running on unraid 5.x? i am looking to use a ip driver to control my control4 system using siri, just need to get the siriproxy running on unraid.... any help would be greatly appreciated!!!
  13. What the hell is the difference? Final or beta rc? If it works who cares what the version says??? Anydvdhd is and always will be beta.... Dont make a difference at all.... Everyone bitches and whines cause they want the version to say final.... Stupid, stupid, stupid
  14. i use the ubnt unifi UAP for wifi, i would like to integrate the controller software to run from my unraid server.....is it possible? no idea.... http://forum.ubnt.com/showthread.php?t=45945
  15. i currently am running 5.0 RC 8a...it runs flawless for me.....i have 8 3tb wd30eurs drives non 4k alligned....what is the best way to convert to 4k alligned without loosing any data?
  16. 6 cards confirmed for the second order......need 4 more.....anyone else interested?
  17. Is there the possibility to pay for the lot via paypal? If so, I am interested in one or both but only have a short timeframe. Living in Europe and relatives will be hopping over from the US for vacation/visit within a week or so...shipping needs to arrive in time, hence. regards, Ford PM sent