onyx00

Something is very wrong. Random crashes, etc. No idea what is going on or why. I thought it was the RAM, s I ran memtest overnight and 5 passes succeeded, so I'm having a hard time thinking it is that now. I have disabled NFS for now in hopes that helps, but wtf is wrong is beyond me. tower-diagnostics-20251208-0744.zip

Can't say if 7.2.2 update is related, but I started seeing docker that would not start (execution error). I rolled back to 7.2.1 and thought everything was fine, and now I am seeing share issues like below in midnight commander. Diagnostics attached, can anyone shed some light or point me what I should be looking at as the issue? Nothing hardware wise has changed. . tower-diagnostics-20251207-1712.zip

Came here to share similar issues - segfaults and related.

Related question - if you are getting random crashes, will the remote server and/or mirror to flash catch all crashes including kernel?

Not sure what is going on, but I wake up to stack trace dump and nothing in syslog. Frustrated...any ideas or help? Syslog doesn't show much but I grabbed a picture of the console before reboot. And of course diagnostic attached for good measure but not sure how helpful it will be. Would mirroring syslog to flash help capture more information for the next (😒) crash? EDIT: added small section of syslog showing time leading up to crash. Only thing I see is some docker seg faults 6 hours earlier, but not sure if that would be related. Apr 9 19:11:14 Tower rc.nfsd: NFS server daemon... Started. Apr 9 19:14:51 Tower root: Fix Common Problems Version 2025.03.12 Apr 9 19:14:52 Tower root: Fix Common Problems: Warning: Docker Application ClamAV has an update available for it Apr 9 19:14:52 Tower root: Fix Common Problems: Warning: Docker Application n8n has an update available for it Apr 9 19:14:56 Tower root: Fix Common Problems: Warning: Share downloads set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:14:56 Tower root: Fix Common Problems: Warning: Share Temp set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:14:56 Tower kernel: block nvme0n1: the capability attribute has been deprecated. Apr 9 19:14:57 Tower kernel: r8169 0000:04:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Apr 9 19:14:57 Tower kernel: mpt3sas 0000:05:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Apr 9 19:20:00 Tower root: Fix Common Problems Version 2025.03.12 Apr 9 19:20:04 Tower root: Fix Common Problems: Warning: Share downloads set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:20:04 Tower root: Fix Common Problems: Warning: Share Temp set to use pool cachessd, but files / folders exist on the cache pool Apr 9 20:19:08 Tower kernel: Radarr[19134]: segfault at 12e7 ip 0000154fe97c5f7e sp 0000154fe83f6d90 error 6 in libsqlite3.so.3.49.1[154fe9697000+130000] likely on CPU 7 (core 12, socket 0) Apr 9 20:19:08 Tower kernel: Code: 71 2c 03 71 28 48 f7 d8 48 63 f6 48 c1 e0 0a 48 99 48 f7 fe ba 00 ca 9a 3b 48 39 d0 48 0f 4e d0 48 89 d6 48 8b 79 48 41 ff d0 <41> 80 00 24 11 00 00 08 41 83 00 24 14 01 00 22 48 83 00 10 41 5c Apr 9 20:28:04 Tower kernel: traps: Plex Transcoder[399491] general protection fault ip:14953c1edd26 sp:149539a38770 error:0 in libh264_decoder.so[14953c13d000+13e000] Apr 9 20:55:47 Tower kernel: python3[18875]: segfault at 140043703100 ip 000014bc45783543 sp 00007ffd37362080 error 4 in libpython3.13.so.1.0[14bc4563a000+2c0000] likely on CPU 2 (core 4, socket 0) Apr 9 20:55:47 Tower kernel: Code: 89 cf ff e0 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 49 89 f5 41 54 49 89 fc 53 48 83 ec 18 4c 8b 3f eb 2f 0f 1f 40 00 4d 89 fe <49> 8b 17 49 8b 46 10 49 8b 5e 08 49 89 d7 85 c0 0f 88 55 1a ed ff Apr 9 22:15:06 Tower emhttpd: spinning down /dev/sdd Apr 9 22:15:07 Tower emhttpd: spinning down /dev/sdc Apr 9 22:17:21 Tower kernel: traps: Plex Transcoder[1111868] general protection fault ip:14a46af4fd26 sp:14a46943f770 error:0 in libh264_decoder.so[14a46ae9f000+13e000] Apr 9 22:21:38 Tower emhttpd: spinning down /dev/sdi Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdk Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdg Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sde Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdf Apr 9 23:19:02 Tower emhttpd: spinning down /dev/sdh Apr 10 00:19:47 Tower emhttpd: spinning down /dev/sdn Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdm Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdo Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdl Apr 10 00:20:11 Tower emhttpd: spinning down /dev/sdj Apr 10 01:00:12 Tower emhttpd: read SMART /dev/sde Apr 10 01:00:14 Tower emhttpd: read SMART /dev/sdi Apr 10 01:00:24 Tower emhttpd: read SMART /dev/sdg Apr 10 01:00:24 Tower emhttpd: read SMART /dev/sdf Apr 10 01:03:26 Tower emhttpd: read SMART /dev/sdh Apr 10 02:00:01 Tower Plugin Auto Update: Checking for available plugin updates Apr 10 02:00:02 Tower Plugin Auto Update: Checking for language updates Apr 10 02:00:02 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Apr 10 02:01:23 Tower emhttpd: read SMART /dev/sdo Apr 10 02:10:48 Tower emhttpd: read SMART /dev/sdl Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: veth3b723c7: renamed from eth0 Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: veth32a44e3 (unregistering): left allmulticast mode Apr 10 03:01:09 Tower kernel: veth32a44e3 (unregistering): left promiscuous mode Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered disabled state Apr 10 03:01:09 Tower kernel: veth9ff322f: entered allmulticast mode Apr 10 03:01:09 Tower kernel: veth9ff322f: entered promiscuous mode Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered forwarding state Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered disabled state Apr 10 03:01:10 Tower kernel: eth0: renamed from veth23aa3cc Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered forwarding state Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:12 Tower kernel: veth75603fc: renamed from eth0 Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:12 Tower kernel: veth510c4a0 (unregistering): left allmulticast mode Apr 10 03:01:12 Tower kernel: veth510c4a0 (unregistering): left promiscuous mode Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered blocking state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered disabled state Apr 10 03:01:13 Tower kernel: veth423eaa6: entered allmulticast mode Apr 10 03:01:13 Tower kernel: veth423eaa6: entered promiscuous mode Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered blocking state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered forwarding state Apr 10 03:01:13 Tower kernel: eth0: renamed from vethfde0f6f Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: veth676d27d: renamed from eth0 Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: veth4367e69 (unregistering): left allmulticast mode Apr 10 03:01:15 Tower kernel: veth4367e69 (unregistering): left promiscuous mode Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered blocking state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered disabled state Apr 10 03:01:15 Tower kernel: veth19c9d7d: entered allmulticast mode Apr 10 03:01:15 Tower kernel: veth19c9d7d: entered promiscuous mode Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered blocking state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered forwarding state Apr 10 03:01:15 Tower kernel: eth0: renamed from veth04889ce Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: vethab96854: renamed from eth0 Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: veth09a5ca7 (unregistering): left allmulticast mode Apr 10 03:01:18 Tower kernel: veth09a5ca7 (unregistering): left promiscuous mode Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered blocking state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered disabled state Apr 10 03:01:18 Tower kernel: veth06e02b3: entered allmulticast mode Apr 10 03:01:18 Tower kernel: veth06e02b3: entered promiscuous mode Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered blocking state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered forwarding state Apr 10 03:01:18 Tower kernel: eth0: renamed from veth69ebad8 Apr 10 03:01:20 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:20 Tower kernel: veth2feba60: renamed from eth0 Apr 10 03:01:21 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:21 Tower kernel: vethec0b410 (unregistering): left allmulticast mode Apr 10 03:01:21 Tower kernel: vethec0b410 (unregistering): left promiscuous mode Apr 10 03:01:21 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered blocking state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered disabled state Apr 10 03:01:21 Tower kernel: vethf05803a: entered allmulticast mode Apr 10 03:01:21 Tower kernel: vethf05803a: entered promiscuous mode Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered blocking state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered forwarding state Apr 10 03:01:21 Tower kernel: eth0: renamed from veth7d66b03 Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: veth2da8298: renamed from eth0 Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: vethc3acd7a (unregistering): left allmulticast mode Apr 10 03:01:24 Tower kernel: vethc3acd7a (unregistering): left promiscuous mode Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered blocking state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered disabled state Apr 10 03:01:24 Tower kernel: veth1a8aac9: entered allmulticast mode Apr 10 03:01:24 Tower kernel: veth1a8aac9: entered promiscuous mode Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered blocking state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered forwarding state Apr 10 03:01:24 Tower kernel: eth0: renamed from vethdef6b4e Apr 10 03:01:28 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:28 Tower kernel: vethb4343d5: renamed from eth0 Apr 10 03:01:29 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:29 Tower kernel: veth7378604 (unregistering): left allmulticast mode Apr 10 03:01:29 Tower kernel: veth7378604 (unregistering): left promiscuous mode Apr 10 03:01:29 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered blocking state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered disabled state Apr 10 03:01:29 Tower kernel: veth8b136f5: entered allmulticast mode Apr 10 03:01:29 Tower kernel: veth8b136f5: entered promiscuous mode Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered blocking state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered forwarding state Apr 10 03:01:29 Tower kernel: eth0: renamed from veth4f38e95 Apr 10 04:10:30 Tower emhttpd: spinning down /dev/sdh Apr 10 04:13:10 Tower emhttpd: spinning down /dev/sdg Apr 10 04:13:10 Tower emhttpd: spinning down /dev/sdf Apr 10 05:01:36 Tower emhttpd: spinning down /dev/sdo Apr 10 05:58:59 Tower emhttpd: spinning down /dev/sdl Apr 10 06:04:21 Tower emhttpd: spinning down /dev/sde Apr 10 06:40:44 Tower emhttpd: read SMART /dev/sde Apr 10 06:46:43 Tower emhttpd: spinning down /dev/sdi Apr 10 07:10:04 Tower rc.rsyslogd: Syslog server daemon... Started. tower-diagnostics-20250410-0713.zip

