-
The unraid server suddenly became inaccessible on March 3 at 9:30pm, with logs indicating kernel errors.
Thank you syslog-192.168.2.55.log
-
The unraid server suddenly became inaccessible on March 3 at 9:30pm, with logs indicating kernel errors.
tower-diagnostics-20250303-2352.zip Any help is appreciated. log: Mar 3 19:59:58 Tower webgui: Successful login user root from 192.168.2.15 Mar 3 21:05:34 Tower monitor_nchan: Stop running nchan processes Mar 3 21:20:08 Tower nmbd[2967]: validate_nmb_packet: Bad QUERY Packet. validate_nmb_packet: Ignoring request packet with opcode 0. Mar 3 21:20:08 Tower nmbd[2967]: validate_nmb_packet: Bad QUERY Packet. validate_nmb_packet: Ignoring request packet with opcode 0. Mar 3 21:20:10 Tower nmbd[2967]: validate_nmb_packet: Bad QUERY Packet. validate_nmb_packet: Ignoring request packet with opcode 0. Mar 3 21:26:28 Tower kernel: ------------[ cut here ]------------ Mar 3 21:26:28 Tower kernel: kernel BUG at fs/buffer.c:3042! Mar 3 21:26:28 Tower kernel: invalid opcode: 0000 [#1] PREEMPT SMP PTI Mar 3 21:26:28 Tower kernel: CPU: 36 PID: 453 Comm: kswapd0 Tainted: P O 6.6.78-Unraid #2 Mar 3 21:26:28 Tower kernel: Hardware name: NVIDIA DGX Station/X99-E-10G WS, BIOS 1201 05/27/2019 Mar 3 21:26:28 Tower kernel: RIP: 0010:free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: Code: c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b 57 48 48 8d 47 48 48 89 fe 48 39 c2 74 02 <0f> 0b 48 8b 3d b8 6f 30 01 e8 06 a3 f9 ff bf 01 00 00 00 e8 58 29 Mar 3 21:26:28 Tower kernel: RSP: 0018:ffffc900050afa50 EFLAGS: 00010206 Mar 3 21:26:28 Tower kernel: RAX: ffff8881abd52b40 RBX: ffff8881abd52af8 RCX: 0000000000000000 Mar 3 21:26:28 Tower kernel: RDX: ffff88a1abd52b40 RSI: ffff8881abd52af8 RDI: ffff8881abd52af8 Mar 3 21:26:28 Tower kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000080270022 Mar 3 21:26:28 Tower kernel: R10: 0000000000000246 R11: 0000000000000024 R12: ffff8881abd52af8 Mar 3 21:26:28 Tower kernel: R13: ffff888184b48520 R14: 0000000000000001 R15: ffffea004e575bc8 Mar 3 21:26:28 Tower kernel: FS: 0000000000000000(0000) GS:ffff889fbfd00000(0000) knlGS:0000000000000000 Mar 3 21:26:28 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 3 21:26:28 Tower kernel: CR2: 00001455f0404000 CR3: 00000001271ea006 CR4: 00000000003726e0 Mar 3 21:26:28 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 3 21:26:28 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 3 21:26:28 Tower kernel: Call Trace: Mar 3 21:26:28 Tower kernel: <TASK> Mar 3 21:26:28 Tower kernel: ? __die_body+0x1a/0x5c Mar 3 21:26:28 Tower kernel: ? die+0x30/0x49 Mar 3 21:26:28 Tower kernel: ? do_trap+0x7b/0xfe Mar 3 21:26:28 Tower kernel: ? free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: ? free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: ? do_error_trap+0x6e/0x98 Mar 3 21:26:28 Tower kernel: ? free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: ? exc_invalid_op+0x4c/0x60 Mar 3 21:26:28 Tower kernel: ? free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Mar 3 21:26:28 Tower kernel: ? free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: try_to_free_buffers+0x9b/0xc4 Mar 3 21:26:28 Tower kernel: shrink_folio_list+0x78c/0x920 Mar 3 21:26:28 Tower kernel: ? cgroup_rstat_updated+0x21/0xa5 Mar 3 21:26:28 Tower kernel: shrink_lruvec+0x614/0x9a8 Mar 3 21:26:28 Tower kernel: ? preempt_latency_start+0x1e/0x46 Mar 3 21:26:28 Tower kernel: ? preempt_latency_start+0x1e/0x46 Mar 3 21:26:28 Tower kernel: shrink_node+0x4ca/0x734 Mar 3 21:26:28 Tower kernel: balance_pgdat+0x419/0x5e3 Mar 3 21:26:28 Tower kernel: ? __perf_event_task_sched_out+0x33/0x3d1 Mar 3 21:26:28 Tower kernel: kswapd+0x2d6/0x319 Mar 3 21:26:28 Tower kernel: ? __pfx_autoremove_wake_function+0x10/0x10 Mar 3 21:26:28 Tower kernel: ? __pfx_kswapd+0x10/0x10 Mar 3 21:26:28 Tower kernel: kthread+0xf4/0xfc Mar 3 21:26:28 Tower kernel: ? __pfx_kthread+0x10/0x10 Mar 3 21:26:28 Tower kernel: ret_from_fork+0x24/0x36 Mar 3 21:26:28 Tower kernel: ? __pfx_kthread+0x10/0x10 Mar 3 21:26:28 Tower kernel: ret_from_fork_asm+0x1b/0x30 Mar 3 21:26:28 Tower kernel: </TASK> Mar 3 21:26:28 Tower kernel: Modules linked in: dm_mod nvidia_uvm(PO) xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge stp llc nfsd auth_rpcgss lockd grace sunrpc md_mod ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap bonding tls ixgbe xfrm_algo mdio intel_rapl_common iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel nvidia_drm(PO) nvidia_modeset(PO) zfs(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel nvidia(PO) crypto_simd cryptd mei_me rapl spl(O) drm_kms_helper intel_cstate wmi_bmof intel_wmi_thunderbolt mxm_wmi drm intel_uncore nvme i2c_i801 backlight mei i2c_smbus nvme_core i2c_core ahci libahci wmi button [last unloaded: xfrm_algo] Mar 3 21:26:28 Tower kernel: ---[ end trace 0000000000000000 ]--- Mar 3 21:26:28 Tower kernel: pstore: backend (efi_pstore) writing error (-5) Mar 3 21:26:28 Tower kernel: RIP: 0010:free_buffer_head+0x15/0x64 Mar 3 21:26:28 Tower kernel: Code: c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b 57 48 48 8d 47 48 48 89 fe 48 39 c2 74 02 <0f> 0b 48 8b 3d b8 6f 30 01 e8 06 a3 f9 ff bf 01 00 00 00 e8 58 29 Mar 3 21:26:28 Tower kernel: RSP: 0018:ffffc900050afa50 EFLAGS: 00010206 Mar 3 21:26:28 Tower kernel: RAX: ffff8881abd52b40 RBX: ffff8881abd52af8 RCX: 0000000000000000 Mar 3 21:26:28 Tower kernel: RDX: ffff88a1abd52b40 RSI: ffff8881abd52af8 RDI: ffff8881abd52af8 Mar 3 21:26:28 Tower kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000080270022 Mar 3 21:26:28 Tower kernel: R10: 0000000000000246 R11: 0000000000000024 R12: ffff8881abd52af8 Mar 3 21:26:28 Tower kernel: R13: ffff888184b48520 R14: 0000000000000001 R15: ffffea004e575bc8 Mar 3 21:26:28 Tower kernel: FS: 0000000000000000(0000) GS:ffff889fbfd00000(0000) knlGS:0000000000000000 Mar 3 21:26:28 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 3 21:26:28 Tower kernel: CR2: 00001455f0404000 CR3: 00000001271ea006 CR4: 00000000003726e0 Mar 3 21:26:28 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 3 21:26:28 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 3 21:26:28 Tower kernel: ------------[ cut here ]------------ Mar 3 21:26:28 Tower kernel: WARNING: CPU: 36 PID: 453 at kernel/exit.c:820 do_exit+0x81/0x90b Mar 3 21:26:28 Tower kernel: Modules linked in: dm_mod nvidia_uvm(PO) xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge stp llc nfsd auth_rpcgss lockd grace sunrpc md_mod ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap bonding tls ixgbe xfrm_algo mdio intel_rapl_common iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel nvidia_drm(PO) nvidia_modeset(PO) zfs(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel nvidia(PO) crypto_simd cryptd mei_me rapl spl(O) drm_kms_helper intel_cstate wmi_bmof intel_wmi_thunderbolt mxm_wmi drm intel_uncore nvme i2c_i801 backlight mei i2c_smbus nvme_core i2c_core ahci libahci wmi button [last unloaded: xfrm_algo] Mar 3 21:26:28 Tower kernel: CPU: 36 PID: 453 Comm: kswapd0 Tainted: P D O 6.6.78-Unraid #2 Mar 3 21:26:28 Tower kernel: Hardware name: NVIDIA DGX Station/X99-E-10G WS, BIOS 1201 05/27/2019 Mar 3 21:26:28 Tower kernel: RIP: 0010:do_exit+0x81/0x90b Mar 3 21:26:28 Tower 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 62 d9 9c 00 48 83 bb c0 07 00 00 00 74 02 <0f> 0b 48 8b bb d8 06 00 00 e8 2c d8 9c 00 48 8b 83 d0 06 00 00 83 Mar 3 21:26:28 Tower kernel: RSP: 0018:ffffc900050afee0 EFLAGS: 00010282 Mar 3 21:26:28 Tower kernel: RAX: 0000000000000000 RBX: ffff888103e12f40 RCX: 0000000000000000 Mar 3 21:26:28 Tower kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: 00000000ffffffff Mar 3 21:26:28 Tower kernel: RBP: 000000000000000b R08: 0000000000000000 R09: ffff88810a181e90 Mar 3 21:26:28 Tower kernel: R10: 0000000000000001 R11: 0000000000aaaaaa R12: ffff888103a8fb40 Mar 3 21:26:28 Tower kernel: R13: ffff888103aa7380 R14: 0000000000000002 R15: ffffffff8222c44c Mar 3 21:26:28 Tower kernel: FS: 0000000000000000(0000) GS:ffff889fbfd00000(0000) knlGS:0000000000000000 Mar 3 21:26:28 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 3 21:26:28 Tower kernel: CR2: 00001455f0404000 CR3: 00000001271ea006 CR4: 00000000003726e0 Mar 3 21:26:28 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 3 21:26:28 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 3 21:26:28 Tower kernel: Call Trace: Mar 3 21:26:28 Tower kernel: <TASK> Mar 3 21:26:28 Tower kernel: ? __warn+0x99/0x11a Mar 3 21:26:28 Tower kernel: ? report_bug+0xd9/0x153 Mar 3 21:26:28 Tower kernel: ? do_exit+0x81/0x90b Mar 3 21:26:28 Tower kernel: ? handle_bug+0x53/0x7c Mar 3 21:26:28 Tower kernel: ? exc_invalid_op+0x13/0x60 Mar 3 21:26:28 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Mar 3 21:26:28 Tower kernel: ? do_exit+0x81/0x90b Mar 3 21:26:28 Tower kernel: ? __pfx_kswapd+0x10/0x10 Mar 3 21:26:28 Tower kernel: ? kthread+0xf4/0xfc Mar 3 21:26:28 Tower kernel: make_task_dead+0x113/0x113 Mar 3 21:26:28 Tower kernel: rewind_stack_and_make_dead+0x17/0x17 Mar 3 21:26:28 Tower kernel: RIP: 0000:0x0 Mar 3 21:26:28 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Mar 3 21:26:28 Tower kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000 Mar 3 21:26:28 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Mar 3 21:26:28 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Mar 3 21:26:28 Tower kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Mar 3 21:26:28 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Mar 3 21:26:28 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Mar 3 21:26:28 Tower kernel: </TASK> Mar 3 21:26:28 Tower kernel: ---[ end trace 0000000000000000 ]---
-
Unraid logs are suddenly full of errors
I think after docker and the VM are shut down, the reporting stops. I want to know how to locate the error. Feb 20 22:16:59 Tower nginx: 2025/02/20 22:16:59 [error] 1229089#1229089: nchan: Out of shared memory while allocating message of size 22018. Increase nchan_max_reserved_memory. Feb 20 22:16:59 Tower nginx: 2025/02/20 22:16:59 [error] 1229089#1229089: *722557 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Feb 20 22:16:59 Tower nginx: 2025/02/20 22:16:59 [error] 1229089#1229089: MEMSTORE:01: can't create shared message for channel /devices Feb 20 22:17:00 Tower nginx: 2025/02/20 22:17:00 [crit] 1229089#1229089: ngx_slab_alloc() failed: no memory Feb 20 22:17:00 Tower nginx: 2025/02/20 22:17:00 [error] 1229089#1229089: shpool alloc failed tower-diagnostics-20250220-2304.zip
-
Odd Ngnix error filling up my syslog
I'm having this problem too.
-
The server is suddenly inaccessible
thank you tower-diagnostics-20240508-1428.zip
-
The server is suddenly inaccessible
I replaced my RAM yesterday afternoon, I wonder if it has anything to do with my new RAM? syslog-192.168.2.55.log
-
关于缓存机制,问题与解决
unraid没点移动直接取消了文件夹缓存,导致文件夹的文件遗留在了ssd里,这种情况有办法处理吗?
-
My unraid server suddenly became inaccessible
syslog-192.168.2.55.log.zip It happened again, this time I am using the unaid system to record logs
-
My unraid server suddenly became inaccessible
log_2022-7-23-19_40_12.html.zip Sorry, this is my log file, it's a bit big, 102MB.
-
My unraid server suddenly became inaccessible
I saved the logs from before the server became inaccessible to Synology. These are screenshots. Can you tell where the problem is? Thanks a lot! It looks like it's been out of whack since 00:00 last night. It dropped completely at 11:00 today. I had to restart the server at 4:30 this afternoon.
-
My unraid server suddenly became inaccessible
My unraid server suddenly became inaccessible and had to be restarted manually. I would like to know if it is a hardware problem or a software problem? This is the second time this has happened and I have no clue about it. tower-diagnostics-20220630-1011.zip
-
disk 2 Unmountable: not mounted
I stopped the array this afternoon and added a HDD to the array. When I restarted the array , one of the old disk came up with an unmountable message. tower-diagnostics-20210914-1842.zip
binghunlong
Members
-
Joined
-
Last visited