Jump to content

betaman

Members
  • Content Count

    497
  • Joined

  • Last visited

Everything posted by betaman

  1. Is support for nzbgetvpn dead? Is there another alternative for vpn with an nzb downloader? Edit: I just deleted, reinstalled and reconfigured docker and it's working. No idea what changed.
  2. Damn...was hoping it wasn’t just me. Just curious if yours was working and then stopped suddenly? And in theory, why couldn’t these two containers use different VPN servers?
  3. My nzbgetvpn stopped working with vpn enabled. I’m using PIA and latest docker release. Anyone else experience this and have a solution? DelugeVPN still working correctly as usually if it is a PIA issue they break together.
  4. I remember flashing FW but knock on wood, I think most of my “red ball” issues are related to my backplanes or cables.
  5. I rebuilt parity. Here's the short SMART test report. Do you see anything I should be concerned about? tower-smart-20191017-2122.zip
  6. Thanks for the quick response. Is there not a good preclear tool for the current release? What do you suggest I do to determine the state of the failed drive? Also, can you tell anything from the diagnostics about the significance of the errors?
  7. I had a drive go down last night. Syslog showed some errors. I captured the Diagnostics (attached) but was unable to get the drive to show up after several start/stops of the array. I just went ahead and replaced the drive since I had a spare handy but was hoping to get some feedback on my next steps. The drive is still rebuilding now and I'm currently out of SATA slots in my server. With the higher capacity drive I used, I could copy over data from a smaller drive to the new one as well so I can put the failed drive back in the machine and do SMART tests and run a pre-clear. The issue is I'm not sure of the best process to reduce the array by one drive. I remember a long time ago do this without losing parity but not sure that's still an option in the latest version of UnRAID (6.7.2)? I checked the FAQ but I wasn't sure if it was updated with the most current best practice for doing this? Several of my drives are old so I'm a little concerned about being uprotected while Parity rebuilds. tower-diagnostics-20191015-0231.zip
  8. Did you add this to the latest container or do I need to create the variable first? I don’t see it currently. Thanks.
  9. Ok, thanks. What server did you specify for PIA? I found US-Midwest to be the fastest one for my connection.
  10. Not a lot of activity here but will ask anyway. Is anyone using NZBgetVPN with PIA and getting download speeds above 10MB/sec (assuming you have a faster internet and news host connection) since the change to PIA's port forwarding capabilities? If so, which server are you specifying? I can only get faster speeds now by disabling VPN service. Thanks.
  11. I have the 4096 cert file presumably because strong certs was enabled. I don't remember why I enabled this in the first place so dropping back to the 2048 version shouldn't be an issue? It doesn't look like my strong cert files are being updated when I pull a new version of the docker (i.e. files are from 2017). EDIT: I was able to get this docker working again by doing a clean install and then copying the correct cert files in the openvpn directory.
  12. Thanks, this worked for me as well. I agree it doesn’t make sense that reverting to an older version fixes the problem.
  13. Can you please screenshot your /config/openvpn/ directory? I tried Switzerland as well to no avail.
  14. I tried option 1 but it didn't work for me. I also didn't see a variable for STRICT_PORT_FORWARD in my settings. Is this because I have an outdated template? EDIT: I also noticed more than one file in the /config/openvpn/ directory. Is this an issue? I tried removing the openvpn.ovpn file but no change.
  15. Thanks for the response. I had to do an unclean shutdown. No obvious cable issues. I rebuilt the drive last night and it has been running ok since. I guess I'll just keep an eye on this HBA.
  16. So I tried stopping the array and it seems stuck at unmounting disks. Not really sure what to do at this point?
  17. Hi guys, I haven't been on the forum lately because well, I haven't had any issues with my UnRAID server! Anyway, just got a red ball on my disk 1 and was looking for some help troubleshooting what went wrong and how best to proceed from here? I did look at the smart report for the affected drive (5XW024TM) and didn't see anything alarming but like I said, haven't done this in a while so looking for some expert opinions. I also noticed the sd#'s don't match between the smart report labeling and what I see on my dashboard (e.g. failed drive is sdw in report but sdi on my dashboard) so not sure if that matters? Thanks in advance. tower-diagnostics-20180606-1102.zip EDIT: I just noticed that I have write errors to several disks as well. I think it's related but can't be sure. Please let me know if any additional info is required. The syslog is repeating these errors over and over: Jun 6 10:41:31 Tower kernel: mdcmd (11848): spindown 2 Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower kernel: mdcmd (11849): spindown 4 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower kernel: mdcmd (11850): spindown 5 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower kernel: mdcmd (11851): spindown 9 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: mdcmd (11852): spindown 10 Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower kernel: mdcmd (11853): spindown 12 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower kernel: mdcmd (11854): spindown 14 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write Jun 6 10:41:31 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jun 6 10:41:31 Tower emhttpd: error: mdcmd, 2639: No such file or directory (2): write
  18. Yeah, I got that now. Problem is I didn't know about it beforehand. Would be nice if there was a toggle in the built-in permissions script but I realize it was really meant for one-time use.
  19. So I was having an issue with my Emby app (for AFTV) as well as web playback. I can't be 100% certain but I believe the root cause was the New Permissions utility changing the attributes of two files. I ran the utility on my cache disk because one of my dockers assigned attributes that wouldn't allow me to copy the file from the cache to the server manually from a Windows VM. Basically, I think it removed the executable attribute from ffmpeg and ffprobe (i.e. from -rwxrwxrwx to -rw-rw-rw-). Once I did a chmod 777 ff* to these two files, Emby started working again. What made the matter most confusing is I wasn't having any issue with Kodi playback using the Emby addon. I presume this is because Kodi has its own playback engine and wasn't relying on the ffmpeg install from Emby but I could be wrong.
  20. How exactly do you access this? I have CA installed but the only thing I see for new permissions is in tools-->UnRAID OS-->New Permissions EDIT: Did you mean the "Fix Common Problems" CA Plugin and the Extended Test?
  21. Yeah, I don't disagree. I also need to get my VM configured to shutdown prior to the server shutdown. Thanks again.
  22. Yep...that would be the problem! Nice catch. I can't even venture a guess as to when/how that hapepened! Nevermind the obvious cues from the dashboard (missing load info and 175.5 min of runtime!). Anyway, thanks for endulging my stupidity!
  23. Nice idea...once I get the first apcupsd issue resolved I'll try adding this to the mix!
  24. It's weird because my logs directory on the flash seems to have stopped saving logs to this location around early February. I don't remember configuring a different location for the log files? Is that even possible?
  25. Thanks for the suggestions guys. Hard to imagine the battery doesn't have enough juice for 30 seconds of runtime plus shutdown. One thing I've noticed that appears to prolong shutdown is the stopping of my Win 7 VM. Whenever I manually restart the server for updates, I make it a habit of shutting down the VM from within Windows (i.e. use shutdown command from within Windows). That seems to dramatically improve the total time to stop the array and shutdown the server. In either case though, we're talking about a min or two difference so 1-2 vs. 3-4 min total. I take it there's no way to confirm the server actually saw the loss of power before shutdown then? I was hoping a log file might still be available but I'm guessing this is a limitation of the log file running in RAM when the shutdown occurs? I'll try the procedure outlined above and report back later.