September 5, 20232 yr I am running unraid 6.12.3 and had a crash this morning, I have logging turned on and tried to make sense of them but i'm not really sure what im looking for, will attach the logs here, It seems the important part starts around this morning (Sept 5th) at 7:53 AM syslog-192.168.1.8.log
September 6, 20232 yr Author After some googling I have found some more info on this, when Unraid crashed my internet also went down but I didn't know until a couple hours later so I assumed these were unrelated problems that just happened to occur over night, but i've found another post on this forum that seems very similar in these 2 posts https://forums.unraid.net/topic/139518-unraid-crashes-and-brings-down-router-with-it/#comment-1266902 https://forums.unraid.net/topic/140861-unraid-crashes-when-starting-the-array/#comment-1277692 it seems that for them the problem was a faulty NVME drive, this is the first time this has happened to me so i'm not really sure if its worth changing out hardware quite yet. if anyone has any more information i'd love to hear it but I guess the best option for now is probably just to wait and see if it happens again.
September 6, 20232 yr Community Expert Lot of call traces in the log, looks more hardware related, one thing you can try is to boot the server in safe mode with all docker/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.
September 6, 20232 yr Author I've been using unraid for 2 months and this is the first time it has happened so I'm not sure running as a NAS for just a few days would be sufficient to know if its a hardware issue or not. you say there are a lot of callbacks, can you give an example of what this means? if this can indicate a hardware problem my guess would be that it is RAM related since that is the only part in the system that I reused from an old system and it has some old unmatched ram sticks, would that make sense with these types of errors? I don't mind ordering some new ram to stick in there and see if it solves things.
September 6, 20232 yr Community Expert Solution 2 minutes ago, ggfools said: I've been using unraid for 2 months and this is the first time it has happened I would then suggest waiting to see if it happens again, it might have been a one time thing. 3 minutes ago, ggfools said: you say there are a lot of callbacks, can you give an example of what this means? Like this: Aug 25 18:55:16 Earth kernel: BUG: unable to handle page fault for address: 0000000000004000 Aug 25 18:55:16 Earth kernel: #PF: supervisor read access in kernel mode Aug 25 18:55:16 Earth kernel: #PF: error_code(0x0000) - not-present page Aug 25 18:55:16 Earth kernel: PGD 257844067 P4D 257844067 PUD 41ee57067 PMD 0 Aug 25 18:55:16 Earth kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Aug 25 18:55:16 Earth kernel: CPU: 0 PID: 3562 Comm: lsof Tainted: P O 6.1.38-Unraid #2 Aug 25 18:55:16 Earth kernel: Hardware name: To Be Filled By O.E.M. Z690 Pro RS/Z690 Pro RS, BIOS 8.01 03/28/2022 Aug 25 18:55:16 Earth kernel: RIP: 0010:__destroy_inode+0x2c/0xf2 Aug 25 18:55:16 Earth kernel: Code: 44 00 00 55 53 48 89 fb e8 b8 fd 01 00 85 c0 74 02 0f 0b 48 8b ab f0 00 00 00 48 85 ed 74 6a f6 83 90 00 00 00 40 75 02 0f 0b <48> 8b 45 00 48 85 c0 75 04 0f 0b eb 49 48 83 c0 60 48 39 c5 74 40 Aug 25 18:55:16 Earth kernel: RSP: 0018:ffffc900321477f8 EFLAGS: 00010202 Aug 25 18:55:16 Earth kernel: RAX: 0000000000000000 RBX: ffff8885e6521318 RCX: 0000000000000000 Aug 25 18:55:16 Earth kernel: RDX: ffff8885e6521418 RSI: ffff8885e65213a8 RDI: ffff8885e6521530 Aug 25 18:55:16 Earth kernel: RBP: 0000000000004000 R08: ffffffff82206678 R09: 00000000000002d2 Aug 25 18:55:16 Earth kernel: R10: ffff88834f591940 R11: 000000000000086d R12: ffff88833ea16d18 Aug 25 18:55:16 Earth kernel: R13: ffff88833ea16d18 R14: 0000000000000000 R15: 0000000000000000 Aug 25 18:55:16 Earth kernel: FS: 000015126a1ffe00(0000) GS:ffff88886f400000(0000) knlGS:0000000000000000 Aug 25 18:55:16 Earth kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 25 18:55:16 Earth kernel: CR2: 0000000000004000 CR3: 00000001636c8000 CR4: 0000000000750ef0 Aug 25 18:55:16 Earth kernel: PKRU: 55555554 Aug 25 18:55:16 Earth kernel: Call Trace: Aug 25 18:55:16 Earth kernel: <TASK> Aug 25 18:55:16 Earth kernel: ? __die_body+0x1a/0x5c Aug 25 18:55:16 Earth kernel: ? page_fault_oops+0x329/0x376 Aug 25 18:55:16 Earth kernel: ? do_user_addr_fault+0x12e/0x48d Aug 25 18:55:16 Earth kernel: ? exc_page_fault+0xfb/0x11d Aug 25 18:55:16 Earth kernel: ? asm_exc_page_fault+0x22/0x30 Aug 25 18:55:16 Earth kernel: ? __destroy_inode+0x2c/0xf2 Aug 25 18:55:16 Earth kernel: ? __destroy_inode+0xf/0xf2 Aug 25 18:55:16 Earth kernel: destroy_inode+0x2c/0x6b Aug 25 18:55:16 Earth kernel: __dentry_kill+0xcb/0x131 Aug 25 18:55:16 Earth kernel: shrink_dentry_list+0xaa/0xba Aug 25 18:55:16 Earth kernel: prune_dcache_sb+0x51/0x73 Aug 25 18:55:16 Earth kernel: super_cache_scan+0xf4/0x17c Aug 25 18:55:16 Earth kernel: do_shrink_slab+0x188/0x2a1 Aug 25 18:55:16 Earth kernel: shrink_slab+0x1f9/0x267 Aug 25 18:55:16 Earth kernel: shrink_node+0x318/0x549 Aug 25 18:55:16 Earth kernel: do_try_to_free_pages+0x1b1/0x3a7 Aug 25 18:55:16 Earth kernel: try_to_free_pages+0x102/0x181 Aug 25 18:55:16 Earth kernel: __alloc_pages_slowpath.constprop.0+0x26b/0x8f8 Aug 25 18:55:16 Earth kernel: ? insert_vmap_area_augment.constprop.0+0x124/0x187 Aug 25 18:55:16 Earth kernel: ? preempt_latency_start+0x2b/0x46 Aug 25 18:55:16 Earth kernel: ? alloc_vmap_area+0x5ce/0x689 Aug 25 18:55:16 Earth kernel: __alloc_pages+0x132/0x1e8 Aug 25 18:55:16 Earth kernel: __vmalloc_node_range+0x384/0x5ea Aug 25 18:55:16 Earth kernel: ? seq_read_iter+0x1d5/0x346 Aug 25 18:55:16 Earth kernel: kvmalloc_node+0xae/0xbc Aug 25 18:55:16 Earth kernel: ? seq_read_iter+0x1d5/0x346 Aug 25 18:55:16 Earth kernel: seq_read_iter+0x1d5/0x346 Aug 25 18:55:16 Earth kernel: ? slab_post_alloc_hook+0x4d/0x15e Aug 25 18:55:16 Earth kernel: seq_read+0x92/0xbc Aug 25 18:55:16 Earth kernel: vfs_read+0xa4/0x19f Aug 25 18:55:16 Earth kernel: ? __do_sys_newfstatat+0x35/0x5c Aug 25 18:55:16 Earth kernel: ksys_read+0x76/0xc2 Aug 25 18:55:16 Earth kernel: do_syscall_64+0x68/0x81 Aug 25 18:55:16 Earth kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Aug 25 18:55:16 Earth kernel: RIP: 0033:0x15126a489afd Aug 25 18:55:16 Earth kernel: Code: 31 c0 e9 e6 fe ff ff 50 48 8d 3d 36 a1 0a 00 e8 49 15 02 00 66 0f 1f 84 00 00 00 00 00 80 3d e1 ca 0e 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 Aug 25 18:55:16 Earth kernel: RSP: 002b:00007ffdca7611b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Aug 25 18:55:16 Earth kernel: RAX: ffffffffffffffda RBX: 00000000004362c0 RCX: 000015126a489afd Aug 25 18:55:16 Earth kernel: RDX: 0000000000000400 RSI: 000000000043fde0 RDI: 0000000000000005 Aug 25 18:55:16 Earth kernel: RBP: 000015126a56b600 R08: 0000000000000001 R09: 0000000000000000 Aug 25 18:55:16 Earth kernel: R10: 0000000000001000 R11: 0000000000000246 R12: 000000000000000a Aug 25 18:55:16 Earth kernel: R13: 0000000000000a68 R14: 000015126a56ad00 R15: 0000000000000a68 Aug 25 18:55:16 Earth kernel: </TASK> Aug 25 18:55:16 Earth kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs xt_MASQUERADE xt_mark iptable_nat ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tun md_mod tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls zfs(PO) i915 zunicode(PO) zzstd(O) zlua(O) zavl(PO) intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal icp(PO) intel_powerclamp coretemp iosf_mbi drm_buddy i2c_algo_bit kvm_intel ttm drm_display_helper zcommon(PO) kvm znvpair(PO) drm_kms_helper spl(O) drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd mei_hdcp mei_pxp intel_gtt cryptd rapl intel_cstate wmi_bmof intel_uncore mpt3sas tpm_crb i2c_i801 agpgart tpm_tis nvme video mei_me tpm_tis_core i2c_smbus ahci Aug 25 18:55:16 Earth kernel: syscopyarea input_leds r8169 raid_class sysfillrect sysimgblt nvme_core i2c_core mei led_class libahci joydev scsi_transport_sas realtek wmi vmd fb_sys_fops backlight tpm intel_pmc_core acpi_pad acpi_tad button unix Aug 25 18:55:16 Earth kernel: CR2: 0000000000004000 Aug 25 18:55:16 Earth kernel: ---[ end trace 0000000000000000 ]--- It means some error or some app crashed, these are not always hardware related, but when there are multiple seemingly unrelated call traces it can be. You can run memtest before replacing the RAM, but like mentioned I would wait for another crash.
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.