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.

Log file filling up - PCIe Bus Error

Featured Replies

My log file seem to be filling up with errors related to the PCIe bus and my NVME devices that are connected via a PCIe to NVME adapter. Could someone look at this log and tell me what the issue specifically is? I can't quite make out what I should do here.

syslog.1.txt

  • Community Expert

you may have teh samsun or related nvme latencey bug...

syslinux grub option may help here...
 

The errors in your log file point to PCIe bus communication issues involving your NVMe devices. Specifically:

Corrected PCIe bus errors: These indicate that data transmission errors occurred between your system and the NVMe devices, but the errors were automatically corrected.

Types of errors: These include RxErr, Timeout, and BadDLLP, which are indicative of signal integrity or compatibility issues.

 

Common Causes of PCIe/NVMe Bus Errors

Signal Integrity Issues:

Poor quality PCIe riser cables or adapters.

Inadequate power delivery to the PCIe slots or NVMe devices.

Firmware/Driver Compatibility:

Outdated firmware for your NVMe devices.

Compatibility issues with the system's PCIe host controller.

Samsung or Similar NVMe Latency Bug:

Certain NVMe drives, particularly Samsung models, are known to encounter latency issues that manifest as PCIe bus errors.

PCIe Link Negotiation:

PCIe lanes running at speeds higher than the system can reliably support (e.g., PCIe Gen 4 vs. Gen 3 compatibility issues).

 

Apply a Kernel Parameter to Suppress Errors

Add the following parameter to your Unraid bootloader (syslinux or GRUB) to mitigate the NVMe-related PCIe errors:

nvme_core.default_ps_max_latency_us=5500 pci=noaer pcie_aspm=off

This disables Advanced Error Reporting (AER), which may reduce the logging of benign corrected errors.

Turns off slep states to prevent power off on pcie devices.

Sets the latency on nvme read in event of error (samsung bug fix)

 

Update NVMe Firmware

Check if your NVMe devices have a firmware update available. You can usually do this using the manufacturer's tools (e.g., Samsung Magician for Samsung drives).

nvme list
nvme fw-download /dev/nvme0n1 --fw=<firmware-file>
nvme fw-activate /dev/nvme0n1

 

nvme list
nvme fw-download /dev/nvme0n1 --fw=<firmware-file>
nvme fw-activate /dev/nvme0n1

 

Manually Set PCIe Link Speed

If your motherboard supports PCIe Gen 4 but your NVMe adapter or drives are Gen 3, this mismatch can cause errors. Force the PCIe slot to Gen 3:

Enter your system BIOS/UEFI.

Navigate to PCIe Configuration or a similar setting.

Set the link speed to Gen 3 for the slot where the adapter is connected.

Save changes and reboot.

 

 

  • Community Expert

Higly rfecomend sylin gurb commads to help assit and potentail fix spam in logs:

Web UI> Main> clik on flash --scroll to bottom

 

image.thumb.png.5886301631122c8afd1f23bfafbf3894.png

 

add

nvme_core.default_ps_max_latency_us=5500 pci=noaer pcie_aspm=off

after bzrooot

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.