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.

Server keeps crashing/rebooting after lockup and parity check

Featured Replies

A few months ago, my Unraid server went offline and was stuck at the power-on message stating "DXE—CPU Initialization.." I rebooted the Server, and it started. Now, on the restart, it does a parity check, and near/close to 100%, it cycles again. This has been happening since. I'm not sure what to do next. I did swap out the USB drive.

 

Any help would be appreciated.

level1-diagnostics-20240606-1851.zip

  • Community Expert

Server rebooting on its own is almost always a hardware issue.

  • Author

I bought a new power supply.  From what I read on the forums it may be the culprit.

  • Author

Swapped with new power supply and ram. The server still crashes and reboots after the parity check.  😔

  • Community Expert

RAM, board or CPU would be the next suspects.

  • Author

I bought some on Amazon and waiting for them to come in.  I'll report back.

 

  • 2 weeks later...
  • Author

Still crashing a few hours after the parity check is complete.  I see this is the logs.  Any idea what's happening here.

 

Jun 26 01:06:56 Level1 kernel: Plex Media Scan[31375]: segfault at 0 ip 0000152d93efdb8d sp 00007ffc00f16840 error 4 in libavcodec.so.59[152d93d87000+3e0000] likely on CPU 4 (core 5, socket 0)
Jun 26 01:06:56 Level1 kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: AER: Corrected error message received from 0000:00:01.1
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1:   device [1022:1483] error status/mask=00000040/00006000
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1:    [ 6] BadTLP 

  • Community Expert
2 hours ago, daddygrant said:

Plex Media Scan[31375]: segfault

These are usually harmless.

 

2 hours ago, daddygrant said:

Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: AER: Corrected error message received from 0000:00:01.1
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1:   device [1022:1483] error status/mask=00000040/00006000
Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1:    [ 6] BadTLP 

See if this help for that:

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

 

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.