STEFAN1987

Members
  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

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

STEFAN1987's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Seems like the reboot did the trick. but i also lowered the dedicated ZFS ARC allocation from 1/2 to 1/4 of the memory. Thanks @JorgeB for you support it is much appreciated
  2. My ZFS Memory usage keeps being at 100%, can that be a part of the crashes?
  3. I have just rebooted and will let it run and post it if it crashes again
  4. Okay that would be amazing if that was the reason. and if it keeps crashing more memory could be a solution?
  5. I dont think i rebooted, as i recall i just started the docker service again. I actually had the thought that the 32 gb of memory was the issue, but i was only using 75% of the total memory, but always 100% ZFS memory usage. i have allocated 50% of the memory to ZFS ARC
  6. Hi My Server keeps crashing and i have no idea what causes the crash. I have upgraded my hardware from AMD Ryzen 3900X intel 14700K. Since the hardware upgrade i am in the process to convert my filesystem til ZFS from XFS and im using Unbalanced to free the disk before formatting. Can one of you guys take a look at the syslog and point to the direction of what causing the crash. On this crash i was moving 1,2 tb 4K movies from one disk to another. The crash today starts at line 3975. I changed the docker network yesterday from macvlan to ipvlan Thanks in advance SysLog.txt
  7. Mine is also totally dead. i cant connect to the webui after i updated not locally or from https. I dont see anything in the log that seem unusual. I has worked like a charm right before last update
  8. I just found out that br-fb663562c2d5 is the gateway to my proxynet made from the guide Spaceinvader made years ago.
  9. Hi Im starting to have issues with the network inside unraid. I keeps falling out so i cannot connect to the servers main page and my dockers web iu, but my VM still have network connection. ive been trying to find out what the problem is but with no luck other than something inside unraid is disabling the eth0 Hope someone can help me figure out what to do. Im running 6.11.0-rc4 This is whats in the log when i happens Aug 28 16:10:01 ServerJohn kernel: vethe9a3b3e: renamed from eth0 Aug 28 16:10:01 ServerJohn kernel: br-fb663562c2d5: port 3(vethf4e0609) entered disabled state Aug 28 16:10:01 ServerJohn avahi-daemon[14901]: Interface vethf4e0609.IPv6 no longer relevant for mDNS. Aug 28 16:10:01 ServerJohn avahi-daemon[14901]: Leaving mDNS multicast group on interface vethf4e0609.IPv6 with address fe80::d82c:6eff:fe47:bda1. Aug 28 16:10:01 ServerJohn kernel: br-fb663562c2d5: port 3(vethf4e0609) entered disabled state Aug 28 16:10:01 ServerJohn kernel: device vethf4e0609 left promiscuous mode Aug 28 16:10:01 ServerJohn kernel: br-fb663562c2d5: port 3(vethf4e0609) entered disabled state Aug 28 16:10:01 ServerJohn avahi-daemon[14901]: Withdrawing address record for fe80::d82c:6eff:fe47:bda1 on vethf4e0609. Aug 28 16:15:01 ServerJohn percent_mover.sh[18455]: Cache is 58% full, which is less than the set point of 80%. Not running
  10. Hi i have problems with syncing my IOS movies when they are over a certain size. Nextcloud is connected through a reversed proxy. and i get 413 file are to large error in the app. what can i do to get it to work? EDIT: I found out that it was my Cloudflare proxy that made the problem, what can i do so i can proxy behind cloudflare and still be able to upload huge filed from ios?
  11. How do i get the extractor plugin to extract inside the folder where the rar files are?
  12. I just updated my bios on my ASUS ROG STRIX X570-F GAMING to 3405 and now i cannot passthrough my GFX. when i start my VM im getting this Any solution to get my VM working again? ErrorWarningSystemArrayLogin 2021-03-12T09:41:40.828988Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddaa, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.828997Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddab, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829005Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddac, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829014Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddad, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829030Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddae, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829041Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddaf, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829051Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb0, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829062Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb1, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829071Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb2, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829081Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb3, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829096Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb4, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829107Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb5, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829128Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb6, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829143Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb7, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829153Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb8, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829162Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddb9, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829171Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddba, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829180Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddbb, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829197Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddbc, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829208Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddbd, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829219Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddbe, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829228Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddbf, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829237Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc0, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829246Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc1, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829255Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc2, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829264Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc3, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829273Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc4, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829281Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc5, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829290Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc6, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829299Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc7, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829307Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc8, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829316Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddc9, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829325Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddca, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829333Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddcb, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829342Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddcc, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829351Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddcd, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829359Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddce, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829368Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddcf, 0x0,1) failed: Device or resource busy 2021-03-12T09:41:40.829377Z qemu-system-x86_64: vfio_region_write(0000:0a:00.0:region1+0xaddd0, 0x0,1) failed: Device or resource busy
  13. Hi im from of today getting this error message in all my both rTorrentVPN and DelugeVPN 2021-02-13 11:23:33,210 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken' [info] 12 retries left [info] Retrying in 10 secs... 2021-02-13 11:23:43,460 DEBG 'start-script' stdout output: parse error: Invalid numeric literal at line 1, column 7 Anyone know how to fix this?