Kulisch

Reserved post for possible upcoming informations.

Hello everyone, despite the expensive prices from nvidia I decided to upgrade to a new gpu to open up more possibilities with AI. I have therefore decided to say goodbye to my 1070 from Zotac and bought a ASUS TUF 4070 TI Super OC from Asus. No other gpus are installed or iGPUs that I can use. (Ryzen 3800XT) So that I could use Docker containers with my new GPU, I wanted to install the latest nvidia drivers. For some reason, however, there were problems downloading them and it kept giving me errors, despite rebooting the host system. So I removed the nvidia plugin, reinstalled it again, restarted unraid and successfully downloaded the latest drivers. Then I rebooted the system again and the Docker containers were able to work with the graphics card (if Docker Settings are correctly configured). I also had difficulties with the VMs at the beginning. In my setup where the 1070 was active I needed two things. Once a vbios file which I got from the TechPowerUp website and a user script that was executed when the array was started. #!/bin/bash echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind my vbios file: Zotac.GTX1070.8192.161103.rom Both are apparently no longer necessary. The vbios file is no longer needed in the 4000 series, as I have read several times, because nvidia has apparently made some changes to make it easier for the user. If I understand correctly, the script has disconnected the GPU from the host system to make it "available" for the VMs. This was necessary with the 1070 so that I could use it there. Even if both are no longer necessary, I still had a black screen when booting up. While browsing the forum I read that it is also possible to use the VNC interface as a graphics card in addition to the nvidia card. Do not forget to configure the corresponding sound card from the nvidia graphics card. I therefore created a Windows 10 VM and carried out the installation via the web interface. I also installed the virtio drivers for the network interface (NetKVM) and the storage (viostor) from the virtio ISO. And here the storage drivers: After installing the OS, I created the offline account and finished the setup. Then downloaded and installed the latest nvidia drivers. Normally it is possible to get graphics card drivers from Windows Updates but in my case none were offered for download. The physical display output appeared after the installation process. Just to make sure that this is not only temporary, I restarted the system via the OS. Then shut it down and booted it up again... and it stayed that way. However, I noticed that the BIOS is only visible in the VNC. On the physical screen, the display output only appears when the OS and the corresponding graphics drivers are loaded. After making sure that this works for the most part, I removed the VNC graphics card. The nvidia card remains in the configuration. Started again and after a few seconds the Windows desktop appeared in the physical monitor when the OS is fully booted. How exactly I solve the problem to get a permanent display output to see the BIOS or when updates are running or a hard disk check is performed,.. I can not say at the moment. If anyone has similar experiences or even a solution to this problem, I would be very grateful if you could let me know. I hope I could help some of you with this information.

If I understand correctly... you want to use this Docker to pull/synchronize mails from a 365 mailserver and store them on the Docker mailserver? What speaks against using a mail client? (Thunderbird, Outlook, Roundcube, etc.)

I cannot recommend an admin web interface. I only use the "setup" command in the container directly (in the console or terminal). docker exec -it docker-mailserver bash To be honest, I'm also not sure if there is one that you can work with properly as they advertise that you can only customize everything via configurations. https://github.com/docker-mailserver/docker-mailserver/issues/1555#issue-650874945 with the "setup" command you can configure everything you need. I can recommend Roundcube as a web client. I downloaded it directly and configured it via the Docker Hub. See configuration in the picture. I hope the information was valuable.

What are you using for Login? Username, Password (special Characters?), Mail Adress, Domain, SSL/TLS, Port? (please censor sensitive data) Is the information you entered in iOS the same as in Outlook? Did you tried Thunderbird?

I'm just here to say thank you. Just found this a few days ago and installed it successfully. Everything works great and I'm using this daily. 👍

I guess this is a read/write problem. Have you changed the permissions? If you are not sure, try a new container or a new path to see if the error happens again. If so, try the following command (not for production environments) chmod 777 /mnt/user/appdata/<dms path>

