starcat

I am attaching a ls -l output of "/sys/class/hwmon/hwmon0/device". Running stock unRAID 4.5.3 with a couple of installed packages, however nothing related to lm-sensors, at least not that I know of. ll the fans are attached using 3-wire cables and they are all different speeds as shown by the BIOS and IPMI card. pwmconfig itself reports the interface control chip: hwmon0/device is w83627hf Attaching the full output of pwmconfig below. This is my mainboard: http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBE.cfm Please take a look at the "Management" and "PC Health Monitoring" section. It mentions "status monitor with firmware / software speed control" for the FANs. I can write to pwm2 and change the value from 0...255, however the fan speed doesn't change. I can not open up the servers case right now, I am watching that the fan speed do no change on the IPMI card display for "Monitoring Sensors". I quite frankly think that Linux is not allowed to change the fan speed. This one is 0. Thanks much for all your efforts and help, highly appreciated! sys-class-hwmon-hwmon0-device.txt pwmconfig-output.txt

You just need to configure mail on unRAID and call it from the script. There are different mail systems available for unraid but in general emailing works perfect from unRAID. You may want to search the forum for "unraid_notify-2.53-noarch-unRAID.tgz" and install it, or just look here: http://lime-technology.com/forum/index.php?topic=2470.0

Xamindar, thanks for the script! I am running the Supermicro X7SBE mainboard and albeit I see the fans and their speed through the IPMI card from the BIOS, pwmconfig doesn't show them as controllable. Any hints as to what I might check? The fans are set in the BIOS to "3-pin optimized for server" and there is clearly speed control applied to them (there is another setting "full on 12V" which I have deselected). I have 5 fans in total each connected to each own header (2 for the case on the back and 3 on the mid fanboard) in addition to the 6th fan for the CPU. They are grouped in 3 groups (case, disk fans on mid fanboard and cpu) and all are 3-wire connected to the mainboard. Tried to set the BIOS to "3-pin optimized for workstations" but only the average RPM slowed down from 800/1500/1000 to 700/1400/900. I found this http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors and played with the fan divisors, set them from 1...64 in /etc/sensors3.conf, rerun sensors -s, then pwmconfig again without any change. Here the chip, a Windbond W83627HF than is used http://www.mjmwired.net/kernel/Documentation/hwmon/w83627hf Output of 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. This is what the IPMI card is showing me from the monitoring sensors: Sensor Type Sensor Name Sensor Status Sensor Reading OEM reserved #c0 CPU Temp Low Temperature Sys Temp OK 39 degrees C Voltage CPU Vcore OK 1.280 (+/- 0.004) Volts Voltage DIMM Volt OK 1.824 Volts Voltage 3.3V OK 3.248 Volts Voltage 5V OK 4.920 (+/- 0.012) Volts Voltage 12V OK 12.096 (+/- 0.048) Volts Voltage -12V OK -12.300 (+/- -0.050) Volts Voltage 5VSB OK 4.944 (+/- 0.012) Volts Voltage VBAT OK 3.184 (+/- 0.008) Volts Fan Fan1 OK 800 RPM Fan Fan2 OK 800 RPM Fan Fan3 OK 800 RPM Fan Fan4 OK 1500 RPM Fan Fan5 OK 1500 RPM Fan Fan6/CPU OK 1000 RPM Power Supply Power Supply OK Module / Board Thermal Trip OK System Firmware Progress BIOS OK When I run the script, it reports: root@tank:~# /boot/scripts/unraid-fan-speed.sh Highest temp is: 44 /boot/scripts/unraid-fan-speed.sh: line 78: /sys/class/hwmon/hwmon0/device/pwm2_enable: No such file or directory Setting pwm to: 255

WOL will work from powered off mode only if you have powered off the server by software, i.e. issuing the poweroff command. If you have powered it off by any other means or have disconnected the power cable in between, the WOL magic packet would not power on your server.

You may use rsync for instance and it is build into unRAID.

Why haven't you just replaced the 1TB Drives in the first Norco one by one with 2TB drives instead of buying a second case? Just curious, but looks good anyway :-)

In my oppinion without this future, simply sleeping unRAID and unnecessary spinning up all drives each time after WOL only to access one of them is a complete waste. THIS is must feature to use with WOL.

http://lime-technology.com/forum/index.php?topic=2555.msg20494#msg20494

Has anyone tried the parameter with those Seagates to stay spun down after WOL? Do they work as the WD Green drives using the jumper?

Great, thanks! I guess I would modify it to execute WeeboTech's secure powerdown and then WOL if needed. No S3 with a server board.

lewcass, is the script you just posted the regular s3 script that I might use (after customization of the custom section of course) in my environment? Thanks!

Which media players are you using?

I read over and over again through the forum and also on the Wiki that in order to mount NFS exports on OS X the insecure option have to be specified in unRAID. That is not true as Mac OS X defaults to using unpriviliged ports for NFS mounts but if the option -P is specified (on the Mac side) it will happily use ports below 1024. Use those guides to "secure" NFS mount folders from unRAID: Use this guide for Snow Leopard (10.6) http://kampmeier.com/chris/blog/?p=43 and this for Leopard (10.5) http://nedos.net/2007/11/10/nfs-in-mac-os-105-leopard/

