Hello,

I've been having problems with Unraid for some time now. Here is an excerpt from the log.

Does anyone have any idea what the problem might be?

Feb  9 09:25:56 DatenTruhe kernel: ------------[ cut here ]------------
Feb  9 09:25:56 DatenTruhe kernel: WARNING: CPU: 0 PID: 9813 at kernel/exit.c:886 do_exit+0x80/0x8d0
Feb  9 09:25:56 DatenTruhe kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap br_netfilter xt_nat xt_tcpudp ipvlan xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet cfg80211 rfkill 8021q garp mrp bridge stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel mei_hdcp mei_pxp kvm wmi_bmof iosf_mbi drm_buddy ttm i2c_algo_bit drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_kms_helper sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl drm intel_cstate intel_uncore intel_gtt i2c_i801 agpgart i2c_smbus e1000e mei_me input_leds led_class i2c_core mei thermal fan video wmi backlight button
Feb  9 09:25:56 DatenTruhe kernel: CPU: 0 UID: 0 PID: 9813 Comm: unraidd0 Tainted: P      D W  O       6.12.54-Unraid #1
Feb  9 09:25:56 DatenTruhe kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [W]=WARN, [O]=OOT_MODULE
Feb  9 09:25:56 DatenTruhe kernel: Hardware name: ASUS All Series/H87I-PLUS, BIOS 2003 11/05/2014
Feb  9 09:25:56 DatenTruhe kernel: RIP: 0010:do_exit+0x80/0x8d0
Feb  9 09:25:56 DatenTruhe kernel: Code: 24 74 04 75 13 b8 01 00 00 00 41 89 6c 24 60 48 c1 e0 22 49 89 44 24 70 4c 89 ef e8 ea aa ae 00 48 83 bb 28 08 00 00 00 74 02 <0f> 0b 48 8b bb 40 07 00 00 e8 92 a9 ae 00 48 8b 83 38 07 00 00 83
Feb  9 09:25:56 DatenTruhe kernel: RSP: 0018:ffffc900094ffee8 EFLAGS: 00010286
Feb  9 09:25:56 DatenTruhe kernel: RAX: 0000000400000000 RBX: ffff88817ccb2100 RCX: 0000000000000001
Feb  9 09:25:56 DatenTruhe kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: 00000000ffffffff
Feb  9 09:25:56 DatenTruhe kernel: RBP: 000000000000000b R08: 0000000000000000 R09: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: R10: 0000000000aaaaaa R11: 0000000000000001 R12: ffff888102d4c400
Feb  9 09:25:56 DatenTruhe kernel: R13: ffff888102e20840 R14: 0000000000000000 R15: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: FS:  0000000000000000(0000) GS:ffff88840fa00000(0000) knlGS:0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb  9 09:25:56 DatenTruhe kernel: CR2: 00001465e93ff840 CR3: 0000000185b54001 CR4: 00000000001726f0
Feb  9 09:25:56 DatenTruhe kernel: Call Trace:
Feb  9 09:25:56 DatenTruhe kernel: <TASK>
Feb  9 09:25:56 DatenTruhe kernel: make_task_dead+0x104/0x110
Feb  9 09:25:56 DatenTruhe kernel: rewind_stack_and_make_dead+0x16/0x20
Feb  9 09:25:56 DatenTruhe kernel: RIP: 0000:0x0
Feb  9 09:25:56 DatenTruhe kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Feb  9 09:25:56 DatenTruhe kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Feb  9 09:25:56 DatenTruhe kernel: </TASK>
Feb  9 09:25:56 DatenTruhe kernel: ---[ end trace 0000000000000000 ]---

Thank you

Pixel-Pete

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread.

It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

Sorry.. Here are my diagnostics.

Thank you

datentruhe-diagnostics-20260209-1127.zip

Can you expand on

2 hours ago, Pixel-Pete said:

having problems

Of course :-) :

After a restart, the error messages appear in the log. I can no longer access my array, even though it is online. The GUI is sometimes unavailable and the system sometimes freezes. Some of the Docker containers still work.

I have now removed all Docker containers from autostart, including the Home Assistant VM.

Now the system starts without any errors in the log. Could it be due to the VM or a Docker container?

At first, I suspected the hardware, as the server is already a bit older.

1 hour ago, Pixel-Pete said:

Could it be due to the VM or a Docker container?

It could, you can also enable the syslog server to see if it catches something more if you cannot get the normal diags after the issues happen.

I have now started the syslog server. Then I reconnected my Zigbee and the Thread Stick for the Home Assistant VM and booted up the VM. I also restarted all the Docker containers that I need at a minimum.

So far, there have been no crashes. Let's see what happens over time.

If it is a hardware problem, it should occur again at some point.