Hallo zusammen, ich nutze seit einiger Zeit Linux VMs und als GPU meine GTX 1070. An sich gibt es kaum Probleme bei der Nutzung der VM mit GPU, abgesehen davon das ich nachdem die VM heruntergefahren ist, immer noch der letzte Frame zu sehen ist und mein Display das die ganze Zeit anzeigt. Bei Windows VMs passiert das nicht. Wenn ich die VM ausschalte zeigt der kein Bild mehr an und das Display geht in standby. Hat jemand das Problem auch schon gehabt oder weiß wie man das lösen kann? Muss die Lösung in der VM stattfinden oder in Unraid? Zusätzliche Infos: Der Rechner ist ein Ryzen 3800XT Build und nur eine GTX 1070. (Keine zweite Grafikkarte) In der VM nutze ich die proprietären Treiber von nvidia. Die Grafikkarte wird nicht über vfio-bind durchgereicht. Es laufen 2 User Skripte auf dem Unraid die mit der Grafikkarte zu tun haben. 1. Script: GPU Unbind - At first Array Start #!/bin/bash echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind 2. Script: GPU Powersave - hourly - (Von Spaceinvader One) #!/bin/bash # check for driver command -v nvidia-smi &> /dev/null || { echo >&2 "nvidia driver is not installed you will need to install this from community applications ... exiting."; exit 1; } echo "Nvidia drivers are installed" echo echo "I can see these Nvidia gpus in your server" echo nvidia-smi --list-gpus echo echo "-------------------------------------------------------------" # set persistence mode for gpus ( When persistence mode is enabled the NVIDIA driver remains loaded even when no active processes, # stops modules being unloaded therefore stops settings changing when modules are reloaded nvidia-smi --persistence-mode=1 #query power state gpu_pstate=$(nvidia-smi --query-gpu="pstate" --format=csv,noheader); #query running processes by pid using gpu gpupid=$(nvidia-smi --query-compute-apps="pid" --format=csv,noheader); #check if pstate is zero and no processes are running by checking if any pid is in string if [ "$gpu_pstate" == "P0" ] && [ -z "$gpupid" ]; then echo "No pid in string so no processes are running" fuser -kv /dev/nvidia* echo "Power state is" echo "$gpu_pstate" # show what power state is else echo "Power state is" echo "$gpu_pstate" # show what power state is fi echo echo "-------------------------------------------------------------" echo echo "Power draw is now" # Check current power draw of GPU nvidia-smi --query-gpu=power.draw --format=csv exit Vielen Dank im voraus.

Hello everybody, now that I have built myself a pikvm to remotely control the system completely, I could also find a solution to my problem. I have tested some settings in these months and noted for me where there was a problem and where not. After I have now found my optimal settings and tested for weeks with success, I can now close the topic. Power Supply Idle = Typical Current Idle PSS Support = deactivated Global C-States = deactivated Core Performance Boost (CPB) = deactivated I used these settings before and after a BIOS upgrade without crashes. In the meantime I also changed the USB stick (fresh install) and formatted the hard disks. Therefore I strongly assume that it is not a setting on the operating system but only the BIOS. P2.20 -> P2.30 (B550 Taichi) The only thing that doesn't work and won't is hibernating a VM. With Global C-States enabled (if I remember correctly) I could wake up VMs from hibernation. Since I had stability issues with that option as well, I had to disable that and when the VM is in hibernation I can't wake it up and have to do "force shutdown". Therefore set in the operating system that hibernation is disabled. I hope this info is helpful for one or the other. I am so relieved to have solved the problem now.

Making similar experiences. My scanner is not supported out of the box, but after driver installation scanimage -L works as well. Unfortunately the scanner is not found in the web interface either. Is there anything that needs to be adjusted in the Docker variables? # Installation Epson Drivers inside Docker (temporarily) docker exec -it scanservjs bash cp /app/config/iscan-gt-f720-bundle-2.30.4.x64.deb.tar.gz /tmp/ cd /tmp/ tar -xvf iscan-gt-f720-bundle-2.30.4.x64.deb.tar.gz cd /app/config/iscan-gt-f720-bundle-2.30.4.x64.deb/ ./install.sh ... scanimage -L Created directory: /var/lib/snmp/cert_indexes device `epkowa:interpreter:001:009' is a Epson Perfection V30 flatbed scanner

