kikkawa

Firstly love the docker for atm8 Thank you! I have one minor issue, even when allocating 8gb ram min and 16gb max, When i try to go into the Nether for the first time the server crashes with the following log Any ideas? crash-2023-03-12_13.34.43-server.txt

I can confirm i found 2 sticks of RAM that would not POST when they were installed solo on the system, these have been replaced and the system has been online for 2.5 days so far with no issues Thank you for you help itimpi!

Memtest does seem very broad and looks at the whole, says yeah everything looks good. Maybe if you ran each stick with memtest on an indivual basis (would take a long time) it *might* show some errors but for the sake of a few power downs and some clicking ram in, its eaiser to swap hardware You've been fantastic thank you!

Hi JorgeB, Thank you for taking a look at the logs for me and confirming my thoughts of cant find anything that indicates the reboot I've had the system running on a single 8GB stick overnight, its finishing a parity check before i play around it more I beleive one of the 8 8Gb sticks could have a fault that wasnt picked up by memtest, as so far it seems to be stable just with high ram usage! Ill add a second stick later on and look at replacing them as well

Hello Unraid Community! My server keeps randomly rebooting at random times, it happened a few weeks back ensured everything was up to date as when it rebooted it kept killing plex config xml which required a rebuild of the docker. Since then it was running 24/7 for around 3 weeks with no issues from what i could tell but it has restarted twice today one at 5am and then again around 11am (08/01/2023) When it happened first time memtest was ran for 8 hours, had no errors Bios is up to date and tried restoring default Tested psu and tried another one still rebooted Tested different ram still reboots Disabled all vms so they are not running, removed dockers that are no longer used and cleaned the app data I've attatched the diagnostics file and syslog, enabled syslog after the first rebooting ocurred but cant see the cause to the reboots Seems silly but i do have a wifi plug to monitor power usage but fail to see how this would cause it to reboot at all Im hopeing the more knowledgable people would be able to point in the direction of the faults tower-diagnostics-20230108-1234.zip syslog-192.168.200.137.log

Thank you for getting back to me, ill uncheck the cores and let unraid do its thing ive allocted 15gb for xms and 25gb for xmx which has helped a little, it is a very big mod pack so i know im asking a lot out of the server and docker its maily in one of the dimensions that things can crash

Im running a modded minecraft server on the docker, only 1 server running and when its just me playing its fine when player 2 joins it gets a little laggy despite being allocated 5gb xms to 15gb xmx ram, pack is ATM 6 so its about 300 mods Is there anything else to up the resources to give a smoother play? Changed the docker to use 8 cores and 8 threads out of the cpus available, would it be worth upping the allocated ram to 20gb+ in mine os server as well?

Thank you! You're an absolute legend changing from bridge to host fixed my adoption issue, it connected up instantly after switching!

Hello, I'm trying to get Filezilla to connect to swag (letsencrypt) they have config files for most apps but not for filezilla, i tried creating my own using the default sample ones but i get 502 bad gateway like its not being pointed in the right direction is there anything im missing at all? I can access it through my ddns web address tho so i know the ftp is working on the correct port ## Version 2021/05/18 # make sure that your dns has a cname set for <container_name> and that your <container_name> container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name filezilla.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app filezilla; set $upstream_port 3000; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } # location ~ (/filezilla)?/api { # include /config/nginx/proxy.conf; # include /config/nginx/resolver.conf; # set $upstream_app filezilla; # set $upstream_port 3000; # set $upstream_proto https; # proxy_pass $upstream_proto://$upstream_app:$upstream_port; # # } }

Adding IOMMU grouping here IOMMU group 0: [1002:5a14] 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host Bridge (rev 02) IOMMU group 1: [1002:5a16] 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) IOMMU group 2: [1002:5a18] 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) IOMMU group 3: [1002:5a1c] 00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 4) IOMMU group 4: [1002:4390] 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40) [3:0:0:0] disk ATA Samsung SSD 840 6B0Q /dev/sdc 256GB [4:0:0:0] disk ATA TOSHIBA MG03ACA3 FL1A /dev/sdd 3.00TB IOMMU group 5: [1002:4397] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [1002:4396] 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2 IOMMU group 6: [1002:4397] 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [1002:4396] 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub IOMMU group 7: [1002:4385] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) IOMMU group 8: [1002:439c] 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) [1:0:1:0] disk ATA ST3500312CS CA12 /dev/sdb 500GB IOMMU group 9: [1002:4383] 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) IOMMU group 10: [1002:439d] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) IOMMU group 11: [1002:4384] 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) IOMMU group 12: [1002:4399] 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub IOMMU group 13: [1002:43a0] 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) IOMMU group 14: [1002:4397] 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma [1002:4396] 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub IOMMU group 15: [1002:9540] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4550] IOMMU group 16: [1106:3483] 02:00.0 USB controller: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller (rev 01) Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 17: [10ec:8168] 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) IOMMU group 18: [10de:1184] 05:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 770] (rev a1) IOMMU group 19: [10de:0e0a] 05:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)

Hello, I had the windows 10 vm working but then had to remove a failing disk, migrated everything over to the other drives using unbalance all went over with no problems. I went to start my windows vm and VNC remote nor remote desktop would work. Tried to reboot same issue. Set the vm up again using VNC which does boot and fully work, but when i add in my GTX 770 to passthrough with the modified bios rom It will start but not web VNC remote or RDP If I change it VNC itll boot and login without issues, i checked the xml and noticed the gpu vbios isnt being shown even after binding those to vfio in system devices Any help is greatly appreciated as after scrolling videos, forum/reddit posts I come up at a blank on a fix VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>3118c475-09f2-7617-2144-4502b26e916e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>5242880</memory> <currentMemory unit='KiB'>5242880</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3118c475-09f2-7617-2144-4502b26e916e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:31:1c:a0'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disk2/isos/Gtx 770.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>

I've got the same issue but can't seem to file the VFIO config to edit the bindings, where is the file located on the usb? Tried it in another pc to find it but havent found any fixes yet