On unraid 7.0 and whenever I install the tailscale plug-in I lose access to the unraid gui instantly. The only option I have is to log in to the physical server, delete the plug-in files (.plg + directory), and reboot. If I try to re-install via the apps page, I end up in the same place. Ideas or help? Diagnostics attached. tower-diagnostics-20250409-1914.zip

I think you may be right. It just locked up again and I've disabled VMs for now. Attached is the log from the last lock which looks even more odd to me...lots of php-fpm messages about pool www or something. Noticed this in there, but seems to run for a bit longer after this... Feb 10 20:07:14 Tower php-fpm[9697]: [WARNING] [pool www] child 3374477 exited on signal 6 (SIGABRT) after 11.017071 seconds from start Feb 10 20:07:15 Tower php-fpm[9697]: [WARNING] [pool www] child 3374550 exited on signal 6 (SIGABRT) after 11.016988 seconds from start Feb 10 20:07:17 Tower kernel: BUG: unable to handle page fault for address: ffff880066690f18 Feb 10 20:07:17 Tower kernel: #PF: supervisor read access in kernel mode Feb 10 20:07:17 Tower kernel: #PF: error_code(0x0000) - not-present page Feb 10 20:07:17 Tower kernel: PGD 0 P4D 0 Feb 10 20:07:17 Tower kernel: Oops: 0000 [#2] PREEMPT SMP NOPTI Feb 10 20:07:17 Tower kernel: CPU: 14 PID: 3375745 Comm: lsof Tainted: P D W O 6.6.68-Unraid #1 Feb 10 20:07:17 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z790 UD AC/Z790 UD AC, BIOS F9 12/14/2023 Feb 10 20:07:17 Tower kernel: RIP: 0010:__d_lookup+0x34/0x9d Feb 10 20:07:17 Tower kernel: Code: 55 41 54 49 89 f4 55 48 89 fd 53 44 8b 36 44 89 f7 e8 ac cf ff ff 48 89 c3 e8 b2 e3 e2 ff 48 8b 1b 48 83 e3 fe 48 85 db 74 52 <44> 39 73 18 75 47 4c 8d 6b 50 4c 89 ef e8 8d 7e 77 00 48 39 6b 10 Feb 10 20:07:17 Tower kernel: RSP: 0018:ffffc90021a0fd70 EFLAGS: 00010286 Feb 10 20:07:17 Tower kernel: RAX: 0000000000000001 RBX: ffff880066690f00 RCX: 0000000000000009 Feb 10 20:07:17 Tower kernel: RDX: ffff8881cf1b9000 RSI: ffffc90021a0fdd8 RDI: 000000000073d3a9 Feb 10 20:07:17 Tower kernel: RBP: ffff888af8018a80 R08: ffffffff8131d41c R09: ffff8881b26f1000 Feb 10 20:07:17 Tower kernel: R10: 00000000ffff0a00 R11: 0000000000000000 R12: ffffc90021a0fdd8 Feb 10 20:07:17 Tower kernel: R13: ffffffff8131d41c R14: 00000000e7a752cd R15: ffff888af8018a80 Feb 10 20:07:17 Tower kernel: FS: 0000149663067f00(0000) GS:ffff88907f980000(0000) knlGS:0000000000000000 Feb 10 20:07:17 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 10 20:07:17 Tower kernel: CR2: ffff880066690f18 CR3: 0000000afbe18000 CR4: 0000000000750ee0 Feb 10 20:07:17 Tower kernel: PKRU: 55555554 Feb 10 20:07:17 Tower kernel: Call Trace: Feb 10 20:07:17 Tower kernel: <TASK> Feb 10 20:07:17 Tower kernel: ? __die_body+0x1a/0x5c Feb 10 20:07:17 Tower kernel: ? page_fault_oops+0x329/0x376 Feb 10 20:07:17 Tower kernel: ? search_bpf_extables+0x5d/0x68 Feb 10 20:07:17 Tower kernel: ? exc_page_fault+0xf2/0x116 Feb 10 20:07:17 Tower kernel: ? asm_exc_page_fault+0x22/0x30 Feb 10 20:07:17 Tower kernel: ? __pfx_proc_fd_instantiate+0x10/0x10 Feb 10 20:07:17 Tower kernel: ? __pfx_proc_fd_instantiate+0x10/0x10 Feb 10 20:07:17 Tower kernel: ? __d_lookup+0x34/0x9d Feb 10 20:07:17 Tower kernel: ? __pfx_proc_fd_instantiate+0x10/0x10 Feb 10 20:07:17 Tower kernel: d_lookup+0x21/0x39 Feb 10 20:07:17 Tower kernel: proc_fill_cache+0x5e/0x157 Feb 10 20:07:17 Tower kernel: ? __pfx_filldir64+0x10/0x10 Feb 10 20:07:17 Tower kernel: proc_readfd_common+0x178/0x1c9 Feb 10 20:07:17 Tower kernel: ? __pfx_proc_fd_instantiate+0x10/0x10 Feb 10 20:07:17 Tower kernel: iterate_dir+0x75/0x12f Feb 10 20:07:17 Tower kernel: __do_sys_getdents64+0x6b/0xd8 Feb 10 20:07:17 Tower kernel: ? __pfx_filldir64+0x10/0x10 Feb 10 20:07:17 Tower kernel: do_syscall_64+0x57/0x7b Feb 10 20:07:17 Tower kernel: entry_SYSCALL_64_after_hwframe+0x78/0xe2 Feb 10 20:07:17 Tower kernel: RIP: 0033:0x1496632d1053 Feb 10 20:07:17 Tower kernel: Code: 00 16 00 00 00 31 c0 eb c6 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 81 6d 11 00 f7 d8 Feb 10 20:07:17 Tower kernel: RSP: 002b:00007ffc43ce9848 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 Feb 10 20:07:17 Tower kernel: RAX: ffffffffffffffda RBX: 00000000004c6bd0 RCX: 00001496632d1053 Feb 10 20:07:17 Tower kernel: RDX: 0000000000008000 RSI: 00000000004c6c00 RDI: 0000000000000006 Feb 10 20:07:17 Tower kernel: RBP: 00000000004c6bd4 R08: 0000000000000000 R09: 0000000000000003 Feb 10 20:07:17 Tower kernel: R10: 00001496633e9200 R11: 0000000000000293 R12: 00000000004c6c00 Feb 10 20:07:17 Tower kernel: R13: ffffffffffffff88 R14: 0000000000000002 R15: 0000149663470000 Feb 10 20:07:17 Tower kernel: </TASK> Feb 10 20:07:17 Tower kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth 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 zfs(PO) spl(O) ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls mlx4_en mlx4_core r8169 realtek i915 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy kvm ttm i2c_algo_bit btusb drm_display_helper btrtl btbcm crct10dif_pclmul btintel crc32_pclmul crc32c_intel ghash_clmulni_intel drm_kms_helper sha512_ssse3 sha256_ssse3 Feb 10 20:07:17 Tower kernel: bluetooth sha1_ssse3 drm aesni_intel crypto_simd cryptd mei_hdcp mei_pxp intel_gtt rapl ecdh_generic input_leds led_class ecc intel_cstate gigabyte_wmi wmi_bmof mpt3sas nvme i2c_i801 mei_me agpgart i2c_smbus intel_uncore nvme_core ahci raid_class mei scsi_transport_sas i2c_core libahci tpm_crb thermal fan tpm_tis video tpm_tis_core tpm wmi backlight acpi_tad acpi_pad button [last unloaded: mlx4_core] Feb 10 20:07:17 Tower kernel: CR2: ffff880066690f18 Feb 10 20:07:17 Tower kernel: ---[ end trace 0000000000000000 ]--- Feb 10 20:07:17 Tower kernel: RIP: 0010:buffer_check_dirty_writeback+0x2b/0x4f Feb 10 20:07:17 Tower kernel: Code: 1f 44 00 00 c6 06 00 c6 02 00 48 8b 07 a8 01 75 02 0f 0b 48 8b 4f 28 48 85 c9 74 2d 48 8b 07 48 d1 e8 88 02 48 89 c8 80 22 01 <48> 8b 38 83 e7 04 74 03 c6 02 01 48 8b 38 83 e7 02 74 03 c6 06 01 Feb 10 20:07:17 Tower kernel: RSP: 0000:ffffc900049c7a80 EFLAGS: 00010217 Feb 10 20:07:17 Tower kernel: RAX: 733d5cd6b20c98b5 RBX: ffffc900049c7c28 RCX: ffff888860c237f8 Feb 10 20:07:17 Tower kernel: RDX: ffffc900049c7aac RSI: ffffc900049c7aab RDI: 0000000000000002 Feb 10 20:07:17 Tower kernel: RBP: ffffc900049c7db0 R08: 0000000000000238 R09: 000000008027001e Feb 10 20:07:17 Tower kernel: R10: 0000000000000246 R11: 0000000000000000 R12: ffffc900049c7ba0 Feb 10 20:07:17 Tower kernel: R13: 0000000000000001 R14: 0000000000000001 R15: ffffea00229719c8 Feb 10 20:07:17 Tower kernel: FS: 0000149663067f00(0000) GS:ffff88907f980000(0000) knlGS:0000000000000000 Feb 10 20:07:17 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 10 20:07:17 Tower kernel: CR2: ffff880066690f18 CR3: 0000000afbe18000 CR4: 0000000000750ee0 Feb 10 20:07:17 Tower kernel: PKRU: 55555554 Feb 10 20:07:17 Tower kernel: note: lsof[3375745] exited with irqs disabled Feb 10 20:07:17 Tower php-fpm[9697]: [WARNING] [pool www] child 3374644 exited on signal 6 (SIGABRT) after 11.017078 seconds from start Feb 10 20:07:18 Tower php-fpm[9697]: [WARNING] [pool www] child 3374745 exited on signal 6 (SIGABRT) after 11.017161 seconds from start Feb 10 20:07:19 Tower php-fpm[9697]: [WARNING] [pool www] child 3375163 exited on signal 6 (SIGABRT) after 11.017372 seconds from start syslog-192.168.1.3.log

