Hello,

my unraid instance does nearly daily report this (example) in the log and after that the docker service is acting weird (crashes some times) and a normal reboot is not possible. Only pulling the power plug is the option. 

 

Thinks I already tested:

• Update to 6.7Rc7
• MemTest 
• only using 1 Ram Module
• removed cache drive

 

My Hardware:

ASRock J3455-ITX

16GB Ram

2 * 3TB HDD (seagate + Toshiba)

 

Docker Container running:

• Nextcloud + Maria DB
• Let's Encrypt (nginx)
• Pihole

 

Hopefully anyone can help.

 

Greetings

 

Apr 20 09:30:01 nas kernel: BUG: unable to handle kernel paging request at ffff88866ff1cc00
Apr 20 09:30:01 nas kernel: PGD 2401067 P4D 2401067 PUD 0 
Apr 20 09:30:01 nas kernel: Oops: 0000 [#1] SMP NOPTI
Apr 20 09:30:01 nas kernel: CPU: 2 PID: 5219 Comm: php7 Not tainted 4.19.33-Unraid #1
Apr 20 09:30:01 nas kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018
Apr 20 09:30:01 nas kernel: RIP: 0010:lock_hrtimer_base.isra.1+0x17/0x40
Apr 20 09:30:01 nas kernel: Code: 00 00 00 48 85 c0 74 08 48 89 c7 e8 56 e7 fc ff 31 c0 c3 41 54 49 89 f4 55 48 89 fd 53 48 8b 5d 00 48 81 fb 40 ef e3 81 74 1d <48> 8b 3b e8 c0 1b 5b 00 49 89 04 24 48 3b 5d 00 74 0f 48 8b 3b 48
Apr 20 09:30:01 nas kernel: RSP: 0018:ffffc90001dcbc00 EFLAGS: 00010287
Apr 20 09:30:01 nas kernel: RAX: 0000000000000000 RBX: ffff88866ff1cc00 RCX: 0000000000000006
Apr 20 09:30:01 nas kernel: RDX: 0000000000000000 RSI: ffffc90001dcbc30 RDI: ffff888404fac268
Apr 20 09:30:01 nas kernel: RBP: ffff888404fac268 R08: 00000000000005a8 R09: 000000000002cd80
Apr 20 09:30:01 nas kernel: R10: 00000000000163ec R11: 000000000002c7d8 R12: ffffc90001dcbc30
Apr 20 09:30:01 nas kernel: R13: 0000000000000000 R14: 000000000001cac0 R15: 0000000000000006
Apr 20 09:30:01 nas kernel: FS:  000014a6ff721b68(0000) GS:ffff88846ff00000(0000) knlGS:0000000000000000
Apr 20 09:30:01 nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00 CR3: 00000003cf744000 CR4: 00000000003406e0
Apr 20 09:30:01 nas kernel: Call Trace:
Apr 20 09:30:01 nas kernel: hrtimer_start_range_ns+0x57/0x1e2
Apr 20 09:30:01 nas kernel: ? get_nohz_timer_target+0x1b/0xe8
Apr 20 09:30:01 nas kernel: __tcp_transmit_skb+0x7de/0x912
Apr 20 09:30:01 nas kernel: tcp_write_xmit+0x979/0xd64
Apr 20 09:30:01 nas kernel: __tcp_push_pending_frames+0x2b/0x90
Apr 20 09:30:01 nas kernel: tcp_sendmsg_locked+0x9d7/0xb2e
Apr 20 09:30:01 nas kernel: tcp_sendmsg+0x23/0x35
Apr 20 09:30:01 nas kernel: sock_sendmsg+0x14/0x1e
Apr 20 09:30:01 nas kernel: __sys_sendto+0xcc/0x10a
Apr 20 09:30:01 nas kernel: ? fuse_file_put+0x81/0x8e
Apr 20 09:30:01 nas kernel: ? syscall_trace_enter+0x164/0x1a3
Apr 20 09:30:01 nas kernel: __x64_sys_sendto+0x1f/0x22
Apr 20 09:30:01 nas kernel: do_syscall_64+0x57/0xe6
Apr 20 09:30:01 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 20 09:30:01 nas kernel: RIP: 0033:0x14a6ff6e43ad
Apr 20 09:30:01 nas kernel: Code: c3 8b 07 85 c0 75 24 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> e9 50 d7 ff ff 41 57 41 56 41 55 41 54 49 89 f4 55 53 48 89 fb
Apr 20 09:30:01 nas kernel: RSP: 002b:00007fff21f32df8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
Apr 20 09:30:01 nas kernel: RAX: ffffffffffffffda RBX: 000014a6ff721b68 RCX: 000014a6ff6e43ad
Apr 20 09:30:01 nas kernel: RDX: 000000000000008f RSI: 000014a6ff2b6000 RDI: 0000000000000004
Apr 20 09:30:01 nas kernel: RBP: 000000000000002c R08: 0000000000000000 R09: 0000000000000000
Apr 20 09:30:01 nas kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 000014a6ff2a6380
Apr 20 09:30:01 nas kernel: R13: 000000000000008f R14: 000014a6ff3d9828 R15: 000014a6ff2b6000
Apr 20 09:30:01 nas kernel: Modules linked in: veth macvlan xt_nat ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding x86_pkg_temp_thermal intel_powerclamp coretemp hid_logitech_hidpp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf r8169 i2c_i801 i2c_core hid_logitech_dj realtek ahci video libahci backlight thermal fan button pcc_cpufreq
Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00
Apr 20 09:30:01 nas kernel: ---[ end trace f451f71b78ac40df ]---
Apr 20 09:30:01 nas kernel: RIP: 0010:lock_hrtimer_base.isra.1+0x17/0x40
Apr 20 09:30:01 nas kernel: Code: 00 00 00 48 85 c0 74 08 48 89 c7 e8 56 e7 fc ff 31 c0 c3 41 54 49 89 f4 55 48 89 fd 53 48 8b 5d 00 48 81 fb 40 ef e3 81 74 1d <48> 8b 3b e8 c0 1b 5b 00 49 89 04 24 48 3b 5d 00 74 0f 48 8b 3b 48
Apr 20 09:30:01 nas kernel: RSP: 0018:ffffc90001dcbc00 EFLAGS: 00010287
Apr 20 09:30:01 nas kernel: RAX: 0000000000000000 RBX: ffff88866ff1cc00 RCX: 0000000000000006
Apr 20 09:30:01 nas kernel: RDX: 0000000000000000 RSI: ffffc90001dcbc30 RDI: ffff888404fac268
Apr 20 09:30:01 nas kernel: RBP: ffff888404fac268 R08: 00000000000005a8 R09: 000000000002cd80
Apr 20 09:30:01 nas kernel: R10: 00000000000163ec R11: 000000000002c7d8 R12: ffffc90001dcbc30
Apr 20 09:30:01 nas kernel: R13: 0000000000000000 R14: 000000000001cac0 R15: 0000000000000006
Apr 20 09:30:01 nas kernel: FS:  000014a6ff721b68(0000) GS:ffff88846ff00000(0000) knlGS:0000000000000000
Apr 20 09:30:01 nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00 CR3: 00000003cf744000 CR4: 00000000003406e0

Edited May 2, 20197 yr by mhlnstdt25

Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your next post. 

Sorry missed that!

nas-diagnostics-20190420-2224.zip

You have allocated 50G to your docker image. It isn't currently using much of that, but such a large docker image often is a sign that the user has been filling docker image and so they have increased its size. That won't fix anything, it will just make it take longer to fill. If you have all your docker applications setup correctly it is extremely unlikely you would ever need even 20G.

 

I didn't notice anything in syslog that would lead me to believe docker image is corrupt though, so that might not have anything to do with your issue. Still, I recommend deleting and recreating docker image at 20G, then reinstalling your dockers using the Previous Apps feature on the Apps page.

 

Maybe it will help your issue, maybe it won't, but you will be better off either way without so much wasted space for docker image with such a small cache. And, if it turns out you are filling docker image, making it smaller will be a way to find out sooner rather than later that you have something setup wrong.

 

Also, your appdata and system shares have some data on the array. While you have that docker image deleted, you should run mover to get those shares moved to cache where they belong.

 

Possibly none of these recommendations will be a fix for the dump you posted, but you will be better off for them anyway.

 

If none of this makes a difference to the problem, you might try simplifying some things to try to isolate the problem. It looks like you were only running one docker at the time the diagnostics were taken. Do you sometimes run more? Does the problem happen when you aren't running certain dockers? Etc.

Thanks for the tips, but that didn't help me to fix my problem.

I replaced all S-ATA Data cables and that seems to fix the problems.