Ok I will try that and give feedback if everything works. Thank you

So if I understand that correctly... Should I ignore the path /mnt/user/ everywhere and instead using /mnt/cache or /mnt/diskX ?

What about the docker containers /mnt/user/appdata/? Should I rsync the files in another place?

unraid-diagnostics-20220919-1331.zip Like mentioned before,... The VM or Unraid crashed if I use /mnt/user/domains If I use /mnt/cache/domains everything works like a charm. I guess the same problem appears if im using docker containers. Using, docker-mailserver, postgres, nextcloud is no problem... using Swag gives me a crash after an amount of time... So im guessing there are problem in /mnt/user/ directory. How can I fix this? Update: Testdisk and Photorec works. Thx for the advise.

After creating a Windows 11 VM and attaching the corrupted Harddrive it detected, the Problem was found during boot by the OS and repaired it. Now I only have to get the persmissions for my Harddrive. I only can list the files in powershell as a administrator. Explorer says the permissions are missing. Using explorer as admin doesnt change anything. Still, I have to repair the array. Is there something that I can use in Unraid to fix this problem. Setting permissions or moving the files? Or do I have delete everything and building up the array from beginning?

I suspect that the problem is with the array itself. The system does not freeze when docker is completely off. The system freezes depending on which container is on. Using the VM under /mnt/user/domains/ causes problems, freezes the VM or Unraid itself. Under /mnt/cache/domains/ I have not noticed any of the mentioned problems. I have performed a RAM check again which was successful. Also a Read-Check. I also checked the S.M.A.R.T. values and everything looks fine there. Do I have to rsync all the data and move it back or is there an easy way to solve the problem? 1 hard disk for cache (pool) and one disk 1 (array). And one of my windows disks the partition layout is broken. It is only recognized as RAW. Does anyone know how I can fix this?

