Oh, sorry, I see I messed up the link, thanks.

Any ideas how this fix will work with S3 sleep mode? Will it work / might give some errors?

No sure, never used it, but it should work.

Thanks all for the help, adding the pcie_aspm=off did it for me. Now the logs are useful again, because I got like 100 lines per second on pcie errors.

On 2/6/2023 at 9:51 AM, David Bott said:

Hi... I added...

 

append initrd=/bzroot pcie_aspm=off

 

...to the UnRAID OS config area.  (Click on Flash Drive to get to the right area.)  Add it in as a new line, save and reboot.

 

I am having the same issue. How do you add this to the config area, and where is it? Thanks

1 hour ago, CAMBO said:

where is it?

Main - Boot Device - Flash - Syslinux Configuration

6 hours ago, trurl said:

Main - Boot Device - Flash - Syslinux Configuration

Where exactly do I input “"pcie_aspm=off "? Please see screenshot. Thanks!

3 hours ago, CAMBO said:

Please see screenshot.

Please see screenshot in the post you quoted above

5 hours ago, trurl said:

Please see screenshot in the post you quoted above

I added in the Unraid OS, but still having the errors, I rebooted severals times as well. I'll post the screenshots. Let me know if I did something wrong. Thanks! 

 

I am running on Version: 6.12.0-rc5

 

 

I had the same issue and modified the config accordingly:
append pcie_aspm=off, pcie_acs_override=downstream, multifunction initrd=/bzroot

 

Seems to work perfectly - many thanks !

 

On 12/17/2022 at 9:59 AM, Nuke said:

Am i change things correct?

Hello, 

 

Appreciate all the posts from everyone here, based on the errors attached:

 

Oct 21 03:08:01 UnRAID emhttpd: read SMART /dev/sdf
Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0:    [ 6] BadTLP                
Oct 21 04:19:07 UnRAID emhttpd: read SMART /dev/sde
Oct 21 04:19:07 UnRAID emhttpd: read SMART /dev/sdo
Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000

 

Added the following:

Select > Main
Select > Flash
Scroll down > Syslinux Configuration
 

Unraid OS

kernel /bzimage
append pcie_aspm=off, initrd=/bzroot pci=noaer

 

Also referenced this post regarding pci=noaer

 

Since reboot, there is no further errors. 
Appreciate the assist here everyone!
Thank you!

kernel /bzimage
append pcie_aspm=off, initrd=/bzroot pci=noaer

 

Didn't seem to work for me. still getting spammed in my log.

Any help?

The "pcie_aspm=off" kernel parameter hides a problem.  I would really like to fix the underlying problem so the parameter isn't needed.

 

If anybody is willing to help fix it, please open a bug report at https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware platform, and attach:

• complete dmesg log (I assume this will include some Correctable Errors)
• output of "sudo lspci -vv"

Try booting with the "pcie_aspm=off" kernel parameter to see if it makes any difference. If it does, please also attach similar dmesg and lspci output for this boot.

This seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem.

So for me, i get the below.
 

Quote

Nov  6 18:34:14 MrServer kernel: i40e 0000:02:00.0:    [12] Timeout               
Nov  6 18:45:46 MrServer kernel: pcieport 0000:00:05.1: AER: Corrected error message received from 0000:02:00.0
Nov  6 18:45:46 MrServer kernel: i40e 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov  6 18:45:46 MrServer kernel: i40e 0000:02:00.0:   device [8086:15ff] error status/mask=00001000/00000000
Nov  6 18:45:46 MrServer kernel: i40e 0000:02:00.0:    [12] Timeout               

Turns out, its my ethernet port.

On 4/26/2024 at 3:26 PM, Bjorn Helgaas said:

The "pcie_aspm=off" kernel parameter hides a problem.  I would really like to fix the underlying problem so the parameter isn't needed.

 

If anybody is willing to help fix it, please open a bug report at https://bugzilla.kernel.org/, product Drivers/PCI, mention the hardware platform, and attach:

• complete dmesg log (I assume this will include some Correctable Errors)

• output of "sudo lspci -vv"

Try booting with the "pcie_aspm=off" kernel parameter to see if it makes any difference. If it does, please also attach similar dmesg and lspci output for this boot.

This seems similar to https://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem.

has anything else been found about this?

i have the same issue, i have just added the line to boot and rebooted

it will take about 4-5 hours before i know for sure as it only ever happens after about 4-5 hours

in my case i have 2 nvme drives same make and model but one is a year old and one is brand new

the old one is fine, its only the new one that keeps having this issue

i was going to return it but it seems to not be an issue with the drive

what im concerned about though, is wont this make power management no longer work? or is this specifically for NVME

i chose unraid to be able to spin down and save power

I'm seeing some similar errors in my logs, I just want to check whether this thread is the right fix before I go ahead and action it?

The item referenced in the log seems to be:

IOMMU group 7: [8086:54be] 00:1c.6 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #7

Here is the logs:

Oct 20 19:57:38 NAS01 kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6

Oct 20 19:57:38 NAS01 kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

Oct 20 19:57:38 NAS01 kernel: pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000

Try this first:

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

4 hours ago, JorgeB said:

Try this first:

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

Thanks, that was the plan 👍

Once the initial data sync finishes from the old NAS, I'll reboot and see if it made a difference.

On 10/21/2025 at 12:01 PM, flashback said:

Thanks, that was the plan 👍

Once the initial data sync finishes from the old NAS, I'll reboot and see if it made a difference.

I can't see anything in syslog for the past 26 hours (which is when the reboot was done), so I can only assume then that has fixed it!