February 27, 20215 yr after hard reset, unraid keep crashing when doing parity check. i try do parity check in safe mode and maintain mode, still no luck. here the logs and diagnostics. what should i try next? please help. Feb 27 19:17:12 Tower kernel: CPU: 14 PID: 4309 Comm: unraidd0 Tainted: G O 5.10.1-Unraid #1 Feb 27 19:17:12 Tower kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH II EXTREME, BIOS 0503 10/25/2019 Feb 27 19:17:12 Tower kernel: RIP: 0010:blk_throtl_bio+0x29/0x4cc Feb 27 19:17:12 Tower kernel: Code: ff 41 57 41 56 41 55 41 54 55 53 48 89 fb 48 83 ec 38 48 8b 47 08 48 8b 7f 48 4c 8b a8 a8 03 00 00 e8 ac db ff ff 44 8b 63 10 <48> 8b 68 28 80 7b 14 00 79 08 45 31 e4 e9 41 04 00 00 49 89 c6 e9 Feb 27 19:17:12 Tower kernel: RSP: 0018:ffffc900022afca0 EFLAGS: 00010246 Feb 27 19:17:12 Tower kernel: RAX: 0000000000000000 RBX: ffff88816681eeb0 RCX: 0000000000000000 Feb 27 19:17:12 Tower kernel: RDX: 0000000000000000 RSI: 000000048c400000 RDI: 0000000000000000 Feb 27 19:17:12 Tower kernel: RBP: ffff88816681eeb0 R08: ffff88816681eeb0 R09: ffff8881535907c0 Feb 27 19:17:12 Tower kernel: R10: 0000000000000000 R11: 00000000fffffffd R12: 0000000000000000 Feb 27 19:17:12 Tower kernel: R13: ffff888149908000 R14: ffff88816681eeb0 R15: ffff88815aec5628 Feb 27 19:17:12 Tower kernel: FS: 0000000000000000(0000) GS:ffff88bf3d380000(0000) knlGS:0000000000000000 Feb 27 19:17:12 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 27 19:17:12 Tower kernel: CR2: 0000000000000028 CR3: 000000015ac3a000 CR4: 0000000000350ee0 Feb 27 19:17:12 Tower kernel: Call Trace: Feb 27 19:17:12 Tower kernel: ? blk_mq_submit_bio+0x32c/0x351 Feb 27 19:17:12 Tower kernel: submit_bio_checks+0x1b2/0x1f6 Feb 27 19:17:12 Tower kernel: submit_bio_noacct+0x2d/0x256 Feb 27 19:17:12 Tower kernel: ? bio_associate_blkg_from_css+0x138/0x15d Feb 27 19:17:12 Tower kernel: unraidd+0x120f/0x12b7 [md_mod] Feb 27 19:17:12 Tower kernel: ? md_thread+0xee/0x115 [md_mod] Feb 27 19:17:12 Tower kernel: ? __kthread_should_park+0x5/0x10 Feb 27 19:17:12 Tower kernel: md_thread+0xee/0x115 [md_mod] Feb 27 19:17:12 Tower kernel: ? init_wait_entry+0x24/0x24 Feb 27 19:17:12 Tower kernel: ? md_seq_show+0x69e/0x69e [md_mod] Feb 27 19:17:12 Tower kernel: kthread+0xe5/0xea Feb 27 19:17:12 Tower kernel: ? kthread_unpark+0x52/0x52 Feb 27 19:17:12 Tower kernel: ret_from_fork+0x22/0x30 tower-diagnostics-20210227-1917.zip
February 27, 20215 yr Author Thanks, trurl. Setting "Global C-state Control" to "disabled" from BIOS fix this issue.
Archived
This topic is now archived and is closed to further replies.