xamindar

I would just like to say thank you for including the it87 hardware monitoring module and to please keep it in future builds. I just replaced my unraid server motherboard with an ASUS C60M1-I and I am able to control my fans without much modification (just had to add "modprobe it87 force_id=0x8721" to the go file). With my previous motherboard I had to compile the module myself for each unraid version so I could control the fan based on hdd temps. This thing sits next to my TV and I want it as quiet as possible without compromising temps too much. By the way, it couldn't hurt to have most of the other monitoring modules built as well just in case someone needs to use one. Just a suggestion. Again, thank you for this great system.

I just bought one to be my cache drive. Nice deal.

Yeah this WD warranty policy is being talked about all over the internet. It is really unfair.

all of you with samba issues, are you positive you did NOT set up users for write access in unraid? You are still able to connect to your unraid shares in this case, but are unable to make modifications due to samba security. Try maping the share as a drive and connect to it using your credentials set up in unraid if you had done that. I think this version of unraid configures samba incorrectly where it alows you to still connect with invalid cradentials but with only readonly access.

EDIT: Nevermind. I am loving this version so far. The features in the 5.0 series allowed me to ditch my unraid on full slackware and now I can have what I want with just the stock and addons.

I don't see how anyone in their right mind would consider this a good deal for these reasons: -It's a Seagate -Only a 1 year warranty -2TB drives can be half this price

Hi, I hope this is in the right forum. I am running unraid on a full linux distro and am having some issues after updating to the most recent unraid 5.0-rc8a. no matter what, the web interface will not work on first boot or first start-up of emhttp. I can kill emhttp and launch it again and then it will work. I can even launch another emhttp instance without killing the first so there are two running and it will work. Just for some reason the first time it is launched it will not display the web interface. I have looked through the logs and can't find anything strange. I can easily have the startup script set to launch emhttp, kill it, then launch it again and that works. But it is a dirty sollution. Any ideas what the cause could be? EDIT: I think I am just going to use unRAID the normal way from the USB drive now and stop with the full distro. Hopefully I will still be able to add my custom udev triggers. So disregard this question, I no longer need an answer.

Yes, but it only does it based on the temperature of the hard drives you specify in the script if that is what you want. Linux calls it PWM no matter which type you have, 3 or 4 pin. I'm using the script with 3 pin fans. No you don't have to start the service, just make sure the modules it found are loaded on boot up.

Yes, just build the f71882fg module and add it. I personally run unraid on a full arch linux distro and had to build my own kernel for it anyway. Just make sure you build from the same kernel source version that is used in unraid. I don't know why limetech doesn't just include all these modules in unraid, they don't take up very much space and make no difference on how it runs unless they are loaded. Some of the choices in the unraid kernel build seem pretty daft.

Yeah, it doesn't look like there is a driver for your sensor chip yet. The closest I can see in the 2.6.36 kernel is this driver. But it doesn't mention 8721 which I assume you have based on the ID. ???????????????????????? ITE IT87xx and compatibles ???????????????????????? ? CONFIG_SENSORS_IT87: ? ? ? ? If you say yes here you get support for ITE IT8705F, IT8712F, ? ? IT8716F, IT8718F, IT8720F and IT8726F sensor chips, and the ? ? SiS960 clone. ? ? ? ? This driver can also be built as a module. If so, the module ? ? will be called it87. ? ? ? Is this your chip? If so, it definitely isn't supported yet. From this it seems like a strange, rare chip only ASUS uses.

Not necessarily, it may just mean there is no driver in the Linux kernel for your chip (or you have none, unlikely with recent hardware). If sensors-detect didn't say "yes" to anything as you went through it then there probably isn't any driver for your hardware. You could possibly try a full slackware or any more recent linux and see if there is a driver (module) for it in more recent kernels.

Bah! I need to look more closely before I reply. Sorry, My previous post is not the issue. Here is your issue: Take a real close look at that... It wasn't able to read sbd, sbe, and sbf because they do not exist. It actually read your Hitachi drives just fine. Try changing all those b's to d's.

It's not getting the temperature for your two Hitachi drives. Maybe no one has used the script with Hitachi drives yet and they report a different name for the temperature value. Could you post the output of: smartctl -d ata -A /dev/sdb sdb or sdc, doesn't matter which you post. We will likely have to modify the script to look for something different. Right now it takes the value of Temperature_Celsius which both my Western Digital and Seagate drives label such as. I think I remember bubbaQ or someone making an actual program to report the temperature. It was a while ago. Anyone remember that? It might be a better way of doing things. Just have the script call that program and get the highest temp that way.

