Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Gragorg

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thinking of giving wireguard on PIA a shot to compare the transfer rates. I have a question about the first step: 1. Change Docker parameter from --cap-add=NET_ADMIN to --privileged=true (WireGuard requires privileged permissions). I assume the "--privileged=true" gets added to the extra parameters line in the docker setup? I don't see the line "--cap-add=NET_ADMIN" in there at all. What am I missing?
  2. Is there a benefit to using wireguard instead of the regular PIA VPN?
  3. So I updated the docker to the latest to do the log and for some reason it works fine now. I upgraded and reverted twice a few days ago and it wouldn't take. Not sure what changed but it works with no issues now. Thanks for all your great work!
  4. Have you managed to fix your issue? I rolled the docker back one version and works again for me.
  5. I’m currently using PIA. For whatever it seems like it wasn’t connecting to PIA and would not launch into the web GUI. All plugins that use privoxy thru the docker were reporting connection problems. I am currently running unraid. I will have to do the log file tomorrow as I am currently not home.
  6. Did you install 2.0.4.dev38_g23a48dd01-2-12 version of the docker when it broke? I just rolled back to 2.0.4.dev38_g23a48dd01-2-11 and all is well now.
  7. Last night I updated to 2.0.4.dev38_g23a48dd01-2-12. This seems version does not work for me. I thought maybe it needed the next gen OVPN file but it still would not work. Rolled back to 2.0.4.dev38_g23a48dd01-2-11 and all is working fine now. Is this an issue with the update or am I missing something?
  8. Here is the information to shrinking the array. Add the 14tb as a new drive with XFS and then follow the shrink array procedure to remove the 1 TB.
  9. Configuration can be stored on your single array drive. Most people store their dockers (apps) and VMs on a cache drive or an unassigned device out of the array for better performance. For the time being it will work on your single drive but will prevent that drive from spinning down. You can have it all move to your cache if you get one down the road.
  10. Just an uncommon term for rebuilding. Goes back to Antique mirrors as they go "tarnished" or damaged you could restore them by re-silvering them.
  11. Disk 4 has read and write errors which could be caused by a bad cable. I would check and replace the sata cable if need be and then run an extended SMART. If they errors persist after that I would change the drive.
  12. I assume unraid is working? Dockers can be reinstalled using previous apps in the app store. This should set them up how they were before. However stuff like your plex database would have to be remade unless you have a backup.
  13. You have to setup something to grab the syslog files. I used kiwi syslog server installed as a service on my pc to gather syslog information. Mirror syslog to flash I don't use and by default I believe is should be set to no to prevent excessive wear and tear on your flash drive.
  14. All media should be in the array not be on your cache drive. Use cache should be set to "yes" for your media. This allows you to copy your movie, series etc over to the cache drive without slowing down for parity. When "mover" is run it will copy the media into the array at a later time. Split level of your shares may be what is preventing the data from pushing over into the array.
  15. Once you reboot your diagnostics and syslog are reset. You should setup remote "syslog server" under Settings so that you can save the syslog on another computer on your network.