Tybio

That would be great, I can use the CPU temp/fans for the system side and the disk temps for the drive side....should be perfect if it is possible in the code :). Thanks for looking into this!

Ugh, had some cut-n-paste issues with the hex values, so ended up having to type them all out. Here you go, looks like it works as expected...though I can't confirm CPU_FAN2 will bundle with CPU_FAN1, but it seems to be likely. root@Tower:~# ipmi-raw 00 30 45 01 01 rcvd: 45 00 root@Tower:~# ipmisensors -t fan ID | Name | Type | Reading | Units | Event 808 | CPU_FAN1 | Fan | 1500.00 | RPM | 'OK' 875 | CPU_FAN2 | Fan | N/A | RPM | N/A 942 | SYS_FAN1 | Fan | 1800.00 | RPM | 'OK' 1009 | SYS_FAN2 | Fan | 2200.00 | RPM | 'OK' 1076 | SYS_FAN3 | Fan | 2400.00 | RPM | 'OK' root@Tower:~# ipmi-raw 00 30 70 66 01 00 32 rcvd: 70 00 root@Tower:~# ipmisensors -t fan ID | Name | Type | Reading | Units | Event 808 | CPU_FAN1 | Fan | 800.00 | RPM | 'OK' 875 | CPU_FAN2 | Fan | N/A | RPM | N/A 942 | SYS_FAN1 | Fan | 1800.00 | RPM | 'OK' 1009 | SYS_FAN2 | Fan | 2200.00 | RPM | 'OK' 1076 | SYS_FAN3 | Fan | 2400.00 | RPM | 'OK' root@Tower:~# ipmi-raw 00 30 70 66 01 00 64 rcvd: 70 00 root@Tower:~# ipmi-raw 00 30 70 66 01 01 32 rcvd: 70 00 root@Tower:~# ipmisensors -t fan ID | Name | Type | Reading | Units | Event 808 | CPU_FAN1 | Fan | 1500.00 | RPM | 'OK' 875 | CPU_FAN2 | Fan | N/A | RPM | N/A 942 | SYS_FAN1 | Fan | 1000.00 | RPM | 'OK' 1009 | SYS_FAN2 | Fan | 1100.00 | RPM | 'OK' 1076 | SYS_FAN3 | Fan | 1200.00 | RPM | 'OK' root@Tower:~# ipmi-raw 00 30 70 66 01 01 64 rcvd: 70 00 root@Tower:~# ipmi-raw 00 30 45 01 02 rcvd: 45 CC

Oddly, they show as expected from the documentation! That might be a first eh? root@Tower:~# ipmisensors -t fan ID | Name | Type | Reading | Units | Event 808 | CPU_FAN1 | Fan | 1000.00 | RPM | 'OK' 875 | CPU_FAN2 | Fan | N/A | RPM | N/A 942 | SYS_FAN1 | Fan | 1200.00 | RPM | 'OK' 1009 | SYS_FAN2 | Fan | 1400.00 | RPM | 'OK' 1076 | SYS_FAN3 | Fan | 1600.00 | RPM | 'OK' root@Tower:~# In this case I have 1 PWM hub in SYS_FAN3 for the Drive side of the case, and 1 PWM hub in SYS_FAN2 for the system side. SYS_FAN1 is the single fan at the back behind the CPU and CPU_FAN1 is obviously the fan on the cooler. My real goal is to be able to set a profile for SYS_FAN3, I can either let the MB control the rest, or have another profile for them...I'm more than willing to rejigger my hubs/ports/whatever....but without 2+ profiles I'm going to have issues balancing the air flow properly.

That would be fine! I have one connection for the Drive side anyway. I think the issue is that this BMC is only exposing one group, or the plugin doesn't know how this new board is splitting them. Unless I'm missing a configuration somewhere?

After reading a great deal of the thread...but not all I admit. I'm not sure that th X11SCA follows the normal Supermicro setup It looks like IPMI exposes FAN1-5, but they break down like this: FAN1&2: CPU FAN3-5: System I wouldn't mind doing all fan control via IPMI tool, but with my case (D600) having two sides...one for the system and one for drives, I have to be able to setup two fan profiles. Is there any way to do that with this plugin?

