unCoreX Posted February 21, 2023 Share Posted February 21, 2023 (edited) I have been receiving this error message after upgrading to 6.11.5. Never seen it before on previous unraid versions. It's so random. But here is the error: Feb 19 15:33:32 Pegasus root: Reloading Nginx configuration... Feb 19 16:52:34 Pegasus kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Feb 19 16:52:34 Pegasus kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Feb 19 16:52:34 Pegasus kernel: pcieport 0000:00:01.0: device [8086:1901] error status/mask=00000001/00002000 Feb 19 16:52:34 Pegasus kernel: pcieport 0000:00:01.0: [ 0] RxErr Feb 19 22:30:27 Pegasus ool www[6361]: Successful logout user root from XX.XX.XX:XX Feb 20 02:21:52 Pegasus kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Feb 20 02:21:52 Pegasus kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Feb 20 02:21:52 Pegasus kernel: pcieport 0000:00:01.0: device [8086:1901] error status/mask=00000001/00002000 Feb 20 02:21:52 Pegasus kernel: pcieport 0000:00:01.0: [ 0] RxErr Feb 21 19:21:31 Pegasus kernel: eth0: renamed from vetha3980df Feb 21 23:01:47 Pegasus kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Feb 21 23:01:47 Pegasus kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Feb 21 23:01:47 Pegasus kernel: pcieport 0000:00:01.0: device [8086:1901] error status/mask=00000001/00002000 Feb 21 23:01:47 Pegasus kernel: pcieport 0000:00:01.0: [ 0] RxErr Feb 21 23:01:58 Pegasus kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Feb 21 23:01:58 Pegasus kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Feb 21 23:01:58 Pegasus kernel: pcieport 0000:00:01.0: device [8086:1901] error status/mask=00000001/00002000 Feb 21 23:01:58 Pegasus kernel: pcieport 0000:00:01.0: [ 0] RxErr Any idea what this ism any why only in unraid version 6.11.5? Edited February 22, 2023 by CiscoCoreX Quote Link to comment
Solution JorgeB Posted February 22, 2023 Solution Share Posted February 22, 2023 Try this: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009 1 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.