dbknightx

Thanks, Hoopster. I've enabled the "Allow meshing to another access point" check box for all of my UAP-AC-LR devices and will just try powering up the UAP-AC-M when I get it to see if that will be enough for it to show up in the controller for adoption. Will give it a shot when the new device arrives on Monday and give an update on how it works.

Hi guys, I have been using this docker container with 3 UAP-AC-LR access points for the past couple of years and have been EXTREMELY happy. I am about to venture into uncharted territory by adding a UAP-AC-M-US to my network in mesh mode (no hardwired ethernet) - this will be used in my back yard to extend my signal. My usual steps for adding a new access point are to plug it into a hardwired ethernet cable, ssh to the device, mca-cli, set-inform, etc. so it can show up in the controller. I was planning on doing those same steps for this new device to get it registered, and then unplug the hardwired ethernet permanently to move it to its final location outside. is there any problem with this approach? Is configuring it in a wired manner going to give me problems when I want to switch it to mesh mode? Thanks in advance for any advice. Much appreciated! -David

I'm having a new issue with WebGrab+ since upgrading last week. It seems that the daily updates are no longer being run. Here is an excerpt from my log for the past 24 hours: Oct 24 10:17:01 83693064cfc5 CRON[48]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 11:17:01 83693064cfc5 CRON[51]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 12:17:01 83693064cfc5 CRON[54]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 13:17:01 83693064cfc5 CRON[57]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 14:17:01 83693064cfc5 CRON[60]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 15:17:01 83693064cfc5 CRON[63]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 16:17:01 83693064cfc5 CRON[66]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 17:17:01 83693064cfc5 CRON[69]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 18:17:01 83693064cfc5 CRON[72]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 19:17:01 83693064cfc5 CRON[75]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 20:17:01 83693064cfc5 CRON[78]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 21:17:01 83693064cfc5 CRON[81]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 22:17:01 83693064cfc5 CRON[84]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 24 23:17:01 83693064cfc5 CRON[87]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 00:17:01 83693064cfc5 CRON[90]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 01:17:01 83693064cfc5 CRON[93]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 02:02:01 83693064cfc5 CRON[96]: (nobody) CMD (/wg++/update.sh) Oct 25 02:02:33 83693064cfc5 CRON[95]: (CRON) info (No MTA installed, discarding output) Oct 25 02:17:01 83693064cfc5 CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 03:17:01 83693064cfc5 CRON[112]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 04:17:01 83693064cfc5 CRON[115]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 05:17:01 83693064cfc5 CRON[118]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 06:17:01 83693064cfc5 CRON[121]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 25 06:25:01 83693064cfc5 CRON[124]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Oct 25 06:27:22 83693064cfc5 CRON[123]: (CRON) info (No MTA installed, discarding output) Oct 25 07:17:01 83693064cfc5 CRON[197]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) If I restart the container, the update will run. Any thoughts? Thanks in advance.

Thanks so much. Working great now!

I've recently started having problems with the WebGrabPlusPlus docker. It had been working fine, but recently would not start, I believe after installing an upgrade in the past day or two. Here is the log: *** Running /etc/my_init.d/startup.sh... /etc/my_init.d/startup.sh: 44: /etc/my_init.d/startup.sh: sudo: not found *** /etc/my_init.d/startup.sh failed with status 127 Has anybody seen this or have any idea what could be happening? I've tried deleting and reinstalling the docker image but no luck. Thanks!

I'm late to this thread, but just happened to run into this format issue. I have an older 1TB drive that I added back into my system and was planning to use outside my array for TVHeadEnd DVR storage. I pre-cleared the drive successfully and whenever I go to format it the button changes to "Formatting" and then quickly switches to "Formatting Failed". I've tried the latest version of the plugin that you just updated and I still seem to be seeing the same problem. Here is what the log shows for my latest attempt: Apr 12 12:15:30 Clearing partition table of disk '/dev/sdn'. Apr 12 12:15:30 Reloading disk '/dev/sdn' partition table. Apr 12 12:15:30 Creating a 'msdos' partition table on disk '/dev/sdn'. Apr 12 12:15:30 Creating a primary partition on disk '/dev/sdn'. Apr 12 12:15:30 Formatting disk '/dev/sdn' with 'xfs' filesystem. Apr 12 12:15:30 Reloading disk '/dev/sdn' partition table. Am happy to provide more info if it helps debug.

