cyriouslydylan

root@HYDRA:/mnt/disk1/DockerApps# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 376918292 bytes 545599728025 (508.1 GiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 12 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.101 netmask 255.255.255.0 broadcast 192.168.0.255 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 85104066 bytes 554801007870 (516.6 GiB) RX errors 0 dropped 13916 overruns 0 frame 0 TX packets 39609148 bytes 126332393253 (117.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 52898 bytes 14164401 (13.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 53867 bytes 30521239 (29.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 376704744 bytes 545585615783 (508.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 213548 bytes 14112242 (13.4 MiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xfbf00000-fbf20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 137464 bytes 25960421 (24.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 137464 bytes 25960421 (24.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth17b05fb: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 8e:b6:70:ea:a8:35 txqueuelen 0 (Ethernet) RX packets 2115 bytes 859529 (839.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1924 bytes 1218400 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth638c205: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether a6:2a:88:78:4c:66 txqueuelen 0 (Ethernet) RX packets 19556 bytes 2062340 (1.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 21441 bytes 9256959 (8.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetha052b41: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 699 bytes 548224 (535.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 897 bytes 705751 (689.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:fb:a4:f1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fe:54:00:7c:e6:b8 txqueuelen 500 (Ethernet) RX packets 12455171 bytes 31394587093 (29.2 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 89716902 bytes 129283508307 (120.4 GiB) TX errors 0 dropped 5018 overruns 0 carrier 0 collisions 0 I'm a noob, but guessing from the ifconfig my docker needs to be pointed at br0 and not eth0 (default)? And if correct, I don't know how to go about doing that but I guess I can keep digging. I suspect it's down to the fact you've got bonding enabled on your Unraid machine as that's the only difference I see between my setup and yours. I went into webUI - edit page for docker; added a variable INTERFACE with a value of bond0 -- I can now access port 943. So I think my issue is resolved, but before I get too comfortable I just want to ask is this fix kosher? Also before this, I didn't realize I could do this. I.e. is there a technical reason it's mapped to eth0, or it's just default (you have to start somewhere)? Again, thank you for your assistance and time (not to mention patience to deal with this noob). Can I ask you how you added this interface? I'm also using a bond connection and cannot figure out how to set this up. I can currently only access the VPN web interface if I change the connection type to Bridge.

So I just installed this docker, and right now I'm having two issues: 1) I can't change my admin password, when I use the "docker exec -it openvpn-as xxxxxx admin" command, it returns "exec" "xxxxxx": executable file not found in $PATH" 2) I have my networking set up as a bond (bond0), how do I set my application to recognize this. Currently I can only access the webGUI if I set the Networking Type to Bridge (I want host, correct?)

I got a response from Supermicro. The response was a little underwhelming: I applied the warm reset, and then set it to optimal using the command above, and my fans lowered, and don't seem to be cycling. I'll keep an eye on this and see how it goes.

I figured it might be the case but was worth trying. I'll contact them and see if I can get the raw commands. When I first installed the fans, the RPM threshholds were out of the range of the plugin, which caused them to cycle up and down. When I fixed this, they stayed at their lowest setting, and I found one command a few pages ago that put them on their highest, and they haven't come down since. I'll see if I can get the raw commands from them though.

So I tried a bunch of these to see if they had any effect and they didn't. Here are the returns I got from inputting them. root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 01 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 91 5A 03 00 01 rcvd: 91 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 91 5A 03 00 02 rcvd: 91 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 91 5A 03 00 03 rcvd: 91 00 root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'OK' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 02 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 00 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 45 00 rcvd: 45 00 00

Yeah I noticed that one was pushing the higher-end of it's RPM limit. I'll have to look into that, because I believe that's the 140mm fan which should have a lower RPM limit. I'll clear that up and see if it fixes it. I set the upper limits to 2100, 2300, 2500 for each fan, and the lower to 300, 200, 100. I went back and re-tried the commands and it still didn't have an effect.

Still no change

hmm nope, looks like they are still sitting at 1900, 1400, and 1300: root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 02 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Thresh old' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Threshold' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A