Hey there, just upgraded to the X11SCA in my sig and I only see fan control for FAN1234, this board seems to have 5 fans and they show up in the list as FAN1-FAN5 with 1 and 2 being CPU fans and the other 3 case fans. I'd really like to have the MB control all the headers (CPU Side) and have this plugin control one header (I have 6 fans on the drive side of the chassis via a PWM hub). Is that possible? Any way to map one of the fan headers to the FANA structure I've read about (But don't see in my settings)?

Found a review of the ASRock version: ASRock Ultra Quad M.2 Card Read more: https://www.tweaktown.com/reviews/8542/asrock-ultra-quad-2-card-16-lane-aic-review/index.html They make a big deal about how the orientation of the slots in this is better...but really these are just adapters. I'd think the only real delta would be in heat dissipation and fan noise.

I'm really struggling with two issues, the first is disk spin up and thus my using this addon...the second (and the root problem) is that shares stop during disk spin-up...but that's for other posts. i /just/ had a disk spin up, with nothing noted in the addon. Is there any known source of spin-ups that wouldn't show an inotifiywait result?

One more question, have you got this plugged into a UPS or Kill-A-Wat? I'd love to know what the idle draw is.

I have a case with no side fan, but I have good front->back fans over the MB...and these cards are fine, not a lot of airflow so you don't need a jet engine...but it does need some air moving over the heat syncs.

Very nice build, almost exactly what I'm going to do but I'm waiting another month or two to see if there is a new TR chipset like there was with the x470. I'd love to get a TR Taichi like the x470 Prime with 10GBE onboard. This will also let me ditch the HBAs as the board will have enough SATA ports On the case front, there was a great deal for the PC-D600 in the US a month ago so I picked that up for my new build...I /love/ the case, I can fit anything I want in it...but it is a little large being double wide :). Have 3 3-in-5 trayless istars in it for 15 hot swap disks, with the TR I'll move Cache to NVMe along with VM SSD. One question, can you confirm the ASRock BIOS lets you set the LED color, or at least turn the LED on the MB off? Case Link: http://www.lian-li.com/pc-d600/

Hurm, I think I need to look into what the "auto" setting does . Perhaps I should just turn it on.

Auto, this is a recent upgrade so I'm still settling into 6.5. I could turn it on, not going to hurt anything, but with a nice 'net facing firewall I don't really see the point so I left it defaulted.

Just updated and I'm getting connection_reset messages when trying to go to the plugin. I've disabled, and re-enabled a few times. Syslog looks fine, and the process is running. Not sure what other debugging would be helpful? Ok, I'm not running SSL and it looks like things are broken: root@Storage:/mnt/disk1/Backups# cd /usr/local/emhttp/plugins/unbalance root@Storage:/usr/local/emhttp/plugins/unbalance# killall unbalance root@Storage:/usr/local/emhttp/plugins/unbalance# ./unbalance I: 2018/05/12 20:42:12 app.go:51: unbalance v5.2.0-1070-aea11c7-v2018.05.12 starting ... I: 2018/05/12 20:42:12 app.go:59: Using config file located at /boot/config/plugins/unbalance ... I: 2018/05/12 20:42:12 server.go:54: Starting service Server ... I: 2018/05/12 20:42:12 server.go:71: Serving files from /usr/local/emhttp/plugins/unbalance I: 2018/05/12 20:42:12 server.go:130: Server started listening https on :6237 I: 2018/05/12 20:42:12 array.go:46: starting service Array ... I: 2018/05/12 20:42:12 planner.go:52: starting service Planner ... I: 2018/05/12 20:42:12 core.go:101: starting service Core ... W: 2018/05/12 20:42:12 core.go:116: Unable to read history: open /boot/config/plugins/unbalance/unbalance.hist: no such file or directory I: 2018/05/12 20:42:12 app.go:73: Press Ctrl+C to stop ... echo: http: TLS handshake error from 192.168.1.7:56665: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56666: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56667: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56668: tls: first record does not look like a TLS handshake

Fixed for me too, great work as always!

Got it, thanks for clarifying! That's great information, I think what I'll do is use some Molex runs with SATA adapters, that way I can get it down to 5 drives per PSU run with one of the runs "splitting" to feed the two SSDs on the side. I'd think that's going to be about as good as I can possibly balance things.

Help me out, I don't think I'm following. If startup is 2A then how could one avoid going over 1.5A for SATA power even with dedicated PS-drive modular cables? (Not to mention that most modular PSUs only have 4/5 "accessory" connections for things like drives) I'm sure I'm not following and we are somewhere in the middle. Like for 15 drives use 3xSATA power split properly or somesuch. Remember, the cages have 2xSATA power each, so by definition the best I can do is 2.5 drives per SATA power.

There is a post here about ordering extras, the PSU is this one: https://www.amazon.com/gp/product/B01HXYRJYK/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 so fully modular. Another user posted a source for cables, perhaps I'll just get 2 more as the Seasonic comes with 2xSATA Power and 4xSATAPower. I could home run all my devices with 4 of the 2x cables and never have to worry about power again.

The Seasonic has a 6-pin connector on the PS side :). I'm sure that the power supply can deliver the load, the reason I'm checking in is to make sure that the SATA cable can carry enough power for 3 5-in-3 cage from the power supply to them (2xSATA power connection for each cage).

Quick question all, I'm getting a seasonic 650W for my new build, but it only comes with 6xSATA power, I need to run 3 5-in-3's that each take 2 connectors and 2 SSDs outside of the 5-in-3s. In my old system I just had a sea of Molex splitters and ran off of two power supply lines...however I'm wondering if you can run 3x5-in-3 off one 6-pin connection to the power supply via an extender, or if I should split them between two (which would mean ordering another cable). This will power 15 drives, Mostly 8+TB IronWolfs at this point.

This is great info! Thanks a lot for posting, I've been working around a lack of 6-pins for a while...much better to get the right ones than do adapters and splitters!

They have the PC-A79 with 3 fans up front, not sure they are on a door however.

Best option I've seen to date is this: Not run it myself, but thought I'd point it out.

The file is in your library, your library isn't in the docker. Just install the Nerdpack plugin and then add mediainfo to unraid and process the file. Mediainfo output isn't going to change based on running it from within the docker or not (And if it does, we have a much bigger problem here

Thanks for the update! I'll check things over the next few days...really love the new Gather feature