Metti

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

Metti's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Metti started following [6.12.4] Can't upgrade to Unraid 6.12.5 and higher
  2. Metti
    Problem Description: I am trying to upgrade my Unraid system from version 6.12.4 to 6.12.5 or a later version, but I encounter a problem that blocks the boot process. Regardless of whether I attempt the upgrade directly through the operating system or by flashing the USB dongle with the new version, the system gets stuck at the same point during boot. Reverting back to version 6.12.4 immediately resolves the issue, suggesting that the problem is specific to the newer versions. Steps to Reproduce: 1. Attempt to upgrade the system via the operating system to Unraid 6.12.5 -> System hangs during boot. 2. Flashing the USB dongle with Unraid 6.12.5 (and later versions) and booting the system -> System remains stuck at the same point. 3. Tried several USB dongles, with the same result. 4. Returning to Unraid 6.12.4 results in the system booting without issues. Expected Behavior: The system should successfully boot and function after upgrading to Unraid 6.12.5 or a later version. Actual Behavior: The system gets stuck at a specific point during boot when upgraded to Unraid 6.12.5 or a later version. A screenshot of the terminal output at the point where the system hangs is attached. Also attached is a screenshot showing that the system successfully gets past this point at version 6.12.4. Attached Files: - Screenshot of the terminal output when the system hangs andgpu 0000:0a:00.0: amdgpu: GART: 256M 0x000000F00000000 - 0x000000FFOFFFFFFF Carm] Detected VRAM RAM=8192M, BAR=256M [drm] RAM width 256bits GDDR5 [drm] andgpu: 8192M of VRAM memory ready [drm ] andgpu: 32115M of GTT memory ready. Ldrm] GART: num cpu pages 65536, num gpu pages 65536 [drm] PCIE GART of 256M enabled (table at 0x000000F400800000). Idrm] Chained IB support enabledt andgpu: hungr sw_init smu backed is polaris10_smu [drm] Found UVD firmuare Version: 1.130 Family ID: 16 [arm] Found UCE firmuare Version: 53.26 Binary ID: 3 [drm] Display Core initialized with u3.2.2071 Larm too and tob enc initialized successfully. 275: Loaded module U2.1.14-1, 2PS pool version 5000, 2FS filesystem version 5 [drm] VCE initialized successfully. kfd kfd: andgpu: Allocated 3969056 bytes on gart andgpu: sama_bitnap: f andgpu: SRAT table not found andgpu: Virtual CRAT table created for GPU andypu: Topology: Add AGPU node [0x67df:0x1002] kfd kfd: andgpu: added device 1002:67df andgpu 0000:0:00.0: andgpu: SE 4, SH per SE 1, CU per SH 9, active cu number 36 andypu 0000:0a:00.0: andgpu: Using BACO for runtime Carm] Initialized andgpu 3.49.0 20150101 for 0000:0a:00.0 on minor 0 fbcon: andgpudrfb (fbO) is primary device Console: switching to colour frame buffer device 240x67 andypu 0000:0a:00.0: [drm] fbO: andgpudrmfb frame buffer device Mounting non-root local filesystems: / deu/shn : already mounted huget Ibfs : successfully mounted Setting the system clock rate: /sbin/ad jtimex -tick 10000 --frequency 0 Setting systen time fron the harduare clock (UTC): Tue Feb 13 21:11:04 CET 2024 Configuring kernel parameters: /sbin/sysctl -e --system * Applying /usr/lib/sysctl.d/60-libuirtd.conf ... ts.aio max-mr = 1048576 * Applying /usr/lib/sysctl.d/60-gemu-postcopy-migration.conf ... *Applying /etc/sysctl.conf .. • Is.inotify.max_user watches = 524288 net.core.rmem_max = 16777216 net core.umem_max = 16777216 net, iput.top_rmem = 4096 87380 16777216 net, pus, tcp-smem = 4096 65536 16777216 net, iput, ip forward = 1 Using boot/config/random-seed to initialize /dev/urandom. INIT: Entering rulevel: 3 Going multiuser,.. Updating shared Library links: /sbin/Idconfig & Starting rsysloga daemon: ust/sbin/rsyslogd -1 /var/run/rsyslogd.pid Updating X font indexes; /usy/bin/fc-cache -f& Updating hardware database index: sbin/udevadm hudb --update Triggering udeu events: /sbin/udevadm trigger -action=change - Screenshot of successful passage at version 6.12.4 คห Fo แบ้า (ruare Uers ton: 1.700 Fantly D: 16 Carm] Found VCE firmuare Version: 53.26 Binary ID: 3 Carm] Display Core initialized with 03.2.1871 [drm] UVD and UVD ENC initialized successfully. kha do it ia sued full bytes on gart andgpu: sana_bitmap: f andgpu: SRAT table not found andgpu: Virtual CRAT table created for GPU andgpu: Topology: Add AGPU node COx67df:0x10021 kfd kfd: andgpu: added deuice 1002:674F andgpu 0000:0a:00,0: andgpu: S6 4, SH per SE 1, CU per SH 9, active_ou number 36 andgpu 0000:0a:00.0: andgpu: Using BACO for runtime pm Carmi Initialized andgpu 3.47.0 20150101 for 0000:0a:00.0 on minor o fbcon: andgpudrfb (FbO) is primary device Console: switching to colour frame buffer device 240x67 andgpu 0000:0a:00.0: [drm] fbo: andgpudrmfb frame buffer device Setting the system clock rate: /sbin/adjtimex -tick 10000 -frequency o Setting time from the harduare clock (UTC): Bluetooth: hcio: Waiting for firmare download t Bluetooth: hcio: Firmware loaded in 1348768 usecs Bluetooth: hcio: Waiting for device to boot Bluetooth: hci®: Device booted in 15627 usecs Bluetooth: hciO: Found Intel DDC parameters: intel/ibt-20-1-3.dde Bluetooth: hci®: Applying Intel DDC parameters completed Bluetooth: hci0: Firmuare revision 0.3 build 20 week 28 2022 Tue Feb 13 21:51:43 UTC 2024 Configuring kernel parameters: /sbin/sysctl -e --system fs.aio-max-ar = 1048576 = Applying /usr/lib/sysctl.d/60-gemu-postcopy-migration.conf ... * Applying /etc/sysctl.conf fs. inotify.max_user_watches net.core.rmem max = 16777216 net.core.unem_max = 16777216 net.ipu4.tcp_rmem = 4096 87380 net.iput.tcp_umem = 4096 65536 16777216 net.iput.ip_forward = 1 INIT: Entering runlevel: 3 Going multiuser... Updating shared links: /sbin/ldconfig & Starting rsyslogd daemon: /usr/sbin/rsyslogd -i /var/run/rsyslogd.pid Updating harduare database index: /sbin/udevadm hudb --update Triggering udev events: /sbin/udevadm trigger --action-change Starting system message bus: /usr/bin/bus-uuidgen -ensure : /usr/bin/dbus-daemon -susten Starting elogind: /1ib64/elogind/elogind --daemon Starting Internet super-server daemon: /usr/sbin/inetd Starting OpenSSH SSH daemon: /usr/sbin/sshd ssh-keygen: generating new host keys: RSA ECDSA Starting NIP daemon: /usr/sbin/ntpd -g -u ntpintp Starting ACPI daemon: /usr/sbin/acpid Enabled CPU frequency scaling governor: ondemand Compiling Settings XML schema files: usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas & Starting crond; /usr/sbin/crond Starting atd; /usr/sbin/atd -b 15 -1 1 Starting Samba: /usr/sbin/smid -) /usr/sbin/nmbd -D /usr/sbin/usdd2 -d /usr/sbin/winbindd -D unRAID Server 08 version: 6.11,5 IPu address: 192.168.0.9 IPu6 address: not set Tower login: System Configuration: Model:Custom M/B:ASUSTeK COMPUTER INC. ROG STRIX X570-E GAMING Version Rev X.0x s/n 190958139400757 BIOS:American Megatrends Inc. Version 4021 Dated 08/09/2021 CPU:AMD Ryzen 9 3900X 12-Core @ 3800 MHz HVM:Enabled IOMMU:Enabled Cache:L1 - Cache: 768 KiB, L2 - Cache: 6 MiB, L3 - Cache: 64 MiB Memory:64 GiB DDR4 (max. installable capacity 128 GiB) Network:bond0: fault-tolerance (active-backup), mtu 9000 Kernel:Linux 6.1.49-Unraid x86_64 OpenSSL:1.1.1v Attempted Solutions: - Tried several USB dongles - Returned to version 6.12.4, where the system works Further Information: tower-diagnostics-20240214-1517.zip
  3. Metti
  4. Metti
    Have you made any progress? I have a similar problem in that my Windows VM crashes as soon as I play a game for longer than 10 minutes. All cores assigned to the VM immediately jump to 100%. What is always visible in the Unraid Console with "Top" is qemu-system-x86.
  5. Metti started following How can I prevent my CPU usage from always peaking?
  6. Metti
    On my Unraid, there is always high utilisation as far as CPU usage is concerned. Not always immediately, but at regular intervals, around 10 minutes, as soon as I play a game like SAtisfactory on my Windows 11 WM. Parallel to the game client, a Satifactory server runs in a Docker container.
  7. Metti
    Yes, i pasted that code, that i read before from you. <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> i also renamed the SMB Share, so the Driveletter Z:, is free. The main problem seems, that i don't get the "Mass Storage Controller", in devicemanager.
  8. Metti
    Ich habe versucht die Anleitung von https://virtio-fs.gitlab.io/howto-windows.html zu folgen, jedoch wird mir der "Mass Storage Controller" im Geräte-Manager nicht angezeigt. Ist es korrekt, dass ich den Installer für https://winfsp.dev/rel/ , ganz einfacht mit der Standardkonfiguration folge? Wo finde ich ausserdem diese "virtiofs PCI device driver" ?
  9. Metti started following Slow SMB access times, general io vs SFTP
  10. Metti
    is there an update to this issue?
  11. Metti
    The error with "Validate Installation:" I used to make, that is long gone. The share with Appdata was set to "Yes", it is now set to "prefer". What is causing the problem in this case?
  12. Metti
    Hello all I have the problem that my server resets itself towards the evening. That is, after the last player has left the server, the server is not turned off or otherwise. It runs through the night, and when you join the server again the next evening, it is like resette. A new world is loaded and also the serverconfig was reset to default. When I look at the log file, it starts at the "new" day and I don't see anything from the night before. Strangely, however, the gamesave is present, as well as the map that I custom reingeladen. I write the serverconfige with the app (container) filebrowser. Attached you will find the log file from the day after the reset, as well as my config. Translated with www.DeepL.com/Translator (free version) output_log.txt serverconfig.xml
  13. Metti started following Case icon requests
  14. Metti
    Intertech Inter-Tech 4U 40255 Please https://www.inter-tech.de/products/ipc/server-cases/4u-40255
  15. Metti
    Metti changed their profile photo
  16. Metti
    Metti joined the community
  17. Metti
    I'm getting the error when attempting to start a VM I just made. I'm trying to pass through my Nvidia Quadro K4000 but I hit this error. 2020-10-03T10:08:43.348511Z qemu-system-x86_64: -device vfio-pci,host=0000:0f:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x5,romfile=/mnt/disk1/Quan/Bios ROM/Quadro K4000/169262.rom: vfio 0000:0f:00.0: failed to setup container for group 14: Failed to set iommu for container: Operation not permitted 2020-10-03 10:08:43.570+0000: shutting down, reason=failed Here is the xml of the VM: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>362096c1-4b6c-74c8-90af-8d725fa7aa90</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>20971520</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/362096c1-4b6c-74c8-90af-8d725fa7aa90_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='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> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.189.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 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:56:5b:9b'/> <source bridge='virbr0'/> <model type='virtio'/> <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='2'/> </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='0x0f' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/Quan/Bios ROM/Quadro K4000/169262.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0f' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> I'm going to keep working to try and find a workaround. Please let me know if there's an easy way around this so I can keep my sanity for another day.