IPMI fru displays FRU Inventory Device: BMC FRU (ID 00h) FRU Board Manufacturing Date/Time: 01/01/96 - 05:00:00 FRU Board Manufacturer: Supermicro FRU Board Serial Number: FRU Product Serial Number: My board is a Supermicro X11SSM-F http://www.supermicro.com/products/motherboard/Xeon/C236_C232/X11SSM-F.cfm ipmi-raw 00 30 70 66 01 00 32 This returned "rcvd 70 00" but didn't change any of my fan speeds. The same with 01 32 and 02 32. My fans are currently running at full speed, and this should have turned them down to half right? root@NeverlandUNRAID:~# ipmi-raw 00 30 91 5A 03 10 ff rcvd: 91 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 91 5A 03 11 ff rcvd: 91 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 01 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Threshold' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A root@NeverlandUNRAID:~# ipmi-fru FRU Inventory Device: BMC FRU (ID 00h) FRU Board Manufacturing Date/Time: 01/01/96 - 05:00:00 FRU Board Manufacturer: Supermicro FRU Board Serial Number: FRU Product Serial Number: root@NeverlandUNRAID:~# ipmi-raw 00 30 70 66 01 00 32 rcvd: 70 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 70 66 01 01 32 rcvd: 70 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 70 66 01 02 32 rcvd: 70 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 70 66 01 00 32 rcvd: 70 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 45 01 02 rcvd: 45 00 root@NeverlandUNRAID:~# ipmi-raw 00 30 70 66 01 00 20 rcvd: 70 00 root@NeverlandUNRAID:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 607 | FAN1 | Fan | 1900.00 | RPM | 'At or Above (>=) Upper Critical Threshold' 674 | FAN2 | Fan | 1400.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 1300.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A I tried all the above commands but none of them took my fans off of full-blast. I also tried the following and it doesn't seem to have any effect either. //for half speed ipmi-raw 00 30 91 5A 03 10 7f ipmi-raw 00 30 91 5A 03 11 7f

I'd love to test these out for you, I'm just unfamiliar with how to do so. Where can I implement these and report back to you. That same config file you had me export earlier? The ipmi-sensors-config command it's only for config options. I won't change fan speeds. If your drives are hot with fans at full speed, I'd look at the air flow in the case and over the drives. The ipmi-raw commands are entered in the command line. So you'd have to run one of the commands, it should give a received response or error and then see if the fans respond as intended. You can run ipmi-sensors -t fan to check fan speeds. The fans weren't running at full speed, which is why the HD temp was spiking. I just used ipmi-raw 00 30 45 01 01 and it put them all up to full speed, worked perfectly. If I want to use your temperature-dependent commands I just put this into the command line like so? if ($max_temp > 39) { # at least one hard drive is 40 deg C or higher # set fan speed control to Full `ipmi-raw 00 30 45 01 01` } elsif ($max_temp == 39 ){ # maximum drive temperature is 39 deg C # set fan speed to 50% duty cycle `ipmi-raw 00 30 70 66 01 00 32` } else { # all hard drive temperatures are 38 deg C or cooler # set fan speed control to Optimal `ipmi-raw 00 30 45 01 02` }

I'd love to test these out for you, I'm just unfamiliar with how to do so. Where can I implement these and report back to you. That same config file you had me export earlier?

So am I correct in that the Fan Control doesn't actually work for Supermicro Boards? Ever since I lowered the threshhold down, it seems that my drives are hotter now that my fans are spinning up to their max all the time. Is there a way I can manually increase fan speed or somehow get fan control working?

Awesome, thank you so much. I have the config file successfully exported, just need to get a proper word processor that can edit config files. It would make sense my fan range, because the ones I have are low RPM, between 650 and 1500 I believe. So for editing the file I should just change the ran RPM range values? For instance change: Section 607_FAN1 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 700.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 500.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 25300.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 25400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 25500.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection To something along the lines of: Section 607_FAN1 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection EDIT: Worked like a charm! My fans are finally at a steady speed!!

Yes I can see all these sensors now if I go to tools > IPMI. My event log is filled with "Lower Critical - going low ; Sensor Reading = 500.00 RPM ; Threshold = 500.00 RPM" warnings and errors. And in the IPMI settings, fan control has a big red "NOT FUNCTIONAL YET" next to "IPMI Fan Control" As far as the rest of the unRAID webgui is concerned, yes everything seems to be going fine. It looks like my FAN4 is the one constantly cycling.

Try ipmi-sensors from the command line. What does it show? "-bash: ipmi-sensors: command not found" I didn't have the ipmi plugin installed, but when I do install it I get this message repeating constantly: "-u: ipmi-fru: invalid hostname" Did the plugin show any errors when you installed it? Also what version of unRAID? Here's the link https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/plugins/ipmi.plg I reinstalled it and was able to get it to work, ipmi-sensors returns this: ID | Name | Type | Reading | Units | Event 4 | CPU Temp | Temperature | 28.00 | C | 'OK' 71 | PCH Temp | Temperature | 34.00 | C | 'OK' 138 | System Temp | Temperature | 27.00 | C | 'OK' 205 | Peripheral Temp | Temperature | 31.00 | C | 'OK' 272 | VcpuVRM Temp | Temperature | 31.00 | C | 'OK' 339 | DIMMA1 Temp | Temperature | 27.00 | C | 'OK' 406 | DIMMA2 Temp | Temperature | N/A | C | N/A 473 | DIMMB1 Temp | Temperature | 28.00 | C | 'OK' 540 | DIMMB2 Temp | Temperature | N/A | C | N/A 607 | FAN1 | Fan | 900.00 | RPM | 'OK' 674 | FAN2 | Fan | 800.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 800.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A 942 | 12V | Voltage | 12.13 | V | 'OK' 1009 | 5VCC | Voltage | 4.95 | V | 'OK' 1076 | 3.3VCC | Voltage | 3.38 | V | 'OK' 1143 | VBAT | Voltage | 3.08 | V | 'OK' 1210 | VCPU | Voltage | 0.86 | V | 'OK' 1277 | VDIMMAB | Voltage | 1.19 | V | 'OK' 1344 | 5VSB | Voltage | 5.00 | V | 'OK' 1411 | 3.3VSB | Voltage | 3.21 | V | 'OK' 1478 | VBMC 1.2V | Voltage | 1.20 | V | 'OK' 1545 | VPCH 1.0V | Voltage | 1.00 | V | 'OK' 1612 | Chassis Intru | Physical Security | N/A | N/A | 'OK'

