Jump to content

ColdKeyboard

Members
  • Posts

    4
  • Joined

  • Last visited

ColdKeyboard's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Ok, I ran memtest for 24h, completed 10 passes. I know I didn't give it a lot of time, but still, it reported 0 errors. (Months ago I let it run for couple of days and still had 0 errors. I didn't touch the config since then). So I think it would be reasonable to assume memory is ok. I have also attached diagnostics report from UnRaid. nas-diagnostics-20210221-0127.zip
  2. I had the same issue for the past couple of weeks. Server would crash "randomly". I disabled docker and VM (I'm not using any VMs but still). Same thing, UnRaid crashes. If I leave array stopped, server runs for days. As soon as I start the array, in the next hours or couple of days, it will crash. Last time I setup remote logging and captured that last message received mentioned "kernel BUG at mm/vmscan.c:1703!" Below is what I captured with my remote logging. Any help/suggestion on how to solve this would be greatly appreciated. 2021-02-17 05:53,Warning,192.168.0.25,CR2: 000000000044f300 CR3: 00000001d6ae2000 CR4: 00000000003406f0 2021-02-17 05:53,Warning,192.168.0.25,CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2021-02-17 05:53,Warning,192.168.0.25,FS: 0000000000000000(0000) GS:ffff888430600000(0000) knlGS:0000000000000000 2021-02-17 05:53,Warning,192.168.0.25,R13: 0000000000000000 R14: 0000000000000001 R15: 000000000000074c 2021-02-17 05:53,Warning,192.168.0.25,R10: 0000000000044268 R11: ffff8884306dfb40 R12: 0000000000000046 2021-02-17 05:53,Warning,192.168.0.25,RBP: 00000000000000e0 R08: 0000000000000000 R09: ffff8884306da5c0 2021-02-17 05:53,Warning,192.168.0.25,RDX: 0000000000000001 RSI: 0000000000000003 RDI: 000000000000074c 2021-02-17 05:53,Warning,192.168.0.25,RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff81e3ca80 2021-02-17 05:53,Warning,192.168.0.25,RSP: 0018:ffffc90001933e20 EFLAGS: 00010046 2021-02-17 05:53,Warning,192.168.0.25,Code: 89 f8 48 89 f7 c6 00 00 57 9d 0f 1f 44 00 00 c3 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 <f0> 0f b1 17 85 c0 74 09 89 c6 e8 16 d1 9f ff 66 90 4c 89 e0 41 5c 2021-02-17 05:53,Warning,192.168.0.25,RIP: 0010:_raw_spin_lock_irqsave+0x1a/0x31 2021-02-17 05:53,Warning,192.168.0.25,---[ end trace 575c6c2f1f88a641 ]--- 2021-02-17 05:53,Warning,192.168.0.25,Modules linked in: xt_nat veth ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod bonding edac_mce_amd ccp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd i2c_piix4 i2c_core r8169 video ahci k10temp backlight glue_helper libahci nvme realtek wmi_bmof nvme_core wmi thermal button pcc_cpufreq acpi_cpufreq 2021-02-17 05:53,Warning,192.168.0.25,ret_from_fork+0x22/0x40 2021-02-17 05:53,Warning,192.168.0.25,? kthread_park+0x89/0x89 2021-02-17 05:53,Warning,192.168.0.25,kthread+0x10c/0x114 2021-02-17 05:53,Warning,192.168.0.25,? mem_cgroup_shrink_node+0xa4/0xa4 2021-02-17 05:53,Warning,192.168.0.25,? __switch_to_asm+0x41/0x70 2021-02-17 05:53,Warning,192.168.0.25,kswapd+0x451/0x58a 2021-02-17 05:53,Warning,192.168.0.25,shrink_node+0xf1/0x3cb 2021-02-17 05:53,Warning,192.168.0.25,? super_cache_count+0x70/0xb4 2021-02-17 05:53,Warning,192.168.0.25,? xfs_fs_nr_cached_objects+0x16/0x19 [xfs] 2021-02-17 05:53,Warning,192.168.0.25,shrink_node_memcg+0x4c4/0x64a 2021-02-17 05:53,Warning,192.168.0.25,shrink_inactive_list+0xd8/0x47e 2021-02-17 05:53,Warning,192.168.0.25,Call Trace: 2021-02-17 05:53,Warning,192.168.0.25,CR2: 000000000044f300 CR3: 00000001d6ae2000 CR4: 00000000003406f0 2021-02-17 05:53,Warning,192.168.0.25,CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2021-02-17 05:53,Warning,192.168.0.25,FS: 0000000000000000(0000) GS:ffff888430600000(0000) knlGS:0000000000000000 2021-02-17 05:53,Warning,192.168.0.25,R13: ffff88818f48bc00 R14: 0000000000000002 R15: 0000000000000002 2021-02-17 05:53,Warning,192.168.0.25,R10: ffffc90001d0bc58 R11: 0000000000000003 R12: 0000000000000002 2021-02-17 05:53,Warning,192.168.0.25,RBP: ffff88818f48bc20 R08: ffffc90001d0bea3 R09: 0000000000000000 2021-02-17 05:53,Warning,192.168.0.25,RDX: ffffc90001d0bc60 RSI: 0000000000000000 RDI: ffffea000d70c6c0 2021-02-17 05:53,Warning,192.168.0.25,RAX: 00000000ffffffea RBX: ffffea000d70c6c8 RCX: ffffc90001d0bba0 2021-02-17 05:53,Warning,192.168.0.25,RSP: 0018:ffffc90001d0bb70 EFLAGS: 00010082 2021-02-17 05:53,Warning,192.168.0.25,Code: 53 08 48 89 1a eb 25 48 8b 43 08 48 8b 3b 48 89 47 08 48 89 38 48 8b 45 00 48 89 58 08 48 89 03 48 89 6b 08 48 89 5d 00 eb 02 <0f> 0b 49 ff c7 4c 89 d8 4d 39 dc 49 0f 43 c4 48 3b 04 24 0f 82 cb 2021-02-17 05:53,Warning,192.168.0.25,RIP: 0010:isolate_lru_pages.isra.0+0x18b/0x2b9 2021-02-17 05:53,Warning,192.168.0.25,Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F60c 10/29/2020 2021-02-17 05:53,Warning,192.168.0.25,CPU: 0 PID: 786 Comm: kswapd0 Tainted: G D 4.19.107-Unraid #1 2021-02-17 05:53,Warning,192.168.0.25,invalid opcode: 0000 [#2] SMP NOPTI 2021-02-17 05:53,Critical,192.168.0.25,kernel BUG at mm/vmscan.c:1703! 2021-02-17 05:53,Warning,192.168.0.25,------------[ cut here ]------------ 2021-02-17 05:53,Info,192.168.0.25,oom_reaper: reaped process 28849 (shfs), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB 2021-02-17 05:53,Error,192.168.0.25,Killed process 28849 (shfs) total-vm:483680kB, anon-rss:21368kB, file-rss:4kB, shmem-rss:1064kB 2021-02-17 05:53,Error,192.168.0.25,Out of memory: Kill process 28849 (shfs) score 1 or sacrifice child
  3. I'm new to UnRaid and just recently got everything up and running. So I'm a complete newbie and have zero experience in debugging UnRaid issues. Last month, I've been experiencing intermittent crashes, where server becomes completely unresponsive (web, ssh and hdmi out) and I have to restart it. I tried running mem test for overnight (~10+ hrs) and had 0 problems. Last time this happened, I've removed all plugins that I had (ssd trim, ssd folder caching etc.) and basically now I'm running Docker only. However, the issue is still not resolved. Interesting thing is that when start the array, after ~12hrs parity check is complete. My configuration is: Gigabyte Technology Co., Ltd. B450M DS3H-CF, Version x.x American Megatrends Inc., Version F51f BIOS dated: Thu 02 Jul 2020 12:00:00 AM EDT AMD Ryzen 5 2400G with Radeon Vega Graphics @ 3600 MHz 16 GiB DDR4 Any suggestions what should I try or what information should I collect and post here so I can figure out what is going on wrong? nas-diagnostics-20200821-2317.zip
×
×
  • Create New...