Everything posted by starcat
-
Temperature based fan speed control?
The T-Balancer bigNG will go inside and there wouldn't be any mess with your beautiful case. You connect the fans to the T-Balancer and the T-Balancer to an internal USB port. Then use the linux driver to control the fans depending on the HDD sensors. I am already ordering mine. Of course you should obligatory first try the scripts as they are for free anyway. However, they are not really easy to configure (and extend) and you will definitely need *some* Linux knowledge.
-
Temperature based fan speed control?
Get the T-balancer bigNG and connect the fans to it, then use a script to control their speed depending on actual SMART HDD (or CPU or chassis) temp.
-
Temperature based fan speed control?
Matt, great info, thanks! Could you also post the device path for the fans for this board or better your updated version of the script?
-
Temperature based fan speed control?
bubbaQ, thank you very much! I am just looking at the mCubed T-Balancer bigNG at http://www.sidewindercomputers.com/tbalancerbigng.html and I think it should do the job. Do you know if the Linux software (http://sourceforge.net/projects/xban/forums/forum/462785/topic/1271826) may be executed straight from unRaid (booted from USB, without full Slack install)? I think I am going to order it straight away... This should be a section in the FAQ! Great find!
-
Temperature based fan speed control?
Not yet. I am at the moment giving up on this. Tested from full Linux install, even Supermicro confirmed that this won't work with the X7SBE, fans are controlled only from the BIOS. I may connect the fans to an AMX cardframe with 3x VAIG cards (analog voltage out set to 0..12V) and make it login to unRAID and based on smart data and HDD temp, control the voltage on the fans directly. Sounds complicated but this is the best I have come up with. All other fan control solutions I have seen so far can't be controlled from scripts but are autonomous based on some temperature sensors.
-
Temperature based fan speed control?
I can confirm that the fan speed control script is working with the Supermicro X7SPA-HF-O Mini ITX mainboard! The fan device is /sys/class/hwmon/hwmon4/device/pwm4 The modified script is attached. And don't forget to use a 4-pin PWM fan with this script. unraid-fan-speed.sh.zip
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
BRIT, are there any controllers that prevents this? The freezing of a drive when spinning up other disks and implementing spinup groups as a solution to this, certainly neglects the idea of unRAID having independent disks and it's major benefit compared to traditional RAID arrays where all disks either sleep or spin. I mean, one either must be single user to an unRAID server or put all disks in a single spinup group to avoid freezing the second disk when another is already being read?!
-
Looking for better ideas how how to sleep/suspend my unraid box
Check your NIC settings that only wakeup on magic packet WOL is enabled and not on ARP requests. ethtool should only tell you the "g" option and not "a", this would explain why it goes up again (after the next broadcast happens in your network).
-
Pimp Your Rig
Joe, great build, looks nice and at an awesome price! Congrats!
-
Temperature based fan speed control?
bubbaQ, thanks for your hints. Can you recommend some PWM 4-pin fan board control that is software controllable from Linux? Must be good, cost doesn't matter. Other option would be to get a hardware fan control, one channel with control for my three fans, off in addition to three other speeds with selectable temperature should be fine. I may position the flat temp sensors between the disks in the Norco 4220 case. Would not be that precise like a software based option though. I still haven't got a reply from Supermicro regarding how I may vary fan speed on the X7SBE. Thanks again!
-
Pimp Your Rig
Seagate spec'ed temp for their drives is up to 60 degrees, and for the WD RE4-GP it is up to 55. While 47 is a bit hot for the WD2002FYPS it is within specs :-)
-
Temperature based fan speed control?
Well, I have two AOC-SAT2-MV8 PCI-X controllers but may change them against the PCI-E versions as they are also supported in unRAID and running well. May change the memory also depending on the mainboard. It's only that I already have those, but nothing stops me actually from swapping (except from loosing money). IPMI however is almost a must as I don't want to deal with monitor and keyboard at any time. I would need at least two PCI-E slots, best would be to have three 8x PCI-E. Intel NICs are also a must, because of performance and wake-up, etc.
-
Temperature based fan speed control?
Which boards are you guys using that allow software fan speed control? I would need 2 PCI-X slots preferable on two busses (but may theoretically change controllers to PCIe), IPMI, Intel GigE NIC, C2D 775 slot and preferably DDR2 800 ECC Memory as this is what I already have. 4 SATA ports are ok, 6 or 8 would be nice.
-
Temperature based fan speed control?
I found this file for the X7SBU (mine is X7SBE) and used it instead of /etc/sensors3.conf: http://www.lm-sensors.org/wiki/Configurations/SuperMicro/X7SBU Here the sensors output now: # sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +47.0°C (high = +78.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +44.0°C (high = +78.0°C, crit = +100.0°C) w83627hf-isa-0290 Adapter: ISA adapter +5.0V: +5.13 V (min = +6.42 V, max = +6.83 V) ALARM cpu0_vid: +1.519 V beep_enable:enabled w83793-i2c-0-2f Adapter: SMBus I801 adapter at 1100 CPU Core: +1.28 V (min = +0.92 V, max = +1.38 V) +1.25V: +1.26 V (min = +0.00 V, max = +2.05 V) VTT: +1.18 V (min = +0.99 V, max = +1.33 V) -12V: -12.36 V (min = -12.85 V, max = -11.46 V) DIMM: +1.82 V (min = +1.62 V, max = +1.98 V) +3.3V: +3.26 V (min = +2.96 V, max = +3.63 V) +12V: +12.00 V (min = +10.75 V, max = +13.25 V) +5V: +4.94 V (min = +4.49 V, max = +5.50 V) 5VSB: +4.97 V (min = +4.49 V, max = +5.50 V) VBAT: +3.20 V (min = +2.96 V, max = +3.63 V) disk fan1: 2591 RPM (min = 712 RPM) disk fan2: 2532 RPM (min = 712 RPM) disk fan3: 2551 RPM (min = 712 RPM) case fan1: 1809 RPM (min = 712 RPM) case fan2: 1819 RPM (min = 712 RPM) cpu fan: 1140 RPM (min = 712 RPM) CPU Temp: +52.0°C (high = +83.0°C, hyst = +78.0°C) sensor = Intel PECI Sys Temp: +50.0°C (high = +50.0°C, hyst = +45.0°C) sensor = thermistor beep_enable:disabled
-
Temperature based fan speed control?
Yes, I am attaching the output of pwmconfig below. pwmconfig.txt
-
Temperature based fan speed control?
Installed full Slackware 13.0. Ran sensors-detect, it outputs in /etc/sysconfig/lm_sensors that I need following modules in that order: ipmi-si coretemp w83627hf w83793 Loaded each of them manually by calling modprobe. Ran sensors again and voila, all fans are now shown (see below for output). So it looks like this monitoring hardware is definitely supported but unRAID is looking for fans1..3 on the w83627hf-isa-0290, Adapter: ISA adapter instead on w83793-i2c-0-2f, Adapter: SMBus I801 adapter at 1100. However, I did a find in /sys and couldn't locate any pwm?_enable files and this looks strange to me. Do I have to create them manually somehow? fan1..3 are the three fans located on the mid fanboard of a Norco 4220 case fan4..5 are the case fans located on the back of a Norco 4220 case fan7 is the CPU fan all are 4-pin PWM enabled fans # sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +46.0°C (high = +78.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +46.0°C (high = +78.0°C, crit = +100.0°C) w83627hf-isa-0290 Adapter: ISA adapter in0: +0.00 V (min = +1.09 V, max = +1.50 V) ALARM in1: +0.00 V (min = +1.09 V, max = +1.50 V) ALARM in2: +0.00 V (min = +2.82 V, max = +3.79 V) ALARM in3: +3.06 V (min = +3.82 V, max = +4.06 V) ALARM in4: +0.00 V (min = +3.57 V, max = +4.02 V) ALARM in5: +0.00 V (min = +2.54 V, max = +1.89 V) ALARM in6: +0.00 V (min = +3.95 V, max = +2.03 V) ALARM in7: +3.38 V (min = +4.00 V, max = +4.08 V) ALARM in8: +3.26 V (min = +4.08 V, max = +3.82 V) ALARM fan1: 0 RPM (min = 0 RPM, div = 2) fan2: 0 RPM (min = 0 RPM, div = 2) fan3: 0 RPM (min = 25000 RPM, div = 2) ALARM temp1: +127.0°C (high = +45.0°C, hyst = -69.0°C) ALARM sensor = thermistor temp2: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor temp3: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor cpu0_vid: +1.519 V beep_enable:enabled w83793-i2c-0-2f Adapter: SMBus I801 adapter at 1100 VcoreA: +1.28 V (min = +0.92 V, max = +1.38 V) VcoreB: +1.26 V (min = +0.00 V, max = +2.05 V) in2: +1.18 V (min = +0.99 V, max = +1.33 V) in3: +0.50 V (min = +0.40 V, max = +0.67 V) in4: +1.82 V (min = +1.62 V, max = +1.98 V) in5: +3.26 V (min = +2.96 V, max = +3.63 V) in6: +1.00 V (min = +0.90 V, max = +1.10 V) +5V: +5.09 V (min = +4.64 V, max = +5.65 V) 5VSB: +5.09 V (min = +4.64 V, max = +5.65 V) Vbat: +3.20 V (min = +2.96 V, max = +3.63 V) fan1: 2591 RPM (min = 712 RPM) fan2: 2523 RPM (min = 712 RPM) fan3: 2528 RPM (min = 712 RPM) fan4: 1802 RPM (min = 712 RPM) fan5: 1819 RPM (min = 712 RPM) fan6: 0 RPM (min = 712 RPM) ALARM fan7: 1142 RPM (min = 712 RPM) fan8: 0 RPM (min = 712 RPM) ALARM fan9: 0 RPM (min = 712 RPM) ALARM fan10: 0 RPM (min = 712 RPM) ALARM temp1: +51.0°C (high = +83.0°C, hyst = +78.0°C) sensor = Intel PECI temp2: -103.0°C (high = +83.0°C, hyst = +78.0°C) sensor = Intel PECI temp3: -128.0°C (high = +83.0°C, hyst = +78.0°C) sensor = Intel PECI temp4: -128.0°C (high = +83.0°C, hyst = +78.0°C) sensor = Intel PECI temp5: +50.0°C (high = +50.0°C, hyst = +45.0°C) ALARM sensor = thermistor temp6: +46.0°C (high = +50.0°C, hyst = +45.0°C) sensor = thermistor beep_enable:disabled # lsmod Module Size Used by w83793 27256 0 w83627hf 23148 0 hwmon_vid 2684 2 w83793,w83627hf coretemp 5660 0 ipmi_si 38060 0 ipmi_msghandler 31276 1 ipmi_si appletalk 29452 20 ipv6 243508 12 pcmcia 33772 0 pcmcia_core 32016 1 pcmcia agpgart 29256 0 lp 9316 0 ppdev 7200 0 parport_pc 24036 0 parport 30700 3 lp,ppdev,parport_pc fuse 54008 1 joydev 9504 0 evdev 9152 3 thermal 15096 0 psmouse 41676 0 serio_raw 5024 0 i2c_i801 8784 0 sg 24912 0 e1000e 113100 0 rtc_cmos 10124 0 rtc_core 15992 1 rtc_cmos container 3132 0 rtc_lib 2332 1 rtc_core button 5708 0 processor 38600 1 thermal shpchp 31888 0 thermal_sys 10756 2 thermal,processor hwmon 2104 4 w83793,w83627hf,coretemp,thermal_sys
-
How-To Wake-On-ARP unRAID (also wake from PCH C-200, Apple, PCs, etc)
dlmh, this is great info, however this is the Apple-only implementation of things. The approach I was describing is a general one and an IGMP snooping capable switch will solve this by waking unRAID by reverse-ARP and not by Magic Packet. Magic Packet is nice but in order to fully automate wakeup (like Apple is doing) there are hardware specific additions needed (like the ones described in the Airport Express/Extreme) and will work only with dedicated OS'es, otherwise you must send the Magic Packet manually.. or use the method described in the OP :-) The WoD will also never work from dumb streaming clients with a special and unmodifiable firmware as they typically can't send a Magic Packet.
-
Temperature based fan speed control?
The generated /etc/init.d/lm_sensors file looks like this. MODULE_0=ipmi-si MODULE_1=ipmisensors MODULE_2=w83627hf MODULE_3=coretemp However, those modules can't be find and loaded. Should I get them from a Slackware distro and simply insmod them in that order? root@tower:~# lsmod Module Size Used by md_mod 37868 14 xor 12825 1 md_mod ata_piix 17076 4 e1000e 96516 0 sata_mv 19903 11
-
Temperature based fan speed control?
No, I just have stock unRAID, no other sensors related stuff has been done. What is the order for configuring and which commands should I run? Here is the output of sensors-detect root@tower:~# sensors-detect # sensors-detect revision 5337 (2008-09-19 17:05:28 +0200) 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. We can start with probing for (PCI) I2C or SMBus adapters. Do you want to probe now? (YES/no): YES Probing for PCI bus adapters... Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9 We will now try to load each adapter module in turn. Load `i2c-i801' (say NO if built into your kernel)? (YES/no): YES FATAL: Module i2c_i801 not found. Loading failed... skipping. If you have undetectable or unsupported I2C/SMBus adapters, you can have them scanned by manually loading the modules before running this script. To continue, we need module `i2c-dev' to be loaded. Do you want to load `i2c-dev' now? (YES/no): FATAL: Module i2c_dev not found. Loading failed, expect problems later on. We are now going to do the I2C/SMBus adapter probings. Some chips may be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. Some chips are also 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): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM78-J' 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 Probing for `IPMI BMC KCS' at 0xca0... Success! (confidence 4, driver `ipmisensors') Probing for `IPMI BMC SMIC' at 0xca8... No Some Super I/O chips may also contain 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): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... Yes Found `Winbond W83627HF/F/HG/G Super IO Sensors' Success! (address 0x295, driver `w83627hf') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Trying family `ITE'... No Some south bridges, CPUs or memory controllers may also contain embedded sensors. Do you want to scan for them? (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD K10 thermal sensors... No Intel Core family thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal and voltage sensors... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `ipmisensors' (should be inserted): Detects correctly: * ISA bus, address 0xca0 Chip `IPMI BMC KCS' (confidence: 4) Driver `w83627hf' (should be inserted): Detects correctly: * ISA bus, address 0x295 Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9) Driver `coretemp' (should be inserted): Detects correctly: * Chip `Intel Core family thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): YES Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules.
-
How-To Wake-On-ARP unRAID (also wake from PCH C-200, Apple, PCs, etc)
If you are interested in how you can make your unRAID server (or any other computer) wake up automatically as soon as another device connects to it, both from sleep or powered-off state, and also regardless of the protocol or application, then read on. What you need: 1. Intel NIC, that supports wake-on-ARP, i.e. ethtool must return the "a" option. This is not to be confused with Wake-On Magic Package, i.e. the "g" option. See here for a sample output of ethtool http://lime-technology.com/forum/index.php?topic=3657.msg63091#msg63091 The problem is that set that way the server will wake up each time a multicast broadcast ist sent within the network (which happens typically each couple of minutes), so the next thing we need in order to wake the server when a real access is made, is 2. A network switch that supports IGMP snooping. By snooping IGMP registration information within a frame, a list of workstations in the multicast group is created. The switch uses this list to intelligently forward packets to the appropriate workstations, i.e. the switch do not any longer have to multicast broadcast packets to all computers on the network as he knows which IP address is on which MAC address and limits the traffic to only the ports that have requested that traffic. A packet is actually sent through a port only when the server is accessed regardless of protocol or application (may be SMB, NFS, VNC, etc) and then the NIC wakes the server. More Info: Switches with IGMP snooping support include: Linksys SLM2008, the D-Link DGS-1216T, DGS-1224T, DGS-1248T and others The Apple world of computers including the Apple TVs implement Wake-On-LAN using Magic Packet. Sending the Magic Packet however is integrated and done automatically as soon as one Mac connects to the other. By using IGMP Snooping enabled network the same effect may be achieved between all computers in a network, between dumb streaming clients that do not allow installation of any software and any other servers in the network.
-
Temperature based fan speed control?
Thanks for the tip, in the meantime here the output of pwmconfig, the output looks strange to me. root@tower:/usr/sbin# pwmconfig # pwmconfig revision 5345 (2008-09-28) 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 w83627hf hwmon1/device is coretemp hwmon2/device is coretemp Found the following PWM controls: hwmon0/device/pwm1 hwmon0/device/pwm2 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon0/device/fan1_input current speed: 0 ... skipping! hwmon0/device/fan2_input current speed: 0 ... skipping! hwmon0/device/fan3_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. http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors Also root@tower:/usr/sbin# sensors w83627hf-isa-0290 Adapter: ISA adapter VCore 1: +0.00 V (min = +1.09 V, max = +1.50 V) ALARM VCore 2: +0.00 V (min = +1.09 V, max = +1.50 V) ALARM +3.3V: +0.00 V (min = +2.82 V, max = +3.79 V) ALARM +5V: +5.11 V (min = +6.40 V, max = +6.83 V) ALARM +12V: +0.00 V (min = +13.56 V, max = +15.26 V) ALARM -12V: -14.91 V (min = -1.83 V, max = -5.53 V) ALARM -5V: -7.71 V (min = +4.70 V, max = -1.33 V) ALARM V5SB: +5.67 V (min = +6.72 V, max = +6.85 V) ALARM VBat: +3.26 V (min = +4.05 V, max = +3.82 V) ALARM Fan1: 0 RPM (min = 1004 RPM, div = 64) ALARM Fan2: 0 RPM (min = 1004 RPM, div = 64) ALARM Fan3: 0 RPM (min = 1004 RPM, div = 64) ALARM temp1: +127.0°C (high = +45.0°C, hyst = -69.0°C) ALARM sensor = thermistor temp2: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor temp3: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor cpu0_vid: +1.519 V beep_enable:enabled coretemp-isa-0000 Adapter: ISA adapter Core 0: +68.0°C (high = +78.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +67.0°C (high = +78.0°C, crit = +100.0°C) Find'ing at /lib/modules/2.6.32.9-unRAID I don't see any libsensors and also modprobe -l | grep sensor doesn't show anything. pwmconfig reports the w83627hf chip and there is also the appropriate section in /etc/sensors3.conf, changes in the config file are reflected when I call /usr/bin/sensors. I suspect the appropriate module is simply missing...
-
Temperature based fan speed control?
That's a good idea. Are there any Slackware Live CDs available? I will try connecting the CD/DVD image through my IPMI card and run it from there over the network.
-
Temperature based fan speed control?
Which is the correct driver and how can I influence this? I am running stock unrAID 4.5.4 from an USB stick. Do I need to install full Slackware? Getting this to work is absolutely crucial.
-
Temperature based fan speed control?
Guys, got three of those 4-pin PWM 120mm DELTAs (3900 rpm with 148.34 CFM) http://www.newegg.com/Product/Product.aspx?Item=N82E16835706028&cm_re=120mm_fan_PWM-_-35-706-028-_-Product Also changed the CPU fan and both case fans to 4-pin PWM fans so that now all fans used in the system are 4-pin PWM. I set the BIOS to 4-pin PWM but I still can't get the unraid-fan-speed.sh script to work. echo 0 > /sys/class/hwmon/hwmon0/device/pwm? and echo 255 > /sys/class/hwmon/hwmon0/device/pwm? doesn't do anything. I also don't have pwm_enable. However when the server boots, fans rotate at full speed, then when the OS is running, speed is reduced. Config is in my sig. I am running stock unRAID 4.5.4. Any help highly appreciated.
-
Looking for better ideas how how to sleep/suspend my unraid box
Look here: http://lime-technology.com/forum/index.php?topic=6729