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.

Upgraded to 6.4 from 6.3.5 and having issues that cause Unraid to freeze

Featured Replies

Recently upgraded and immediately noticed several errors in logs that eventually lead to the log directory filling up with Unraid eventually freezing up altogether. Before that happens all seems to be running extremely well. 

 

Here's my build:

AMD Ryzen Threadripper 1920x

32GB RAM

MSI X399 GAMING PRO CARBON AC

2x Intel SAS Raid Controller Cards

NVIDIA GTX 1060

 

Errors that are causing the system to freeze up eventually:

ErrorWarningSystemArrayLogin


Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [ 8] RELAY_NUM Rollover 
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [12] Replay Timer Timeout 
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0a00(Transmitter ID)
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: device [1000:0072] error status/mask=00001100/00002000
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [ 8] RELAY_NUM Rollover 
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [12] Replay Timer Timeout 
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0a00(Transmitter ID)
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: device [1000:0072] error status/mask=00001000/00002000
Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [12] Replay Timer Timeout 
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000b(Transmitter ID)
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00001000/00006000
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [12] Replay Timer Timeout 
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Corrected error received: id=0000
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000b(Receiver ID)
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000080/00006000
Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [ 7] Bad DLLP 

Jan 19 19:22:39 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000
Jan 19 19:22:39 CheshireCat kernel: pcieport 0000:00:01.3: can't find device of ID0000

 

Anyone know what these are? Things worked fine while I ran under v.6.3.5.

cheshirecat-diagnostics-20180119-1916.zip

  • Community Expert

These can usually only be fixed by a new bios, new kernel or swapping the controllers to different slots if available, since you have two try with one at a time in all the different slots to try and identify the current problem one(s).

Archived

This topic is now archived and is closed to further replies.

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.