New unraid build migrated from older system. I have had an intermittent issue where the server disappears and becomes unresponsive to everything (web UI, shares, dockers - nothing accessible). This happened late last night and I was hoping someone could look at the syslog and weight in? Below is a snippet where I believe the server went quiet at 21:42:38, then the next line is when I rebooted it. Feb 7 19:37:38 Tower kernel: Console: switching to colour dummy device 80x25 Feb 7 19:37:38 Tower acpid: input device has been disconnected, fd 11 Feb 7 19:37:39 Tower kernel: vfio-pci 0000:00:02.0: vgaarb: deactivate vga console Feb 7 19:37:39 Tower kernel: vfio-pci 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem Feb 7 19:37:39 Tower kernel: br0: port 2(vnet2) entered blocking state Feb 7 19:37:39 Tower kernel: br0: port 2(vnet2) entered disabled state Feb 7 19:37:39 Tower kernel: vnet2: entered allmulticast mode Feb 7 19:37:39 Tower kernel: vnet2: entered promiscuous mode Feb 7 19:37:39 Tower kernel: br0: port 2(vnet2) entered blocking state Feb 7 19:37:39 Tower kernel: br0: port 2(vnet2) entered forwarding state Feb 7 19:37:41 Tower kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x8d92 Feb 7 19:56:56 Tower monitor_nchan: Stop running nchan processes Feb 7 20:01:42 Tower kernel: x86/split lock detection: #AC: CPU 0/KVM/2844839 took a split_lock trap at address: 0xfffff8063ae0e1dd Feb 7 21:42:38 Tower emhttpd: spinning down /dev/sdj Feb 8 10:37:30 Tower rc.rsyslogd: Syslog server daemon... Started. syslog-192.168.1.3.log

