Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Kernel panic after starting parity check

Featured Replies

Hi,

After a while, the server becomes unresponsive. The issue can be reproduced by triggering a parity check.

The chassis is a supermicro sc846 with dual PSU.

I’ve already tried:

Swapping CPU

Swapped RAM

Swapped LSI HBA controller

Swapped motherboard

Last thing would maybe be the backplane ?

Already thank you for your help

patricksnas-diagnostics-20250612-1252.zip

IMG_0547.jpeg

IMG_0546.jpeg

Edited by Hamilcar
Added screenshots

Solved by JorgeB

  • Author

I tried running a parity check in safe mode, issue still appears.

IMG_0549.jpeg

IMG_0548.jpeg

  • Community Expert

Unraid driver is crashing, this is almost always a hardware issue, typically bad RAM, or since you have a 14900K, it could also be a bad CPU due to the Intel 13/14 gen issues.

  • Author

I’ve already changed the cpu twice, could it be something else ?

The ram has also been changed and is new is it worth it to run a memtest ?

Edited by Hamilcar

  • Community Expert

memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

  • Author

I tried the sticks one by one, same result every time: start to see a kernel panic after a few minutes after the boot starting a parity check or not doesn’t matter.

I tried to include what I could see in the logs every time.

IMG_0553.jpeg

IMG_0554.jpeg

IMG_0555.jpeg

IMG_0556.jpeg

IMG_0558.jpeg

IMG_0559.jpeg

IMG_0560.jpeg

IMG_0562.jpeg

IMG_0561.jpeg

IMG_0557.jpeg

IMG_0552.jpeg

Edited by Hamilcar

  • Community Expert
  • Solution

Then the CPU would be my main suspect, even if it's the second one, there have been a lot of similar cases where it was confirmed the problem, especially with 13700K, 13900K, 14700K and 14900K

  • Author

Yeah, also there was a recent microcode update included with the latest asus bios for my motherboard.

I’ll try with another CPU and come back to the thread !

Edited by Hamilcar

  • Author

I have been able to run the system for a few hours today with a new 14900k.

No errors.

Thanks for the help !

  • 3 months later...
  • Community Expert

Diags are just after a reboot, don't see any crashes logged.

  • Community Expert

Difficult to say based on that panic. Do you get errors again during a parity check?

  • Author

No the first time the issue happened wasn’t during a parity check.

The system was running smoothly for a week.

Schould I just give up with those 14th gen, maybe I have a bad mobo/cpu combination ?

Edited by Hamilcar

  • Community Expert

Post a new log when it happens next, the error may be more clear.

  • 1 month later...
  • Author

I ended up switching the motherboard and cpu for another model. The system is now stable, thanks for the help.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.