October 23, 20241 yr I've been having an operatic issue the past few months where one of my unraid servers completely becomes unresponsive. I cannot ping it, or interactive with it in the GUI locally. I found the bug check but need some help deciphering. It appears to clear it'self sometimes, other times I've had to hard reboot. 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ------------[ cut here ]------------ 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Can't encode file handler for inotify: 255 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel WARNING: CPU: 2 PID: 3330128 at fs/notify/fdinfo.c:55 show_mark_fhandle+0x77/0xe6 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Modules linked in: xt_mark nft_compat nft_chain_nat dm_mod ipvlan nf_tables xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls zfs(PO) spl(O) mei_hdcp mei_pxp mei_gsc mei_me mei i915 edac_mce_amd edac_core intel_rapl_common iosf_mbi drm_buddy ttm video i2c_algo_bit kvm_amd drm_display_helper drm_kms_helper kvm crct10dif_pclmul crc32_pclmul drm crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd wmi_bmof mxm_wmi rapl backlight mpt3sas nvme acpi_cpufreq intel_gtt i2c_piix4 agpgart r8169 k10temp ccp i2c_core raid_class ahci nvme_core 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel scsi_transport_sas realtek libahci tpm_crb wmi tpm_tis tpm_tis_core tpm button 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel CPU: 2 PID: 3330128 Comm: lsof Tainted: P O 6.6.52-Unraid #2 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Hardware name: Micro-Star International Co., Ltd. MS-7A33/X370 GAMING PLUS (MS-7A33), BIOS 5.JS 11/02/2021 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RIP: 0010:show_mark_fhandle+0x77/0xe6 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Code: ff 00 00 00 89 c1 74 04 85 c0 79 22 80 3d 36 24 2d 01 00 75 5e 89 ce 48 c7 c7 7f df 25 82 c6 05 24 24 2d 01 01 e8 69 b7 d8 ff <0f> 0b eb 45 89 44 24 0c 8b 44 24 04 48 89 ef 31 db 48 c7 c6 bd df 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RSP: 0018:ffffc900022b3c10 EFLAGS: 00010286 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RAX: 0000000000000000 RBX: ffff88810615bbf0 RCX: 0000000000000027 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RDX: 0000000082c1bc70 RSI: ffffffff822430c0 RDI: 00000000ffffffff 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RBP: ffff888103753000 R08: 0000000000000000 R09: ffffffff82c1bc70 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel R10: 00003fffffffffff R11: 000000002d2d2d2d R12: ffff888103753000 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel R13: ffff888103753000 R14: ffffffff812e7104 R15: ffff888103d42078 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel FS: 00001541048e3f00(0000) GS:ffff8887fe880000(0000) knlGS:0000000000000000 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel CR2: 00000000004c3048 CR3: 000000019246c000 CR4: 00000000003506e0 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Call Trace: 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel <TASK> 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? __warn+0x99/0x11a 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? report_bug+0xd9/0x153 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? show_mark_fhandle+0x77/0xe6 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? handle_bug+0x3c/0x63 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? exc_invalid_op+0x13/0x60 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? asm_exc_invalid_op+0x16/0x20 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? __pfx_inotify_fdinfo+0x10/0x10 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? show_mark_fhandle+0x77/0xe6 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? __pfx_inotify_fdinfo+0x10/0x10 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? srso_return_thunk+0x5/0x5f 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? seq_vprintf+0x2d/0x49 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? srso_return_thunk+0x5/0x5f 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? seq_printf+0x53/0x6e 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? preempt_latency_start+0x2b/0x46 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? srso_return_thunk+0x5/0x5f 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel inotify_fdinfo+0x83/0xaa 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel show_fdinfo.isra.0+0x66/0xab 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel seq_show+0x155/0x173 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel seq_read_iter+0x171/0x353 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel seq_read+0x91/0xbb 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel vfs_read+0xa7/0x1d1 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? srso_return_thunk+0x5/0x5f 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ? __do_sys_newfstat+0x34/0x5c 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ksys_read+0x74/0xc0 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel do_syscall_64+0x57/0x7b 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel entry_SYSCALL_64_after_hwframe+0x78/0xe2 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RIP: 0033:0x154104b7b6ed 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel Code: 21 87 0e 00 f7 d8 64 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 80 3d 59 0b 0f 00 00 74 17 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RSP: 002b:00007ffc1ab07518 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RAX: ffffffffffffffda RBX: 000000000043f600 RCX: 0000154104b7b6ed 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RDX: 0000000000000400 RSI: 0000000000447e90 RDI: 0000000000000007 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel RBP: 0000154104c631f0 R08: 0000000000000001 R09: 0000000000000000 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel R10: 0000000000000000 R11: 0000000000000246 R12: 0000154104c630a0 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel R13: 0000000000000000 R14: 0000000000001000 R15: 000000000043f600 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel </TASK> 192.168.1.15 Oct 22 09:14:11 Unraid01 kern warning kernel ---[ end trace 0000000000000000 ]--- unraid01-diagnostics-20241023-0827.zip
October 23, 20241 yr Community Expert This specific call trace is harmless, enable the syslog server and post that after a crash.
October 23, 20241 yr Author I have remote sysloging e nabled currently, that's where I pulled the trace from. There's nothing for 10 minutes before that trace. I know it froze at the time of the log because I was watching Plex and everything stopped.
October 23, 20241 yr Community Expert If there's nothing relevant logged, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.