Everytime I use the VM for an hour, happens a kernel panic in unraid. So there is no chance to check anything after that. After disabling Docker and starting the VM the CPU goes on some CPU Threads on 100 %. (Windows 11 fresh install) root@unRAID:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.0G 14G 13% / tmpfs 32M 420K 32M 2% /run /dev/sda1 15G 3.2G 12G 23% /boot overlay 16G 2.0G 14G 13% /lib/firmware overlay 16G 2.0G 14G 13% /lib/modules devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 476K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1 2.8T 1.3T 1.5T 48% /mnt/disk1 /dev/sdb1 466G 200G 264G 44% /mnt/cache shfs 2.8T 1.3T 1.5T 48% /mnt/user0 shfs 2.8T 1.3T 1.5T 48% /mnt/user /dev/loop3 50G 4.9M 50G 1% /etc/libvirt Forcing the shutdown doesn't work and after the 2nd try, Unraid crashes. After booting up, started the VM and it crashed after 1 hour again. root@unRAID:~# tail -f /var/log/syslog Sep 7 14:03:20 unRAID avahi-daemon[10293]: New relevant interface vnet0.IPv6 for mDNS. Sep 7 14:03:20 unRAID avahi-daemon[10293]: Registering new address record for fe80::fc54:ff:fe8d:ec92 on vnet0.*. Sep 7 14:03:20 unRAID flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Sep 7 14:05:59 unRAID ntpd[1724]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Sep 7 14:06:51 unRAID sshd[15169]: Connection from 10.0.10.117 port 1579 on 10.0.10.10 port 22 rdomain "" Sep 7 14:06:51 unRAID sshd[15169]: Postponed keyboard-interactive for root from 10.0.10.117 port 1579 ssh2 [preauth] Sep 7 14:06:56 unRAID sshd[15169]: Postponed keyboard-interactive/pam for root from 10.0.10.117 port 1579 ssh2 [preauth] Sep 7 14:06:56 unRAID sshd[15169]: Accepted keyboard-interactive/pam for root from 10.0.10.117 port 1579 ssh2 Sep 7 14:06:56 unRAID sshd[15169]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Sep 7 14:06:56 unRAID sshd[15169]: Starting session: shell on pts/1 for root from 10.0.10.117 port 1579 id 0 Sep 7 14:07:55 unRAID avahi-daemon[10293]: Interface vnet0.IPv6 no longer relevant for mDNS. Sep 7 14:07:55 unRAID avahi-daemon[10293]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe8d:ec92. Sep 7 14:07:55 unRAID kernel: br0: port 2(vnet0) entered disabled state Sep 7 14:07:55 unRAID kernel: device vnet0 left promiscuous mode Sep 7 14:07:55 unRAID kernel: br0: port 2(vnet0) entered disabled state Sep 7 14:07:55 unRAID avahi-daemon[10293]: Withdrawing address record for fe80::fc54:ff:fe8d:ec92 on vnet0. Sep 7 14:08:21 unRAID kernel: br0: port 2(vnet1) entered blocking state Sep 7 14:08:21 unRAID kernel: br0: port 2(vnet1) entered disabled state Sep 7 14:08:21 unRAID kernel: device vnet1 entered promiscuous mode Sep 7 14:08:21 unRAID kernel: br0: port 2(vnet1) entered blocking state Sep 7 14:08:21 unRAID kernel: br0: port 2(vnet1) entered forwarding state Sep 7 14:08:22 unRAID avahi-daemon[10293]: Joining mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:fe8d:ec92. Sep 7 14:08:22 unRAID avahi-daemon[10293]: New relevant interface vnet1.IPv6 for mDNS. Sep 7 14:08:22 unRAID avahi-daemon[10293]: Registering new address record for fe80::fc54:ff:fe8d:ec92 on vnet1.*. Sep 7 14:08:39 unRAID nmbd[10250]: [2022/09/07 14:08:39.002205, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Sep 7 14:08:39 unRAID nmbd[10250]: ***** Sep 7 14:08:39 unRAID nmbd[10250]: Sep 7 14:08:39 unRAID nmbd[10250]: Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Sep 7 14:08:39 unRAID nmbd[10250]: Sep 7 14:08:39 unRAID nmbd[10250]: ***** Sep 7 14:11:00 unRAID root: Fix Common Problems Version 2022.08.29 Sep 7 14:11:07 unRAID root: Fix Common Problems: Warning: NerdPack.plg Not Compatible with Unraid version 6.11.0-rc4 Sep 7 14:11:10 unRAID root: Fix Common Problems: Warning: Syslog mirrored to flash Sep 7 14:11:10 unRAID root: Fix Common Problems: Warning: The plugin usb_manager_usbip_addon.plg is not known to Community Applications and is possibly incompatible with your server Sep 7 14:36:46 unRAID kernel: ------------[ cut here ]------------ Sep 7 14:36:46 unRAID kernel: WARNING: CPU: 3 PID: 57 at kernel/rcu/tree.c:2634 rcu_do_batch+0x3d8/0x46c Sep 7 14:36:46 unRAID kernel: Modules linked in: xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap vhci_hcd usbip_host usbip_core xfs md_mod efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm btusb sr_mod btrtl cdrom btbcm kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel wmi_bmof ghash_clmulni_intel aesni_intel crypto_simd btintel cryptd i2c_piix4 backlight rapl bluetooth ccp k10temp i2c_core igc syscopyarea sysfillrect ahci sysimgblt fb_sys_fops joydev libahci ecdh_generic ecc wmi button unix Sep 7 14:36:46 unRAID kernel: CPU: 3 PID: 57 Comm: rcuop/6 Tainted: P O 5.19.3-Unraid #1 Sep 7 14:36:46 unRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B550 Taichi, BIOS P1.80 02/22/2021 Sep 7 14:36:46 unRAID kernel: RIP: 0010:rcu_do_batch+0x3d8/0x46c Sep 7 14:36:46 unRAID kernel: Code: 00 00 00 75 49 48 85 d2 74 44 31 c0 48 89 83 f0 00 00 00 48 8b 05 71 c6 fe 00 48 89 83 00 01 00 00 48 8b 43 78 48 85 c0 74 4a <0f> 0b 48 8b 3c 24 e8 91 54 00 00 48 85 c0 74 02 0f 0b 48 8b 3c 24 Sep 7 14:36:46 unRAID kernel: RSP: 0018:ffffc9000039be60 EFLAGS: 00010086 Sep 7 14:36:46 unRAID kernel: RAX: ffff888101494000 RBX: ffff888122390d70 RCX: 0000000000000000 Sep 7 14:36:46 unRAID kernel: RDX: 0000000100000000 RSI: ffffffffffffffed RDI: ffff88881e9acdb8 Sep 7 14:36:46 unRAID kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff88881e8ec070 Sep 7 14:36:46 unRAID kernel: R10: 0000000000000000 R11: ffff888100400058 R12: 0000000000000246 Sep 7 14:36:46 unRAID kernel: R13: 0000000000000013 R14: 000000000000000a R15: ffff888100a76e40 Sep 7 14:36:46 unRAID kernel: FS: 0000000000000000(0000) GS:ffff88881e8c0000(0000) knlGS:0000000000000000 Sep 7 14:36:46 unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 7 14:36:46 unRAID kernel: CR2: 0000000000462cb8 CR3: 000000019f590000 CR4: 0000000000350ee0 Sep 7 14:36:46 unRAID kernel: Call Trace: Sep 7 14:36:46 unRAID kernel: <TASK> Sep 7 14:36:46 unRAID kernel: ? preempt_latency_start+0x2b/0x46 Sep 7 14:36:46 unRAID kernel: rcu_nocb_cb_kthread+0x10f/0x28c Sep 7 14:36:46 unRAID kernel: ? rcu_cpu_kthread+0x10a/0x10a Sep 7 14:36:46 unRAID kernel: kthread+0xe7/0xef Sep 7 14:36:46 unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b Sep 7 14:36:46 unRAID kernel: ret_from_fork+0x22/0x30 Sep 7 14:36:46 unRAID kernel: </TASK> Sep 7 14:36:46 unRAID kernel: ---[ end trace 0000000000000000 ]--- Sep 7 14:36:46 unRAID kernel: ------------[ cut here ]------------ Sep 7 14:36:46 unRAID kernel: WARNING: CPU: 3 PID: 57 at kernel/rcu/tree.c:2637 rcu_do_batch+0x3e8/0x46c Sep 7 14:36:46 unRAID kernel: Modules linked in: xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap vhci_hcd usbip_host usbip_core xfs md_mod efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm btusb sr_mod btrtl cdrom btbcm kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel wmi_bmof ghash_clmulni_intel aesni_intel crypto_simd btintel cryptd i2c_piix4 backlight rapl bluetooth ccp k10temp i2c_core igc syscopyarea sysfillrect ahci sysimgblt fb_sys_fops joydev libahci ecdh_generic ecc wmi button unix Sep 7 14:36:46 unRAID kernel: CPU: 3 PID: 57 Comm: rcuop/6 Tainted: P W O 5.19.3-Unraid #1 Sep 7 14:36:46 unRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B550 Taichi, BIOS P1.80 02/22/2021 Sep 7 14:36:46 unRAID kernel: RIP: 0010:rcu_do_batch+0x3e8/0x46c Sep 7 14:36:46 unRAID kernel: Code: 00 00 00 48 8b 05 71 c6 fe 00 48 89 83 00 01 00 00 48 8b 43 78 48 85 c0 74 4a 0f 0b 48 8b 3c 24 e8 91 54 00 00 48 85 c0 74 02 <0f> 0b 48 8b 3c 24 e8 81 54 00 00 48 85 c0 75 41 0f 0b eb 3d 48 2b Sep 7 14:36:46 unRAID kernel: RSP: 0018:ffffc9000039be60 EFLAGS: 00010002 Sep 7 14:36:46 unRAID kernel: RAX: 0000000000000023 RBX: ffff888122390d70 RCX: 0000000000000000 Sep 7 14:36:46 unRAID kernel: RDX: 0000000000000000 RSI: ffffffffffffffed RDI: ffff88881e9acdb8 Sep 7 14:36:46 unRAID kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff88881e8ec070 Sep 7 14:36:46 unRAID kernel: R10: 0000000000000000 R11: ffff888100400058 R12: 0000000000000246 Sep 7 14:36:46 unRAID kernel: R13: 0000000000000013 R14: 000000000000000a R15: ffff888100a76e40 Sep 7 14:36:46 unRAID kernel: FS: 0000000000000000(0000) GS:ffff88881e8c0000(0000) knlGS:0000000000000000 Sep 7 14:36:46 unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 7 14:36:46 unRAID kernel: CR2: 0000000000462cb8 CR3: 000000019f590000 CR4: 0000000000350ee0 Sep 7 14:36:46 unRAID kernel: Call Trace: Sep 7 14:36:46 unRAID kernel: <TASK> Sep 7 14:36:46 unRAID kernel: ? preempt_latency_start+0x2b/0x46 Sep 7 14:36:46 unRAID kernel: rcu_nocb_cb_kthread+0x10f/0x28c Sep 7 14:36:46 unRAID kernel: ? rcu_cpu_kthread+0x10a/0x10a Sep 7 14:36:46 unRAID kernel: kthread+0xe7/0xef Sep 7 14:36:46 unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b Sep 7 14:36:46 unRAID kernel: ret_from_fork+0x22/0x30 Sep 7 14:36:46 unRAID kernel: </TASK> Sep 7 14:36:46 unRAID kernel: ---[ end trace 0000000000000000 ]--- Sep 7 14:36:46 unRAID kernel: BUG: scheduling while atomic: rcuop/6/57/0x00000002 Sep 7 14:36:46 unRAID kernel: Modules linked in: xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap vhci_hcd usbip_host usbip_core xfs md_mod efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm btusb sr_mod btrtl cdrom btbcm kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel wmi_bmof ghash_clmulni_intel aesni_intel crypto_simd btintel cryptd i2c_piix4 backlight rapl bluetooth ccp k10temp i2c_core igc syscopyarea sysfillrect ahci sysimgblt fb_sys_fops joydev libahci ecdh_generic ecc wmi button unix Sep 7 14:36:46 unRAID kernel: Preemption disabled at: Sep 7 14:36:46 unRAID kernel: [<ffffffff810cf30d>] rcu_do_batch+0x2e6/0x46c Sep 7 14:36:46 unRAID kernel: CPU: 3 PID: 57 Comm: rcuop/6 Tainted: P W O 5.19.3-Unraid #1 Sep 7 14:36:46 unRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B550 Taichi, BIOS P1.80 02/22/2021 Sep 7 14:36:46 unRAID kernel: Call Trace: Sep 7 14:36:46 unRAID kernel: <TASK> Sep 7 14:36:46 unRAID kernel: dump_stack_lvl+0x44/0x5c Sep 7 14:36:46 unRAID kernel: ? rcu_do_batch+0x2e6/0x46c Sep 7 14:36:46 unRAID kernel: __schedule_bug+0xa3/0xb6 Sep 7 14:36:46 unRAID kernel: __schedule+0x59/0x5f6 Sep 7 14:36:46 unRAID kernel: ? preempt_latency_start+0x2b/0x46 Sep 7 14:36:46 unRAID kernel: schedule+0x8e/0xc3 Sep 7 14:36:46 unRAID kernel: rcu_nocb_cb_kthread+0x90/0x28c Sep 7 14:36:46 unRAID kernel: ? rcu_cpu_kthread+0x10a/0x10a Sep 7 14:36:46 unRAID kernel: kthread+0xe7/0xef Sep 7 14:36:46 unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b Sep 7 14:36:46 unRAID kernel: ret_from_fork+0x22/0x30 Sep 7 14:36:46 unRAID kernel: </TASK> Sep 7 15:08:57 unRAID kernel: BUG: kernel NULL pointer dereference, address: 000000000000009c Sep 7 15:08:57 unRAID kernel: #PF: supervisor read access in kernel mode Sep 7 15:08:57 unRAID kernel: #PF: error_code(0x0000) - not-present page Sep 7 15:08:57 unRAID kernel: PGD 0 P4D 0 Sep 7 15:08:57 unRAID kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Sep 7 15:08:57 unRAID kernel: CPU: 6 PID: 0 Comm: swapper/6 Tainted: P W O 5.19.3-Unraid #1 Sep 7 15:08:57 unRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B550 Taichi, BIOS P1.80 02/22/2021 Sep 7 15:08:57 unRAID kernel: RIP: 0010:update_cfs_rq_load_avg+0x22/0x189 Sep 7 15:08:57 unRAID kernel: Code: 43 80 5b e9 c2 b3 96 00 41 57 41 56 41 55 41 54 55 48 89 fd 53 48 89 f3 41 51 44 8b a6 c4 00 00 00 45 85 e4 0f 84 49 01 00 00 <8b> 86 9c 00 00 00 48 8d be c0 00 00 00 48 89 3c 24 44 8d a8 7e b6 Sep 7 15:08:57 unRAID kernel: RSP: 0018:ffffc90000187e90 EFLAGS: 00010006 Sep 7 15:08:57 unRAID kernel: RAX: ffff8881022c4f0f RBX: ffff88881e9abfc0 RCX: ffff88881e9aca28 Sep 7 15:08:57 unRAID kernel: RDX: ffff88881e9aca28 RSI: 0000000000000000 RDI: ffff88881e9abfc0 Sep 7 15:08:57 unRAID kernel: RBP: ffff8881022c4ec0 R08: 0000000000000000 R09: ffff88881e99f0e0 Sep 7 15:08:57 unRAID kernel: R10: 0000000000000003 R11: 0000000000000000 R12: ffff888100906e40 Sep 7 15:08:57 unRAID kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffffc90000187ed8 Sep 7 15:08:57 unRAID kernel: FS: 0000000000000000(0000) GS:ffff88881e980000(0000) knlGS:0000000000000000 Sep 7 15:08:57 unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 7 15:08:57 unRAID kernel: CR2: 000000000000009c CR3: 00000004b0bb8000 CR4: 0000000000350ee0 Sep 7 15:08:57 unRAID kernel: Call Trace: Sep 7 15:08:57 unRAID kernel: <TASK> Sep 7 15:08:57 unRAID kernel: ? __schedule+0x1ba/0x5f6 Sep 7 15:08:57 unRAID kernel: ? schedule_idle+0x27/0x34 Sep 7 15:08:57 unRAID kernel: ? cpu_startup_entry+0x1d/0x1f Sep 7 15:08:57 unRAID kernel: ? start_secondary+0xeb/0xeb Sep 7 15:08:57 unRAID kernel: ? secondary_startup_64_no_verify+0xce/0xdb Sep 7 15:08:57 unRAID kernel: </TASK> Sep 7 15:08:57 unRAID kernel: Modules linked in: xt_CHECKSUM xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap vhci_hcd usbip_host usbip_core xfs md_mod efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper drm btusb sr_mod btrtl cdrom btbcm kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel wmi_bmof ghash_clmulni_intel aesni_intel crypto_simd btintel cryptd i2c_piix4 backlight rapl bluetooth ccp k10temp i2c_core igc syscopyarea sysfillrect ahci sysimgblt fb_sys_fops joydev libahci ecdh_generic ecc wmi button unix Sep 7 15:08:57 unRAID kernel: CR2: 000000000000009c Sep 7 15:08:57 unRAID kernel: ---[ end trace 0000000000000000 ]--- Sep 7 15:08:57 unRAID kernel: xhci_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command Sep 7 15:08:57 unRAID kernel: xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead Sep 7 15:08:57 unRAID kernel: xhci_hcd 0000:01:00.0: HC died; cleaning up Sep 7 15:08:57 unRAID kernel: usb 1-3: USB disconnect, device number 2 Sep 7 15:08:57 unRAID kernel: usb 1-5: USB disconnect, device number 3 Sep 7 15:08:57 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:57 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 3d 9c 92 00 00 01 00 Sep 7 15:08:57 unRAID kernel: I/O error, dev sda, sector 20814994 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 08 01 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 2049 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 2f c4 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 12228 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 10180, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 3d 9c a2 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 20815010 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 3d 9c c2 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 20815042 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 69 04 00 00 02 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 26884 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 24836, lost async page write Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 24837, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 7a a2 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 31394 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 29346, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 85 b5 00 00 02 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 34229 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 32181, lost async page write Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 32182, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 2f c3 00 00 02 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 12227 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 10179, lost async page write Sep 7 15:08:58 unRAID kernel: Buffer I/O error on dev sda1, logical block 10180, lost async page write Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Sep 7 15:08:58 unRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 85 b5 00 00 01 00 Sep 7 15:08:58 unRAID kernel: I/O error, dev sda, sector 34229 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 7 15:08:58 unRAID kernel: FAT-fs (sda1): Directory bread(block 32181) failed Sep 7 15:08:58 unRAID kernel: FAT-fs (sda1): Directory bread(block 32182) failed Sep 7 15:08:58 unRAID kernel: FAT-fs (sda1): Directory bread(block 32181) failed Sep 7 15:08:58 unRAID kernel: FAT-fs (sda1): Directory bread(block 32182) failed Sep 7 15:08:58 unRAID kernel: FAT-fs (sda1): Directory bread(block 32181) failed I am thinking of creating a backup and reinstalling Unraid on the stick... Is there anything to consider before I do this? For example, the layout of the hard drives or saving the docker templates? syslog unraid-diagnostics-20220907-1336.zip

