Pcie port error in log


Recommended Posts

im new to unraid and after checking my log file i seem to be getting a few errors and unsure if its important or not

 

Version: 6.6.7

 

 

Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: [ 6] Bad TLP
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: [ 6] Bad TLP
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: Error of this Agent is reported first
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: device [1000:0087] error status/mask=00000041/00002000
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: [ 0] Receiver Error (First)
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: [ 6] Bad TLP

asgard-diagnostics-20190401-0624.zip

Edited by Dark-Raptor
Link to comment

Not likely related to your problem, but why are you ignoring this?

Apr  1 06:23:00 Asgard root: Fix Common Problems: Warning: parity.check.tuning.plg Not Compatible with unRaid version 6.6.7 ** Ignored

The reason that plugin is not compatible with your version is because it requires a feature of Unraid that isn't yet available on your version, as mentioned in the first post of the support thread for that plugin:

 

https://forums.unraid.net/topic/78394-plugin-parity-check-tuning/

 

On 3/2/2019 at 8:46 AM, itimpi said:

Requirements

  • Unraid 6.7 rc3 or later

 

Link to comment
1 hour ago, trurl said:

Not likely related to your problem, but why are you ignoring this?


Apr  1 06:23:00 Asgard root: Fix Common Problems: Warning: parity.check.tuning.plg Not Compatible with unRaid version 6.6.7 ** Ignored

The reason that plugin is not compatible with your version is because it requires a feature of Unraid that isn't yet available on your version, as mentioned in the first post of the support thread for that plugin:

 

https://forums.unraid.net/topic/78394-plugin-parity-check-tuning/

 

 

1

its instaled but disabled just waiting for the update

 

 

I've updated the bios and still gettings the errors ill look into changing a PCIe slot but i don't think i can because of clearance issues

 

i am right in thinking this is pcie slot 1?

that is my gfx card i supose i can remove later down the line

Edited by Dark-Raptor
Link to comment
56 minutes ago, Dark-Raptor said:

i just clicked install and it installed

Are you saying that CA DID offer it as an option?   On my test system CA did not offer it while the test system was running 6.6.6.

 

i agree that if you go direct to gitHub to find the .plg file it will not prohibit you installing it, but I did not envisage people doing that! 

Link to comment

 

Just now, itimpi said:

Are you saying that CA DID offer it as an option?   On my test system CA did not offer it while the test system was running 6.6.6.

 

i agree that if you go direct to gitHub to find the .plg file it will not prohibit you installing it, but I did not envisage people doing that! 

i just clicked on the apps tab on the nav bar and found the app and clicked install did nothing strange to get it installed

Link to comment
24 minutes ago, Dark-Raptor said:

 

i just clicked on the apps tab on the nav bar and found the app and clicked install did nothing strange to get it installed

Interesting.    For me searching for the app failed until I update to a 6.7 rc release.   Did you search for it or was it found some other way?   Just wondering if I should add an explicit check into the plugin rather than relying on CA policing it for me?

Edited by itimpi
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.