lsof? It too doesn't show any processes being on /mnt/disk* Edit: I was also wondering what is the default access mode for files on unRAID? I have ownership set for everything to root:root and access rights to 750 for dirs and 640 for files. Can remember that I was changing this lately... But shouldn't have to do anything with the strange behaviour described above?! Edit2: Well, it is definitely cache_dirs spinning up the drives. I sync'ed on the cmdline a couple of times and them spun down the array from unRAID Main. After some time, the disks went up again, one at a time corresponding to the find processes started from cache_dirs... Edit3: I am running unraid_notify, can this be the cause? It says it won't send notification if disks are spun down though, wouldn't do anything to them to spin them up.

It used to work when I first installed/started it by hand. I added it to the go script and then after time had to reboot adding a new drive. Then I noticed that the drives won't spin down. Killed, started by hand and it worked again. Restarted again the server, same - no spin down. However, since last manual restart drives are still spinning and I don't know why.

I have cache_dirs 1.6.4 and unRAID 4.5 final. fuser don't show any processes on the /mnt/disk*. Also, I have about 130k files and 4GB memory. I don't have $PATH in my go. I just start /boot/scripts/cache_dirs -w -B Is it ok to have two cache_dir processes running? The one starts the other, it has its PID as parents PID in the second. root 300 1 0 Jan07 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -w -B root 3874 300 0 00:38 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -w -B

I am noticing some strange phenomenom. When I call cache_dirs -w -B from the go script, my drives do not spin down. When I kill the process and start it manually on the cmdline, same syntax, they will properly spin down after the specified amount of time. Any hints as to what might be causing this behaviour? For what it matters I am calling cache_dirs -w -B right before calling unMenu in my go script.

Joe, thanks much! Great help - I understand now.

I'll try again specifying explicitly the depth. Is maxdepth counting from /mnt/disk*/ downwards only, or starting with / ? I am running 4.5. I've read somewhere unRAID supports only 4GB main memory as it runs 32bit, no point adding more RAM, right? Edit: This is what I get when I execute the following. cache_dirs loops showing the same and don't terminate at all. The Test user share is a very small one. cache_dirs -B -w -F -v -e Archive -i Test Executing find /mnt/disk3/Test -noleaf Executing find /mnt/disk9/Test -noleaf Executed find in 0.011855 seconds, weighted avg=0.011855 seconds, now sleeping 5 seconds Executing find /mnt/disk3/Test -noleaf Executing find /mnt/disk9/Test -noleaf Executed find in 0.012200 seconds, weighted avg=0.012085 seconds, now sleeping 4 seconds

Just counted 119638 files. I have 4GB memory, can add 4 more if unRAID can see all 8? If cache_dirs support some Depth for scanning/caching, might add that too, I would care for depth=3 only.

I tried cache_dirs -w and all my drives are now not spinning down at all? I see in ps one cache_dirs -w per drive. When I manually try to spin down a drive, it immediately spins up again. I have started cache_dirs -w from the terminal (as I have not rebooted the server, otherwise it would be in the go script). Any hints?

Anyone out there with X7SBE with unRAID and configuration for S3?

Just got an email from Supermicro stating that the X7SBE supports S3 by default and that no jumpers have to be set. I doublechecked and ACPI is enabled in the BIOS. Still wondering why I can't suspend the system from unRAID? I have noticed lot of people are running unRAID with this mainboard, any hints?

The X7SBE indeed supports S3, however just reading the manual the default is off and a jumper must be set. PS2 Keyboard (KB)/Mouse Wake Up Select Enable to “wake your system up” from the S1, S3, S4 or S5 state. If this feature is set to Enabled, you will also need to enable the JPWAKE jumper by closing pins 1-2. (Please refer to Pg. 1-5 and Chapter 2 for more details). The default setting is Disabled. USB Wake Up This setting allows you to wake up the system from S3/S4 state. Make sure to set the proper It also says ACPI S3 optional on a digram... but the manual is definitely not clear on this and I can't find that jumper!!

Anyone has a hint for me? When I try to put my system into sleep mode, I get the following: root@startank:~# echo 3 > /proc/acpi/sleep -bash: echo: write error: No such device same with S5 root@startank:~# echo 5 > /proc/acpi/sleep -bash: echo: write error: No such device root@startank:~# ls -l /proc/acpi/sleep -rw-r--r-- 1 root root 0 Dec 12 02:31 /proc/acpi/sleep root@startank:~# cat /proc/acpi/sleep S0 S1 S5 I have enabled ACPI in the BIOS and root@startank:~# ethtool eth0 Supports Wake-on: pumbag Wake-on: g I am using 4.5 beta11. I was reading this thread and also following http://lime-technology.com/wiki/index.php?title=Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL) Anyone has any idea? Thanks much!