Dark-Raptor Posted April 1, 2019 Share Posted April 1, 2019 (edited) 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 April 1, 2019 by Dark-Raptor Quote Link to comment
trurl Posted April 1, 2019 Share Posted April 1, 2019 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 Quote Link to comment
JorgeB Posted April 1, 2019 Share Posted April 1, 2019 7 hours ago, Dark-Raptor said: PCIe Bus Error: severity=Corrected Usually ways of trying to fix these is to use a different PCIe slot for the offending card, especially moving from a CPU slot to PCH slot or vice-versa and/or look for a bios update. Quote Link to comment
Dark-Raptor Posted April 1, 2019 Author Share Posted April 1, 2019 (edited) 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 April 1, 2019 by Dark-Raptor Quote Link to comment
itimpi Posted April 1, 2019 Share Posted April 1, 2019 7 minutes ago, Dark-Raptor said: its instaled but disabled just waiting for the update How did it get installed? I thought that CA would not offer it as an option unless you were on a high enough release? Quote Link to comment
Dark-Raptor Posted April 1, 2019 Author Share Posted April 1, 2019 i just clicked install and it installed Quote Link to comment
itimpi Posted April 1, 2019 Share Posted April 1, 2019 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! Quote Link to comment
Dark-Raptor Posted April 1, 2019 Author Share Posted April 1, 2019 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 Quote Link to comment
itimpi Posted April 1, 2019 Share Posted April 1, 2019 (edited) 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 April 1, 2019 by itimpi Quote Link to comment
Squid Posted April 1, 2019 Share Posted April 1, 2019 6 hours 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 You found a bug. Thanks. It shouldn't have showed it at all. Quote Link to comment
Recommended Posts
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.