July 4, 20233 yr Due to broken parity on both of my drives (hard crash during parity check) I rebuilt parity on both of my parity drives. After the rebuilds had finished I ran a non-correcting check and it was stuck at 0 errors, less than one minute remaining for 24 hours. I used the web GUI to reboot and now it rebooted with a kernel panic error. I have attached a photo of the error for those who might understand it better than me. Is there anything I should do to fix the parity check and kernel panic ie just reboot, new flash drive etc? I have left it in this state because I did not know if I should try and get logs (if that is even possible) before rebooting. Edit: Attached syslog in below comment now that I know it was accessible from this state Edited July 4, 20233 yr by AngryPig
July 4, 20233 yr Community Expert You can enable the syslog server and post that if it happens again.
July 4, 20233 yr Author Just now, JorgeB said: You can enable the syslog server and post that if it happens again. I have syslog set to write to flash. Would it be accessible if I hard shutdown and pulled the USB or would it be wiped because of the panic? I thought I read that it was wiped at each reboot
July 4, 20233 yr Community Expert 3 minutes ago, AngryPig said: I have syslog set to write to flash. Would it be accessible if I hard shutdown and pulled the USB It should.
July 4, 20233 yr Community Expert A do see a few call traces, but they are from a few days ago, nothing recent.
July 4, 20233 yr Author 8 hours ago, JorgeB said: A do see a few call traces, but they are from a few days ago, nothing recent. Any insight on what they mean? The timestamps roughly line up with the time of the parity check that didn't finish
July 12, 20232 yr Author On 7/5/2023 at 12:59 AM, JorgeB said: Not really, but they look more hardware related. New update, it keeps having 'kernel panic' on startup now and if I try go to safe mode it gives me a kernel null pointer dereference error. I built a new USB with a trial license and tried booting to it and I also got 'kernel panic' so that pretty much confirms hardware I guess? Would it be worth booting into Ubuntu or Windows on a spare HDD or bootable USB to test the machine to try identify issues? I want to run all my options before going out and buying new hardware to start swapping parts Edited July 12, 20232 yr by AngryPig Added pictures
July 12, 20232 yr Community Expert 1 hour ago, AngryPig said: I built a new USB with a trial license and tried booting to it and I also got 'kernel panic' so that pretty much confirms hardware I guess? It's my suspicion. 1 hour ago, AngryPig said: Would it be worth booting into Ubuntu or Windows on a spare HDD or bootable USB to test the machine to try identify issues? It's worth a try, same for running memtest.
August 14, 20232 yr Author Solution On 7/5/2023 at 12:59 AM, JorgeB said: Not really, but they look more hardware related. Ended up being a faulty CPU. Had to RMA it.
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.