Try ipmi-sensors from the command line. What does it show? "-bash: ipmi-sensors: command not found" I didn't have the ipmi plugin installed, but when I do install it I get this message repeating constantly: "-u: ipmi-fru: invalid hostname" Apologies, I'm dumb. I just got the command to work: ID | Name | Type | Reading | Units | Event 4 | CPU Temp | Temperature | 28.00 | C | 'OK' 71 | PCH Temp | Temperature | 34.00 | C | 'OK' 138 | System Temp | Temperature | 27.00 | C | 'OK' 205 | Peripheral Temp | Temperature | 31.00 | C | 'OK' 272 | VcpuVRM Temp | Temperature | 31.00 | C | 'OK' 339 | DIMMA1 Temp | Temperature | 27.00 | C | 'OK' 406 | DIMMA2 Temp | Temperature | N/A | C | N/A 473 | DIMMB1 Temp | Temperature | 28.00 | C | 'OK' 540 | DIMMB2 Temp | Temperature | N/A | C | N/A 607 | FAN1 | Fan | 900.00 | RPM | 'OK' 674 | FAN2 | Fan | 800.00 | RPM | 'OK' 741 | FAN3 | Fan | N/A | RPM | N/A 808 | FAN4 | Fan | 800.00 | RPM | 'OK' 875 | FANA | Fan | N/A | RPM | N/A 942 | 12V | Voltage | 12.13 | V | 'OK' 1009 | 5VCC | Voltage | 4.95 | V | 'OK' 1076 | 3.3VCC | Voltage | 3.38 | V | 'OK' 1143 | VBAT | Voltage | 3.08 | V | 'OK' 1210 | VCPU | Voltage | 0.86 | V | 'OK' 1277 | VDIMMAB | Voltage | 1.19 | V | 'OK' 1344 | 5VSB | Voltage | 5.00 | V | 'OK' 1411 | 3.3VSB | Voltage | 3.21 | V | 'OK' 1478 | VBMC 1.2V | Voltage | 1.20 | V | 'OK' 1545 | VPCH 1.0V | Voltage | 1.00 | V | 'OK' 1612 | Chassis Intru | Physical Security | N/A | N/A | 'OK'

I'm trying to get this to work on my Supermicro X11SSM-F and I don't seem to be having any luck. Could anyone point me in the right direction?

Worked like a charm! Thank you for the info!

Hey Everyone, I have a 5TB external hard drive thats NTFS formatted that I'm trying to mount. I installed this plugin without an issue, and it shows my one unassigned drive as mountable, but not the external USB drive. At the end of my system log, I have the following iness: Mar 26 20:37:02 NeverlandUNRAID udevd[16273]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [16385] terminated by signal 7 (Bus error) Mar 26 20:37:02 NeverlandUNRAID udevd[16271]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [16387] terminated by signal 7 (Bus error) Mar 26 20:37:02 NeverlandUNRAID udevd[16270]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [16386] terminated by signal 7 (Bus error) Mar 26 20:37:02 NeverlandUNRAID udevd[16272]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [16388] terminated by signal 7 (Bus error) I was hoping maybe they could give some insight as to why this might not be working for me? I was able to get my drive mounted, but now I can't seem to browse it's contents using dolphin or Krusader. I can click directly on it and view it's contents, but that doesn't help me move/sync data off of it. Thoughts?

If my System Autofan plugin isn't picking up a PWM controller at all, how can I rectify that? My motherboard is a Supermicro - X11SSM-F

How does the path work for this app? I have /data set to /mnt/user/Media/Downloads as that's where I have all my downloaded movies/files at, but in the app I get the error "Permission denied: /mnt/user/Media/Downloads/..." Edit: I see now you have to use your volume mappings. I have /data mapped to /mnt/user/Media/Downloads, so I use "/data" for the download directory.

I know this is a bit of an older thread, but I used QuietPC when choosing the fans for my build: http://www.quietpc.com/120mmfans <- this is the link to their 120mm fans. If you sort by noise level, then look at the amount of air it moves you can figure out a nice balance between noise and airflow. I went with the Nanoxia Deep Silence 120mm Ultra-Quiet PWM PC Fan, because from what I could see it was the best balance between noise and airflow.