Thanks for the reply. Then I take back the GPU from passtrough again, hoping that no crash happens and I can get the informotions locally. Assuming the RAM would fill up, would a RAM expansion be enough? I had planned to go from 32 GB to 64 anyway.

Yesterday I made a memtest which passed. I'm running out of ideas. Does anyone have any suggestions what I could do? Because unfortunately this can not stay like this. I depend on the VMs and it is among other things the reason why I use Unraid at all.

1. I installed the RC2 to test if there are still the same problems. After 18 Days and 5 hours uptime I started a Windows 11 and a Kali VM which I started installing (Stopped at user creation). Just to check if the problem appears again. I lost my RDP Session, tried to ping, nothing happened. This freeze happened after 20 - 30 minutes. 2. i checked the Syslog and it increased a little bit. 42.5 mb... Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] Jul 27 08:06:18 unRAID kernel: vfio-pci 0000:0a:00.0: BAR 3: can't reserve [mem 0xe0000000-0xe1ffffff 64bit pref] This line shows 364433 times up. I removed these lines and replaced it with --- syslog-edit.log unraid-diagnostics-20220824-0756.zip

Großartig. Müssen nach einspielen des Updates Anpassungen am Bios gemacht werden? (C-States z.B.)

So I updated to 6.10.3 again, took the IOMMU Groups back to Unraid, started a VM without any connected hardware device and it froze again. After checking the monitor I saw a Kernel Panic happened. So I couldn't check the diagnostics or "disk free" (df -h). Edit: Forgot to give you the diagnostics and logs after reboot. server-syslogusb-syslogunraid-diagnostics-20220726-0759.zip After starting Unraid, this messages showed up:

Ok, I will try that in the next days. Trank you Gesendet von iPhone mit Tapatalk

I could. I would have to remove the GPU and the USB controller from the passthrough, but that should not affect the error pattern. After all, it affected the VMs with and without passthrough. Should I check something specific or should I just see if the system reacts at all when "freezing".

Update: After the revert to 6.10.2 the Windows 10 and 11 machines are freezing after 1 hour. Not Unraid anymore. 👍 The Kali machine (without GUI) is online over 4 hours and nothing special is going wrong. So I consider the Guest OS makes the trouble. Do I have to check the "Energy saving" options from Windows? (Both options are on "never") Yes both of them. But there are not used for the VM in that case. Mouse and keyboard are passthrough(ed?) with the USB Controller. Monitor is connected with the only GPU which is also passthrough(ed?).