Yeah, install a full slackware as a test then run the same sensors-detect and make sure those sensors are loaded. Then test if you can control the fans. If that all works then you just need to compile a new kernel for unraid with the sensor modules for your hardware. You can follow the unraid wiki for the full slackware install to compile the kernel. Just make sure you go to the hardware sensors section in "make menuconfig" and enable those same sensor modules so they will be built (you can compile them into the kernel as an alternative but then sensors-detect will complain that they can't be found. But it should still work).

You need to research your chipset and what Linux kernel drivers work with it and what those drivers support. You are probably not going to find much help here I'm afraid as people here probably aren't kernel hackers. You might want to check lkml.org and maybe subscribe to that list to ask your questions.

Not the coolest build but it doesn't get too hot. The drives peak around 38 on hot days. Before I replaced the original hotswap fan with a quieter one it was cooler than that and the cpu fan never spun as that one fan kept everything else inside cool as well. But I needed less noise with it being right next to the TV. The new fan also spins down when the hard drives are cool enough or spun down themselves.

The other side:

Thought I would post my unRAID build. I wanted my first one to be small enough to take places (like to parents house to backup dad's photos and other things from their PCs). Found the perfect case thanks to bubbaQ's post. -Mini ITX atom mobo (nothing special) -old 80GB 2.5" laptop hard drive with full Slackware installed on it -Norco 5 in 3 hot swap bay

Don't confuse PWM in lm-sensors with PWM in the bios. I was reading about the 4-pin and 3-pin stuff when I was writing my script and don't know why lm-sensors calls everything pwm. The way I understand it real pwm (4 pin fans) are controlled by pulsing the power at different intervals while always staying at 12 volts. Apparently they are less likely to stall at lower rpms that way. But then there are 3 pin (non pwm) fans. The speed of them is changed by lowering the voltage. This way of changing speed does stall the fan at low rpms and depending on the fan depends on when it stalls. Also, you have to raise the power pretty high to get the fan to start again. Obviously 4 pin is better but 3 pin works just fine in most cases. I am pretty sure if you are using only 3 pin fans you need to select 3 pin in the bios. Don't worry about it not calling it pwm. Lm-sensors should still be able to control them. I have no idea why there is a server and a workstation setting though. If I were you I would try the three settings of disabled, 3 pin server, and 3 pin workstation and see if any of those change what you see under your hwmon0/devices area. Specifically look for pwm2_enable or see if fan2_input is reporting rpms.

Thats one of the problems. He doesn't have pwm_enable. The script wasn't able to change it and the directory listing he posted doesn't include it. His fans are spinning but fan2_input is not showing any rpm values. I don't really have much experience with this to know what the problem is. Looks like your board deffinately supports fan speeds. starcat, do the IPMI fan speeds ever change? They should constantly fluctuate a little as the fans don't go the exact same speed at all times. From one of your earlier posts they were all even numbers (800, 1500...). That doesn't make sense to me unless your monitors are rounding them to the closest 100 or something. In any case, sorry, I'm out of ideas. Sense you have the fan divisors (I don't on mine for some reason) you can read up on it here: http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors

Dang, I had a whole long reply typed out then my computer froze (laptop doesn't like to compile programs for a long time, the ram overheats). What do you see under /sys/class/hwmon/hwmon0/device ?? "ls /sys/class/hwmon/hwmon0/device" Are you running on a full slackware setup? Looks like you are if you are using lm-sensors. Looks like you either don't have 3-wire fans connected or your sensors do not have the correct circuitry connected on the mainboard to control them. Try the following while physically watching the fan: "echo 0 > /sys/class/hwmon/hwmon0/device/pwm2" - that is a zero. It should completely stop that fan. If it does stop spinning then you will be able to control them. "echo 255 > /sys/class/hwmon/hwmon0/device/pwm2" - will bring it back to full speed. If that does nothing at all then either linux is not allowed to change the speed or the board doesn't support it. The error the script gave means it was unable to set the file that tells whether linux controls the fan or the bios controls the fan. I haven't done much testing with different sensor drivers so don't know if there is a different spot for that in your case. Post a directory listing of /sys/class/hwmon/hwmon0/device so we can see if there is anything else that might help. Also "cat /sys/class/hwmon/hwmon0/device/fan2_input" should give you the rpm of the fan on pwm2.

Can anyone out there tell me if some manufacturers name the temperature field differently than "Temperature_Celsius"? I installed a new seagate drive and it was returning two temperature fields when I was just searching for "Temperature" by its self so I had to modify my script to look for the whole "Temperature_Celsius". If anyone has other manufacturers like samsung or hitachi (anything other than WD or seagate) it would be a great help if you could run the following command against those drives and verify if the temperature field is labeled as "Temperature_Celsius" or not. "smartctl -d ata -A /dev/sdX" (without quotes and where X is the drive leter, ie a, b, c and so on) You can find out which drive it is from the devices tab of the unraid web interface. You will see something like (sdb) right before the drive serial number. This command is not dangerous at all, just returns smart fields and may spin up some drives to get it, that's it. The temperature field is usually number 194 but not always. Thanks for any help. It will help to make this script work for any drive.

Woohoo! Got the new fan today and installed it into my unraid. This script works perfect! I had an issue with crontab at first but I must have had a typo in the crontab. Did a couple reboots and everything is working. The script runs every three minutes from cron and changes fan speed when heeded. No need for any special front panel display.

Lol, well thanks for "fixing" it so fast. Either no one tests it before using it or they all have cache drives in their systems. Thanks again for this script!

Just tried this. It seemed to run as it spun up all my disks and they were grinding away for a while. Then I ran "cache_dirs -q" to stop it and started it with "cache_dirs -F" so I can see output but now it just sits there on a blank line forever, no output, nothing. It seems to run fine without the -F option so I guess it's no big deal. Just thought it was supposed to spit back info as it ran.