October 29, 201510 yr Author Lol I just realized. Your CPU fan is probably NOT 4 Pin PWM That's your issue.
October 29, 201510 yr Lol I just realized. Your CPU fan is probably NOT 4 Pin PWM That's your issue. I thought the same and checked the CPU Fan I am using. It has 4 pin connector and the spec says it has PWM: http://www.newegg.com/Product/Product.aspx?Item=N82E16835118074
October 29, 201510 yr Author Lol I just realized. Your CPU fan is probably NOT 4 Pin PWM That's your issue. I thought the same and checked the CPU Fan I am using. It has 4 pin connector and the spec says it has PWM: http://www.newegg.com/Product/Product.aspx?Item=N82E16835118074 wow, okay... Does it have 4 wires? What happens if you plug CPU fan to FANA and try to echo 255 into it? What happens if you plug another fan in its place and also do 255? Another thing I can think of post screenshot of web interface with only fan sensors and showing thresholds
October 29, 201510 yr Author Also what do you have in your go file? I have #!/bin/bash # Sensors modprobe coretemp modprobe jc42 modprobe nct6775 # copy the sensor.conf file for use cp /boot/config/sensors.conf /etc/sensors.d # Start the Management Utility /usr/local/sbin/emhttp & # Copy fancontrol config cp /boot/config/fancontrol /etc/fancontrol # Start the Management Utility /usr/sbin/fancontrol &
October 29, 201510 yr Yes, the CPU fan pin has 4 wires (will double check in the evening) attached is the screenshot from IPMI web interface showing FAN sensors My go file does not have all the entries. Here is how it looks now: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp &
October 29, 201510 yr Author I think you didn't set your thresholds. This could be reason your fan keeps spinning and not slowing down. Here is my sensors.
October 29, 201510 yr I think you didn't set your thresholds. This could be reason your fan keeps spinning and not slowing down. Here is my sensors. This is the command I ran: ipmitool -I lan -U ADMIN -H *ip address* sensor thresh FAN1 lower 150 225 300 Should I run this instead: ipmitool -I lan -U ADMIN -H *ip address* sensor thresh FAN1 lower 0 0 0
October 29, 201510 yr Author Try and see what happens. Lower NR will spin fans up, other two will send you email i think.
October 29, 201510 yr Try and see what happens. Lower NR will spin fans up, other two will send you email i think. What are the values you used in the ipmitool command?
October 29, 201510 yr Author From my screenshot you can see 0 0 0 ( you just dont see first 0 because it's not shown)
October 29, 201510 yr From my screenshot you can see 0 0 0 ( you just dont see first 0 because it's not shown) I updated my thresholds. attached is the screenshot. Will try to run some tests once I get home. Will plug another fan in FAN1 to see if it responds to the tests. Will update the GO file as well. Will update with my results
October 29, 201510 yr Author You should pay attention to go file and understand what each line does. Don't just copy paste.
October 29, 201510 yr You should pay attention to go file and understand what each line does. Don't just copy paste. Thanks for the warning 1. I plan to add mod probe for the three sensors 2. Don't plan to add copy sensor.conf line (per wiki page this is not needed for Dynamix) 3. The other line I am not sure is copying the fancontrol: cp /boot/config/fancontrol /etc/fancontrol Comments/thoughts?
October 29, 201510 yr Author You should pay attention to go file and understand what each line does. Don't just copy paste. Thanks for the warning 1. I plan to add mod probe for the three sensors 2. Don't plan to add copy sensor.conf line (per wiki page this is not needed for Dynamix) My sensor conf simply has labels i am overriding. 3. The other line I am not sure is copying the fancontrol: cp /boot/config/fancontrol /etc/fancontrol The reason I am copying fancontrol is because fancontrol is erased every reboot from /etc/ I am making sure the config is there Last line starts up fancontrol for cpu. keep in mind dynamix plugin is ONLY for HDD temperature not CPU Comments/thoughts?
October 29, 201510 yr M3ki, Outstanding documentation of your progress and one sweet setup. It appears that you have two molex strands from the Seasonic to your backplanes, I would recommending adding more. Extras are available from Amazon. http://www.amazon.com/dp/B00X0L8TA4/ I also recommend stuffing the cable holes in the fanplate to prevent air leaking if you haven't done so already. It dropped my temps by 3-4 degrees.
October 29, 201510 yr Author M3ki, Outstanding documentation of your progress and one sweet setup. It appears that you have two molex strands from the Seasonic to your backplanes, I would recommending adding more. Extras are available from Amazon. http://www.amazon.com/dp/B00X0L8TA4/ I also recommend stuffing the cable holes in the fanplate to prevent air leaking if you haven't done so already. It dropped my temps by 3-4 degrees. Thank you, What do you mean adding more? I actually replaced second molex cable with one from another seasonic PSU, I have now 2 molex cables running to backplane PSU -> 3x and PXU -> 3x so it's much neater I have not stuffed the holes yet but I did stuff unused bays with styrofoam inserts i cut. My temps are currently 28 - 32 C so under 39 I am still transfering files from my synology build to unraid ~ 40 TB. I already setup my syncthing and time machine backups. I am trying to figure out how to setup DSM inside of KVM, it's so unintuitive. Another issue I am having is my drives keep spinning up and I cannot figure out why. I am already running cachedirs plugin but it won't help. at the same time this thread is turning into helping rajsri )
October 29, 201510 yr at the same time this thread is turning into helping rajsri LOL...and I appreciate it
October 29, 201510 yr Author at the same time this thread is turning into helping rajsri LOL...and I appreciate it No problem at all
October 29, 201510 yr Thank you, What do you mean adding more? You currently have 12 hard drives on a single strand. I would recommend lowering that to 8 at least. At hard drive spin-up you'll experience a voltage drop on the 12 volt line if all the drives are spun up simultaneously. Here is a post I made sometime back on the issue: http://lime-technology.com/forum/index.php?topic=15773.msg146800#msg146800
October 29, 201510 yr Author Thank you, What do you mean adding more? You currently have 12 hard drives on a single strand. I would recommend lowering that to 8 at least. At hard drive spin-up you'll experience a voltage drop on the 12 volt line if all the drives are spun up simultaneously. Here is a post I made sometime back on the issue: http://lime-technology.com/forum/index.php?topic=15773.msg146800#msg146800 Interesting, for now I only have 8 drives total so I will have to see how it goes when I add more drives. Btw it seems I have a different backplanes you do, I only have one molex per plane. Forgive my ignorance I am rusty with physics... The cables I have seem pretty solid. I was wondering how much of a difference running let's say 6 individual cables will it make vs 1 -> 3 molex would it really make? Chances are inside of the PSU they are still connected to same rail. If I am saying nonsense please correct me
October 29, 201510 yr Forgive my ignorance I am rusty with physics... The cables I have seem pretty solid. I was wondering how much of a difference running let's say 6 individual cables will it make vs 1 -> 3 molex would it really make? Chances are inside of the PSU they are still connected to same rail. It's a matter of number of copper strands available for the current to travel. If you know the gauge of the wire in question, you can get a pretty good idea of the difference with this calculator. Also keep in mind that every connection has a voltage drop associated with it, so the more paths and fatter the wires, the less voltage is lost between the single rail at the PSU and the drive at the end. The worst outcome is that when the drives all spin up at once for a parity check, or worse yet a read error spins up everything, one or more of the drives on the voltage starved strand fail to respond in time, causing more read errors or even drop the drive totally.
October 30, 201510 yr m3ki, In the IPMI Settings, what is the current setting for "Fan Mode"? Mine is set to "Set Fan to Standard Speed"
October 30, 201510 yr Author m3ki, In the IPMI Settings, what is the current setting for "Fan Mode"? Mine is set to "Set Fan to Standard Speed" Optimal, that allows for independent control of FANA vs rest i think
October 31, 201510 yr Thank you m3ki for such helpful step-by-step posts of your build. Admittedly, a lot of this went above my head, especially the part about option ROM and flashing firmware to IT mode. Some google searching has answered some questions, but I'm still pretty confused about the whole thing (I'll make a separate post asking the community about this stuff as I don't want to hijack your thread). I'm not computer savvy and I don't feel comfortable touching any type of code. I was going to build a server on the SM X10SRA-F (supports Xeon E5-2600/1600 v3 CPUs), but I don't want to touch any of the fan settings you've been doing. I know your SM motherboard is for the E3 CPUs, do you know if the X10SRA-F has the same headache with fan settings as yours does? If so, I think I'm going to avoid Supermicro motherboards altogether ...
October 31, 201510 yr Author Thank you m3ki for such helpful step-by-step posts of your build. Admittedly, a lot of this went above my head, especially the part about option ROM and flashing firmware to IT mode. Some google searching has answered some questions, but I'm still pretty confused about the whole thing (I'll make a separate post asking the community about this stuff as I don't want to hijack your thread). I'm not computer savvy and I don't feel comfortable touching any type of code. I was going to build a server on the SM X10SRA-F (supports Xeon E5-2600/1600 v3 CPUs), but I don't want to touch any of the fan settings you've been doing. I know your SM motherboard is for the E3 CPUs, do you know if the X10SRA-F has the same headache with fan settings as yours does? If so, I think I'm going to avoid Supermicro motherboards altogether ... Now I feel bad that I am scaring people off Here is my reasoning for going with supermicro board. Pros: Supports xeon supports ECC memory (this means data integrity + if I really wanted to use another solution, admittedly more power hungry ex. freenas, I could) onboard SAS ports fewer raid cards to buy IPMI <--- AWESOME!!!! you can connect to the computer and control it via web browser, no need to buy keyboard, mouse or extra screen (NOTE in any solution be it SM ipmi or intel AMT for some asrock mobos you NEED cpu that has built in videocard, you can see that on the ask intel site, my xeon does another model didnt) server grade, good build quality dual gigabit lan Cons: Well, not flexible in terms of fan control you have basic: standard, optimal settings, that's about it. In terms of an issue with option rom.... i think you would/could run into same issue with any other board. Keep in mind I shoved 2 extra raid cards in there but again all is solved now. If you're going with unraid or freenas or any software based raid arrangment you will NEED to flash your raid card into IT mode because you need to make the card to not appear as RAID card to OS. Steps I needed to get everything working: Install the motherboard Chose correct setting in the bios for add on raid cards in bios ( correct GEN, for m1015 it was gen2) Disable onboard SAS card to boot using option rom(option rom is simply a config utility) Flash m1015 -> it mode without option rom(no need for system to boot into that either) Flash second m1015 to IT mode. If you're a silent freak or you want good control of fans: configure linux fan control utility to control your cpu fan. configure autofan to control your array fans... That's about it, nothing scary. Plus I gotta say unraid has an awesome community and good people who are willing to help. Also why do you want such an expensive motherboard?
Archived
This topic is now archived and is closed to further replies.