Jump to content
SpyKiIIer

6.6.6/6.7.0 - System Kernal Panic One Parity Drive Swap

8 posts in this topic Last Reply

Recommended Posts

Hello All,

 

I was running 6.6.6, and have updated to 6.7.0, and both versions have the same issue.  Most of my drives are 3/4TB drives, and one of my 4TB drives died.  I am trying to do the swap method to change the 4TB parity disk to a replacement for the 4tb that died, and make a new 8TB drive the new parity disk.  When I check the checkbox to start the process I see errors in the system logs, and then the system becomes unresponsive, requiring a physical restart to get access again.  Is there anything that can be done to fix this, or do I need to buy drives and copy all my content off, and remake the raid (not preferable).

 

Jun 15 10:31:28 Tower emhttpd: import 30 cache device: (sdk) Samsung_SSD_850_EVO_250GB_S2R5NXAH242308D
Jun 15 10:31:28 Tower emhttpd: import flash device: sda
Jun 15 10:31:53 Tower emhttpd: req (4): startState=SWAP_DSBL&file=&cmdCopy=Copy&confirmStart=OFF&csrf_token=****************
Jun 15 10:31:55 Tower emhttpd: copy: disk5 to disk0 running
Jun 15 10:31:58 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
Jun 15 10:31:58 Tower kernel: PGD 800000040ac10067 P4D 800000040ac10067 PUD 40a49d067 PMD 0
Jun 15 10:31:58 Tower kernel: Oops: 0000 [#1] SMP PTI
Jun 15 10:31:58 Tower kernel: CPU: 1 PID: 8380 Comm: emhttpd Not tainted 4.19.41-Unraid #1
Jun 15 10:31:58 Tower kernel: Hardware name: ASUS All Series/H87I-PLUS, BIOS 2003 11/05/2014
Jun 15 10:31:58 Tower kernel: RIP: 0010:find_get_entry.part.9+0x36/0x98
Jun 15 10:31:58 Tower kernel: Code: 48 89 df e8 63 41 56 00 48 85 c0 48 89 c1 74 76 48 8b 10 48 85 d2 74 6c 48 89 d0 83 e0 03 74 0a 48 ff c8 74 d8 48 89 d1 eb 5c <48> 8b 42 08 48 89 d7 a8 01 74 04 48 8d 78 ff 8b 47 34 85 c0 74 bd
Jun 15 10:31:58 Tower kernel: RSP: 0018:ffffc90001ff3d70 EFLAGS: 00010246
Jun 15 10:31:58 Tower kernel: RAX: 0000000000000000 RBX: ffff88840f046fc8 RCX: ffff8883967bbc48
Jun 15 10:31:58 Tower kernel: RDX: 0000000000000040 RSI: ffffc90001ff3d28 RDI: ffff8883967bbb50
Jun 15 10:31:58 Tower kernel: RBP: 000000000002109a R08: ffff8883967bbc48 R09: ffff8883967bbb50
Jun 15 10:31:58 Tower kernel: R10: ffffc90001ff3d58 R11: 0000000000000000 R12: 0000000000000000
Jun 15 10:31:58 Tower kernel: R13: ffff88840f046fc0 R14: 000000000002109a R15: ffffffff81e45880
Jun 15 10:31:58 Tower kernel: FS: 00001469d3b1e700(0000) GS:ffff88840f880000(0000) knlGS:0000000000000000
Jun 15 10:31:58 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 15 10:31:58 Tower kernel: CR2: 0000000000000048 CR3: 000000040b83c004 CR4: 00000000001606e0
Jun 15 10:31:58 Tower kernel: Call Trace:
Jun 15 10:31:58 Tower kernel: pagecache_get_page+0x29/0x1d0
Jun 15 10:31:58 Tower kernel: generic_file_read_iter+0x1b4/0x6c8
Jun 15 10:31:58 Tower kernel: __vfs_read+0xfc/0x134
Jun 15 10:31:58 Tower kernel: vfs_read+0xa1/0x122
Jun 15 10:31:58 Tower kernel: ksys_read+0x60/0xb4
Jun 15 10:31:58 Tower kernel: do_syscall_64+0x57/0xe6
Jun 15 10:31:58 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 15 10:31:58 Tower kernel: RIP: 0033:0x1469d4b0a974
Jun 15 10:31:58 Tower kernel: Code: 84 00 00 00 00 00 41 54 49 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 7b fc ff ff 4c 89 e2 48 89 ee 89 df 41 89 c0 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 b7 fc ff ff 48
Jun 15 10:31:58 Tower kernel: RSP: 002b:00001469d3b1ddd0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Jun 15 10:31:58 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00001469d4b0a974
Jun 15 10:31:58 Tower kernel: RDX: 0000000000080000 RSI: 00001469d389d010 RDI: 0000000000000009
Jun 15 10:31:58 Tower kernel: RBP: 00001469d389d010 R08: 0000000000000000 R09: 0000000000000000
Jun 15 10:31:58 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080000
Jun 15 10:31:58 Tower kernel: R13: 00007ffc399bf5bf R14: 00001469d3b1e700 R15: 0000000000000000
Jun 15 10:31:58 Tower kernel: Modules linked in: md_mod bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd hid_logitech_hidpp glue_helper i2c_i801 i2c_core wmi_bmof e1000e intel_cstate intel_uncore hid_logitech_dj intel_rapl_perf wmi fan video thermal button ahci backlight libahci pcc_cpufreq [last unloaded: md_mod]
Jun 15 10:31:58 Tower kernel: CR2: 0000000000000048
Jun 15 10:31:58 Tower kernel: ---[ end trace 336c9dd942f47f5d ]---
Jun 15 10:31:58 Tower kernel: RIP: 0010:find_get_entry.part.9+0x36/0x98
Jun 15 10:31:58 Tower kernel: Code: 48 89 df e8 63 41 56 00 48 85 c0 48 89 c1 74 76 48 8b 10 48 85 d2 74 6c 48 89 d0 83 e0 03 74 0a 48 ff c8 74 d8 48 89 d1 eb 5c <48> 8b 42 08 48 89 d7 a8 01 74 04 48 8d 78 ff 8b 47 34 85 c0 74 bd
Jun 15 10:31:58 Tower kernel: RSP: 0018:ffffc90001ff3d70 EFLAGS: 00010246
Jun 15 10:31:58 Tower kernel: RAX: 0000000000000000 RBX: ffff88840f046fc8 RCX: ffff8883967bbc48
Jun 15 10:31:58 Tower kernel: RDX: 0000000000000040 RSI: ffffc90001ff3d28 RDI: ffff8883967bbb50
Jun 15 10:31:58 Tower kernel: RBP: 000000000002109a R08: ffff8883967bbc48 R09: ffff8883967bbb50
Jun 15 10:31:58 Tower kernel: R10: ffffc90001ff3d58 R11: 0000000000000000 R12: 0000000000000000
Jun 15 10:31:58 Tower kernel: R13: ffff88840f046fc0 R14: 000000000002109a R15: ffffffff81e45880
Jun 15 10:31:58 Tower kernel: FS: 00001469d3b1e700(0000) GS:ffff88840f880000(0000) knlGS:0000000000000000
Jun 15 10:31:58 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 15 10:31:58 Tower kernel: CR2: 0000000000000048 CR3: 000000040b83c004 CR4: 00000000001606e0

 

Thanks for any help.

Edited by SpyKiIIer

Share this post


Link to post
On 6/15/2019 at 6:51 PM, trurl said:

Have you done a memtest recently?

I ran the memtest and it showed that there was a bunch of errors with the memory.  I have ordered replacement memory from Amazon and will swap it out and try again.

Share this post


Link to post
5 minutes ago, SpyKiIIer said:

I ran the memtest and it showed that there was a bunch of errors with the memory.  I have ordered replacement memory from Amazon and will swap it out and try again.

Sometime you get errors just because the memory modules are not seated properly.  Always worth checking for.

Share this post


Link to post
9 hours ago, itimpi said:

Sometime you get errors just because the memory modules are not seated properly.  Always worth checking for.

And don't use your server AT ALL until memory problems are fixed.

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.