Hmm, okay - I can create the shares, but is there anywhere I can find permissions and other settings for these missing shares? Just to try and match the standard setup as much as possible.

Hi, I'm on unraid 7.0 and noticed I'm missing some standard shares like system, domains, and isos. All I have is appdata. For context, I've been on unraid for probably 5 - 7 years, upgrading along the way. Do I need to do something to fix this? I'm also seeing an error under Settings->VM Manager that says the following path does not exist: "/mnt/user/system/libvirt/libvirt.img" . This seems related, but I'm not sure what to do. Diagnostics attached in case helpful. tower-diagnostics-20250127-2146.zip

likely in over my head, but have a CSE847 w/ gigabyte 790 and i7 12600k I just bult, pulling ~10 drives from my existing unraid server. Migration went relatively smoothly but I noticed this morning the server was unresponsive and its IP address was dark. Only option was to hard reset the serve and it came back up in safe mode, no major issues observed so I started the array, which went fine. Can someone glance at my diagnostic zip and help me figure out where to look to chase down whatever happened over night?hhg tower-diagnostics-20250106-0957.zip

I have the system booting with a trial unraid license and all comes up fine. Just not sure how to verify the system can see all the drives in the CSE-847. I have the 9305-16i connected to the front backplane. Then the other connector on the front backplane (J49?) goes to the rear backplane, with the other two connectors on the rear backplane (J3 & J4) not connected to anything. Diagnostics attached and thank you in advance. tower-diagnostics-20241229-1630.zip

Thank you sir - new drive delivered today. I’ll lookup cache drive replacement but appreciate any tips to easily swap in new one with minimal disruption!

Uncorrectable count has jumped in the last reach and now sits at ~900. Where do I go from here? Do I simply assume it is bad and replace, or should I attempt some kind of repair? Diagnostic file attached. tower-diagnostics-20240708-1306.zip