Hi,

 

My sys log is logging the below and doing it once or twice every second. Any ideas what this is? My NIC going bad?

 

I have attached my entire log file.

 

Jun  9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6
Jun  9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jun  9 08:25:48 unraid kernel: pcieport 0000:00:1c.6:   device [8086:a296] error status/mask=00000001/00002000
Jun  9 08:25:48 unraid kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                  (First)

unraid-syslog-20200609-1526.zip

See if this helps, or try another slot and/or look for a BIOS update.

Thank you very much, I will try that.

I've done the below and am still having the logging issues. The only PCI device I have in this box is a 2 port sata card. I do have another identical card I could swap it out for. I've no way of knowing what pci device it's referring to in the error. Would someone be able to tell which device is causing the issue?

 

Log:

 

Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: AER: Multiple Corrected error received: 0000:00:1c.1
Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: device [8086:a291] error status/mask=00000001/00002000

 

What I've done:

• Updated to the latest bios (motherboard is  ASUSTeK COMPUTER INC. ROG STRIX Z370-E)
• updated the syslinux.config file within the flash > syslinux folder to the below (adding the pci=nommconfto to the append initrd=/bzroot line).

 

Syslinux file:

 

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append initrd=/bzroot pci=nommconfto
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest

9 hours ago, pixelgraft said:

Would someone be able to tell which device is causing the issue?

Possibly if you post the complete diagnostics.

diagnostics attached. One thing I just noticed is that these log errors only start AFTER I start up dockers. For example, starting up Plex docker, or binhex-krusader docker starts doing these logs.

unraid-diagnostics-20200614-0957.zip

Can't see which device, try doing the same as this one.