je82

Members
  • Posts

    402
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

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

je82's Achievements

Enthusiast

Enthusiast (6/14)

31

Reputation

5

Community Answers

  1. Think i answered my own question, i just expected it to be faster, my cpu literally sleeps while writing at 110mb/s to the xfs encrypted cache volume so to me it seems like there is a hardcoded limitation either inside the xfs encrypted protocol or inside unraid for whatever reason.
  2. Interesting read here: Is unraid just that slow with xfs encrypted? It seems like a crazy performance hit, i have been running my array encrypted for years but i never write directly to the array (the mover does that at night) so the 110mb/s limiter that may be in place somewhere isn't a big problem there, but its definitely a huge issue if on the cache. Is there a limit hardcoded into unraid how fast it can write to a xfs encrypted volume?
  3. I have a very strange issue with my unraid installation. I previously ran 2x 1tb ssd in a btrfs raid partition as a cache for 3 years and never had any speed problems but i wanted to have the volume encrypted and also save 1x ssd so i changed this pool to a single 1tb ssd with xfs encrypted instead. Everything works fine, here is the hickup. Network speed from outside rack to clients = 2500mbit Network speed from inside rack between servers = 10000mbit Next test, setting up a virtual machine inside unraid with a smb share on the same nic/network and try the speeds: Third and final test is to send a file from another server inside the rack that has a 10gbit connection directly to the unraid cache. As you can see clearly in the last test, something is very off, even on 10gbit connectivity i am getting 110mb/s when sending to the cache, but receiving i am getting 10gbit speeds. The issue started the same day i removed my btrfs cache raid partition and changed it into a xfs encrypted. I have already swapped the SSD to a brand new one because i intially though this issue must have been due to 3 years of wear and then xfs encryption on top of that was causing weird slowdowns, brand new ssd, exact same issue.
  4. just to be clear, this was the command that worked to silence these messages in the syslog.
  5. Sorry for opening this thread again, but i have a similar issue but my disks spins down and i don't want it to, i installed unassigned devices and set the disk to "pass through" but i still cannot control the spin up/down from the settings page of the disk where as other disks that are in my array i have the option, see screenshots below: Passed through disk: disk in unraid array:
  6. Hi, New to wireguard and love how easy it was to setup, i am sure everyone will be using it soon. The problem i see is the fact that anyone with a few seconds of time with access to your client machine could potentially steal the peer info and then use it to access your local network, therefor some added enhanced feature set would be nice if possiible. 1. A way to enable/disable peers easily in the gui, and on top of that it would be really cool to be able to schedule when the peer is allowed access, so lets say i have a work schedule, i can easily setup so that my work peer is allowed to access the tunnel on the same hours that i work preventing the tunnel to be used on off hours. 2. A way to get an notification and a little information about connecting client when someone connects to wireguard, i am not sure how much information is exposed to unraid but it would be really nice to be able to setup some kind of notification when a connection has been made which makes it a lot easier to notice if someone that should't have access is having access.
  7. nevermind i see now that i somehow glossed over this, it was mentioned in there, all is good. edit: a good thing to add for future unraid releases is the notice that you have to enable this option "Host access to custom networks: Enabled" under the advance docker setting in order for it to work, right now it only says you have to make a static route in your router and nothing more. otherwise big props to the developers, wireguard was very simple to setup and works liek a breeze!
  8. Hi, i am trying to setup wireguard for my local network and i want the route to have access to the docker containers as well as the rest of the network, all seems to work except the docker containers. I have setup a route a static route in my router to route traffic from the wireguard network to the unraid lan ip as instructed, but no luck. My question is, do i have to enable "Host access to custom networks: Enabled?" under the docker settings tab? I couldn't see this option mentioned anywhere in the guide on how to reach docker so i expected it not to be a thing but found it when i was looking around, should i enable this or am i doing something else wrong? I'm using br0 for all my docker containers with each of them having their own ip on my lan.
  9. Thanks, looks like its gone! root@NAS:~# ls /boot/config/plugins/nvidia-driver/packages/ 5.15.46/ root@NAS:~#
  10. root@NAS:~# ls /boot/config/plugins/nvidia-driver/packages/ 5.10.28/ 5.15.46/ root@NAS:~#
  11. Thanks for the quick reply, here's the diag file, cheers! nas-diagnostics-20220922-0905.zip
  12. I have this error message everytime i boot my unraid server, how can i fix it? (I have no issues whatsoever with the nvidia driver, probably some part of an old uninstall that didnt work?)
  13. had to "umount -l /dev/loop2" to get the array shut down... not sure what happened here, maybe it has nothing to do with the Appdata cache name and maybe more to do with me having some dockers on auto run and shutting down the array before all the autoruns have been processed making the docker process lock up?
  14. nvm it looks like the shares are displaying these linux core files, not just the new cache pool, but when i look in /mnt/ its only cache that is mounted. the array cannot be stopped though, trying to avoid a parity check here, how can i shut down the array? it just keeps saying cache is busy
  15. Pretty much think i broke my unraid, named my Appdata new cache pool to Appdata and set folder Appdata to "Prefer" on cache pool appdata, now it looks like i cannot shutdown the array, when i click whats on the new cache disk it looks like core unraid linux files are being written to the root of the disk. What do i do?