dbknightx

Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by dbknightx

  1. 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.
  2. 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
  3. 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.
  4. 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!
  5. 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.
  6. 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.
  7. 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!
  8. 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.
  9. 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?
  10. 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
  11. 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.
  12. 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)
  13. 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
  14. Same problem here. Anybody know if there is a way to go back to the previous version while we wait for a fix?
  15. This nonsense caused me to switch to Sonarr, and I'm enjoying it much better so far. Good riddance SickRage!
  16. I've gotten myself into a bit of a bind and need some help. When I first started building my server (in November of last year), I started with a couple of WD20EARS drives. When I first installed them in the server I did NOT install the jumpers. My memory is a bit sketchy but I believe I completely pre-cleared them without jumpers before realizing that jumpers were needed for unRAID. I installed the jumpers and pre-cleared them once again. Despite some error messages in the syslog (I know, I should have paid more attention to them) they added just fine to the array and I've been using them successfully ever since. From an operational standpoint they've been fine. Here is an example of some of the errors I'm getting in my syslog for one of the drives: Mar 1 18:43:35 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 1 18:43:35 Tower kernel: ata10.00: irq_stat 0x40000001 Mar 1 18:43:35 Tower kernel: ata10.00: failed command: READ DMA EXT Mar 1 18:43:35 Tower kernel: ata10.00: cmd 25/00:01:af:88:e0/00:00:e8:00:00/e0 tag 0 dma 512 in Mar 1 18:43:35 Tower kernel: res 51/01:01:af:88:e0/06:00:e8:00:00/e0 Emask 0x1 (device error) Mar 1 18:43:35 Tower kernel: ata10.00: status: { DRDY ERR } Recently I tried upgrading to 5.0 beta (first 4, then 5, then 6) and in every instance all of my drives showed up fine EXCEPT for these two. I posted a syslog in the beta 6 thread and limetech kindly pointed out that I had a huge number of errors on those two drives. Apparently something in 5.0 is pickier about drive errors than 4.x. Some more research today suggested that it all had to do with me first preclearing these drives without the jumpers installed. So now I'm trying to figure out what my best option is to fix this problem. I'm currently copying all of the data off one of those drives, and was going to remove the jumper, run preclear 1.7 with the -a option on it (I'm running unRAID 4.7 btw) and then put it back into service. Repeat on the second drive. Will this solve the problem or am I just asking for more headaches by doing this? It seems that some people actually go and RMA their drives but that seems a bit drastic to me. Any suggestions are greatly appreciated. I can't believe what a pain those two little pieces of plastic have caused me... -David
  17. They are both connected to motherboard (ASUS M4A785-M) sata ports. You're right, there are a ton of errors in the logs. However, the system does start up and mount those drives successfully under 4.7. Every beta of 5.0 I've tried has failed similarly to this one. Anything else I can try? BTW I've never seen any errors reported in the 4.x web UI, but I admit I've not scanned through the syslog too closely in the past. These two drives were brand new ones I purchased at the time I set up my UNRAID server around 3 months ago. You should try booting 4.7 again and see if there are errors being reported in the system log. Those errors are happening in device discovery before any unRaid component is started. Looks like I have errors on two drives in 4.7 as well (they are numbered differently - ata9 and ata10 instead of ata2 and ata3). I'm sure they are the same ones, however. The drives do show up just fine in my array and if I didn't look in the syslog, I'd never know there were any issues. Not to take this thread off track any further, are there recommended posts / threads / wikis on how to go about fixing these two drives? -David syslog-dbknightx-4.7.txt.zip
  18. They are both connected to motherboard (ASUS M4A785-M) sata ports. You're right, there are a ton of errors in the logs. However, the system does start up and mount those drives successfully under 4.7. Every beta of 5.0 I've tried has failed similarly to this one. Anything else I can try? BTW I've never seen any errors reported in the 4.x web UI, but I admit I've not scanned through the syslog too closely in the past. These two drives were brand new ones I purchased at the time I set up my UNRAID server around 3 months ago. -David
  19. I'm continuing (since 5.0 beta 4) to have an issue where two of my drives are showing up missing. I didn't try pre-beta 4 so I don't know if it is a new problem. It is not cabling related as everything works fine if I revert to 4.7. Any ideas what may be going on? Screenshot and syslog attached. -David syslog.txt.zip
  20. I made a backup of my flash drive before installing 5.0 and simply restored it. Good as new.
  21. I'm experiencing this exact same problem. In my case I have two drives with no id - both are WD20EARS. Looks like I'm heading back to 4.7... really wanted that AFP support though! -David
  22. Here you go. This is after preclear completed successfully, I powered down and added the jumper, and then powered up. ----- Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 1 243202 1953514552+ 0 Empty Partition 1 does not end on cylinder boundary.
  23. Sorry for the slightly OT post. I just built an Unraid server and am brand new so I wasn't aware of the jumper requirement for these drives. I have three of them in my system that are currently about 16 hours into a preclean (no jumpers). Do I need to stop and start over with a new preclean after installing these jumpers or can I just finish the preclean, add the jumpers, and then add the drives to my array? Where is a good place to find this sort of information about jumper requirements? I've got three other types of drives (WD10EACS, WD7500AACS, and ST31500341AS) that I'd like to eventually add to my array. Thanks! -David
  24. Mine came with a CBL-0068L as well. You were lucky. Mine didn't and when I contacted the seller they told me to take a hike since it wasn't spelled out in the auction. I just ordered one online ($9.95 shipped). -David