lviperz

Members
  • Posts

    26
  • Joined

  • Last visited

Recent Profile Visitors

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

lviperz's Achievements

Noob

Noob (1/14)

1

Reputation

  1. My apologies. I totally missed that in the faq. I added my unraid vpn subnet to the LAN_NETWORK in settings and all is good now. Thank you for pointing me. Also thank you for all your time. It is much appreciated.
  2. I just switched from using openvpn to wireguard. That is working fine. Problem is I can't access the sabnzbdvpn webgui remotely when I'm connected to my unraid vpn that also uses wireguard. I am able to access the sabnzbdvpn webgui from my local network. I assume it's a route issue but I'm not sure what. My unraid vpn peer is set to remote access to lan. Is there a subnet from the container I need to add to the allowed range in the unraid vpn settings?
  3. Thanks for this plugin. I just discovered it and you made setting up an openvpn server as easy as pivpn. I do have wireguard installed and setup but I need to run my vpn server on TCP. My ISP is doing something on UDP that causes my vpn connection to run extremely slow. I found running my vpn server on tcp got me 5 times the speed. So until either I figure out the problem with my isp or wireguard allows tcp, I'll use this plugin. This plugin also frees up my rpi for other things and keeps servers consolidated to unraid. Thanks again.
  4. Daughter is home today so I had her reboot my server. Aside from the forced parity check, everything came back up normal, including docker, all it's containers and the cache doesn't show any errors. Is there anything I should look at or maybe rebuild the cache anyway? Parity check will take about 14 hours. Should I just let things run their course and see if I get a file system corruption again?
  5. BTW, figured I would ask. How do I figure out what may have caused the file corruption on the cache drive? I would like to avoid it from happening again if possible.
  6. Well, the backup finished so I attempted to stop the array but it got stuck in a loop trying to unmount the disk shares. Gave it about 20 minutes then opened a terminal and ran "fuser -km /mnt/user" but that didn't help. I remembered I was sshed in to the cache so I ran "fuser -km /mnt/cache" but that didn't help. When to run it for disk1 but accidently hit enter after "fuser -km /mnt/" and my terminal connection dropped and the webgui is unavailable. Guess I'll have to wait till I get home tonight and do a hard reboot.
  7. Ok, thanks. I couldn't run krusader so I'm manually copying the cache drive to a local computer now. I also have an auto backup from yesterday as well. I'll wait for the backup to finish, hopefully before anything happens, and then follow the instructions you provided.
  8. Is it safe to backup what is currently there since the filesystem is corrupt?
  9. This morning I have 2 errors from Fix Common Problems and I'm not sure what I need to do. Thought I would ask before I jump and assume. Error 1: Unable to write to cache - Drive mounted read-only or completely full. Begin Investigation Here: Unraid Main Error 2: Unable to write to Docker ImageDocker - Image either full or corrupted. Investigate Here: Docker Settings Here is the disk log from the cache. Mar 16 00:00:40 UnNAS kernel: BTRFS error (device sdd1): unable to find ref byte nr 128548089856 parent 0 root 5 owner 265457 offset 85291008 Mar 16 00:00:40 UnNAS kernel: BTRFS: error (device sdd1) in __btrfs_free_extent:6802: errno=-2 No such entry Mar 16 00:00:40 UnNAS kernel: BTRFS info (device sdd1): forced readonly Mar 16 00:00:40 UnNAS kernel: BTRFS: error (device sdd1) in btrfs_run_delayed_refs:2935: errno=-2 No such entry Mar 16 00:00:40 UnNAS kernel: BTRFS error (device sdd1): pending csums is 66195456 I assume this is the cause of the unwriteable docker but I'm unsure of how to fix it. I'm still only a month green at this. I've attached my log file as well. Thanks. unnas-diagnostics-20200316-0740.zip
  10. I got it. Was looking on github issues and noticed that my config.json still had the old token. I'm in now.
  11. I setup bitwarden yesterday and it's working fine. Today I'm trying to get back in to the admin to change the url since I just setup a reverse proxy but I keep getting invalid admin token. So I changed the token and clicked apply but I'm still getting invalid admin token. I did notice the container auto updated last night also. Not sure how to proceed.
  12. Ok, solved. I found my answer over in the unassigned devices support forum. I can't have pass through turned on with auto mount. I misunderstood the switches use.