Sure. Here you go: root@Tower:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 17 | CPU_FAN1_1 | Fan | N/A | RPM | N/A 18 | CPU_FAN2_1 | Fan | N/A | RPM | N/A 19 | REAR_FAN1 | Fan | 0.00 | RPM | 'At or Below (<=) Lower Non-Critical Threshold' 20 | REAR_FAN2 | Fan | 0.00 | RPM | 'At or Below (<=) Lower Non-Critical Threshold' 21 | FRNT_FAN1 | Fan | N/A | RPM | N/A 22 | FRNT_FAN2 | Fan | N/A | RPM | N/A 23 | FRNT_FAN3 | Fan | N/A | RPM | N/A 24 | FRNT_FAN4 | Fan | 2900.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A Three of my front four fans are still connected to the drive array backplane power (not the motherboard) which is why only FRNT_FAN4 is reporting readings. Not sure why the two REAR_FANs are showing zero, since they are definitely running. Hope this helps.

So I opened up my server last night and you are right - the fans are all 3-pin and not pwm fans. I'm planning on upgrading all of them and will do more testing once that has happened. Thanks for the guidance and am really looking forward to the forthcoming fan control feature. Six 5000 RPM fans running at full speed is EXTREMELY loud!

I think they are pwm fans. This is my case and it lists all fans as pwm: https://www.supermicro.com/products/chassis/3U/933/SC933T-R760.cfm I'll need to do some more digging and see if only certain fan headers on the motherboard support fan control. There are a bunch of them so I may just try moving them around and see if anything changes. Thanks for the help.

So I went through and tried setting each value individually to 32 (with all others set to 00) and refreshed the Sensors page to see if any fan speeds changed, and nothing seemed to make a difference. The two fans that are showing non-zero values (REAR_FAN1 and REAR_FAN2) are still showing the same values (which fluctuate between 5100 and 5200). I tried setting all values to 01 also just to see what would happen, and there was no effect. Every time I set the values I get back the same response: 01 C7 Anything else I should try?

dmacias, I've installed your plugin on my system and it is working great for monitoring. I'm EXTREMELY interested in the fan control capability, and am happy to assist with information gathering if I can help. I have an ASRock EP2C602 board and I've tried entering the command you mentioned earlier in the thread and it doesn't seem to be working. ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 --debug This outputs: root@Tower:/# ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 --debug ===================================================== OEM - Unknown Request ===================================================== [ HEX DUMP ..... ] = HEX[ 9B] [ 01h 00h 00h 00h 00h 00h 00h 00h ] [ 00h ] ===================================================== OEM - Unknown Response ===================================================== [ HEX DUMP ..... ] = HEX[ 2B] [ 01h C7h ] rcvd: 01 C7 I assume this is not the expected output. Does this suggest that 3a is not the correct netfn for my motherboard? What should I try next? -David

Steven, I'm still waiting for my hardware to arrive, but am wondering what tool / plugin you were using to view the data above. Looks really useful! Thanks.

Thanks for the great suggestions, guys. I've decided to try the "passive" solution with the shroud and see how that performs. I ordered two of the Supermicro SNK-P0048P heat sinks from Newegg: http://www.newegg.com/Product/Product.aspx?Item=N82E16816101827 I'll report back once I've got everything installed and see how my temps hold up. It'll be a couple of weeks before I get around to doing that. Thanks again. p.s. My current system is based off of a 4-5 year old low end AMD CPU with a small active heatsink under the shroud, but I've never really spent much time focusing on performance. Unraid has always just been a file server to me, but v6 has changed all of that (as most of us in this thread must agree with or we wouldn't be spending all this money on dual Xeon rigs)

Hey all, First of all, a big thanks to the thread starter and all that have added to it over the past several weeks. My wallet is a bit lighter but my server is soon to be a LOT beefier! I've got 2 of the E5-2670s on their way, that I'll be running together on the ASRock board mentioned earlier in the thread. My question is this: I've got a Supermicro SC933 3U chassis that has 15 hot swap drive bays along the front, with 4 fans pulling air from the front and pushing the air through an air shroud over the motherboard and out the back with 2 additional exhaust fans. The shroud creates a pretty good air flow over the motherboard, but prevents me from having any tower-style cpu fans on top of the cpus (like the Dynatron R17). I seem to have 3 options: [*]Keep the shroud and use a large passive heatsink like the Dynatron R8 - aligned so the fins are parallel to the shroud-assisted air flow [*]Keep the shroud and use a top mounted fan heatsink like the Titan TTC-NA43TZ/CU35 [*]Remove the shroud and use a Dynatron R17 tower-style fan I'm leaning towards the passive heatsink, assuming that the shroud is already pulling a huge amount of cool air directly over the motherboard and thus through the heatsink fins. Thoughts? Thanks very much in advance. -David

Same problem here. Anybody know if there is a way to go back to the previous version while we wait for a fix?