Muath

Yes last line in the logs should be "Connecting...", but it will work

Try to change the protocol to "openVPN" instead of NordLynx

The nordlynx protocol was working fine until last week then the container stopped working, just now when i come across your comment I figure the issue and now it's working with openVPN, so thanks ❤️ Just write the country name for an example: "Netherlands" and that's it. and if you're only using Transmission then you should use haugene/transmission-openvpn it works flawlessly .. excpt that you need to delete one variable (OPENVPN_CONFIG ) after docker update.

This keeps happening to me each month suddenly the logs get filled up, I noticed when it happens I can't use the terminal or see the Logs, not sure if my issue is the same as yours. video capture attached. 2020-12-07 17-31-56.mp4

Many thanks to you and @albakhit& @Zyzto 🌹 شاكر لكم جميعًا على المجهود العظيم

That's great to hear, Thank you very much for your hard work and giving support to arabic language. Shookran 😁🌹

بسم الله الرحمن الرحيم، السلام عليكم ورحمة الله وبركاته، ما شاء الله، نبارك لكم افتتاح القسم العربي لنظام "أنريد". ومنه نتعاون في طرح حلول وحل مشاكل البعض خاصة المتعلقة باللغة العربية. ونشر ثقافة وروعة النظام للعالم العربي 😁 سؤالي هل هنالك من تبرع لترجمة النظام للغة العربية؟ إذا أمكن اخبارنا بالطريقة وهل تأخذ من الوقت الشيء الكثير أو لها طرق معينة تسهل العملية؟ لمعرفة إذا ما كان من الممكن المساعدة في الترجمة أو أنها قد تحتاج لوقت طويل وتمكن قوي في اللغة الإنجليزية. شاكر لكم جهودكم 🌹

It did turn out to be a Faulty CPU 💔. Thank you everyone 🌹

I'm using these RAMs: https://www.amazon.com/G-SKILL-TridentZ-288-Pin-3000MHz-F4-3000C16D-16GTZR/dp/B06WP4L3D7/ and tried to use: https://www.newegg.com/g-skill-16gb-288-pin-ddr4-sdram/p/N82E16820232290 not overclocked and I was using 4 of them but then removed 2 and switch between the slots but issue remain .. actually it's getting worse! (I will keep updating this comment with new logs for index purpose if someone search for it 👁️‍🗨️) Jun 24 18:18:05 MoathCenterr kernel: mce: [Hardware Error]: Machine check events logged Jun 24 18:18:05 MoathCenterr kernel: mce: [Hardware Error]: CPU 10: Machine Check: 0 Bank 5: bea0000000000108 Jun 24 18:18:05 MoathCenterr kernel: mce: [Hardware Error]: TSC 0 ADDR 4206c8 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Jun 24 18:18:05 MoathCenterr kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1593011852 SOCKET 0 APIC 5 microcode 8701013 2020-07-06 logs: Jul 6 18:46:08 MoathCenterr kernel: mce: [Hardware Error]: Machine check events logged Jul 6 18:46:08 MoathCenterr kernel: mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 5: bea0000000000108 Jul 6 18:46:08 MoathCenterr kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8109a37a MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Jul 6 18:46:08 MoathCenterr kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1594050335 SOCKET 0 APIC 4 microcode 8701013 Jul 6 18:56:27 MoathCenterr root: Fix Common Problems: Error: Machine Check Events detected on your server Jul 6 18:56:27 MoathCenterr root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. 2020-07-07 - OS suddenly shut down and the message below shown:

I changed the RAMs, GPU and motherboard, so most likely CPU issue! or could it be RAM not supporting AMD CPU?

This is become annoying: Apr 24 04:58:20 MoathCenterr kernel: mce: [Hardware Error]: Machine check events logged Apr 24 04:58:20 MoathCenterr kernel: mce: [Hardware Error]: CPU 10: Machine Check: 0 Bank 5: bea0000000000108 Apr 24 04:58:20 MoathCenterr kernel: mce: [Hardware Error]: TSC 0 ADDR 14b767dc2084 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Apr 24 04:58:20 MoathCenterr kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1587693467 SOCKET 0 APIC 5 microcode 8701013 Apr 24 05:03:30 MoathCenterr root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 24 05:03:30 MoathCenterr root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Apr 24 05:08:22 MoathCenterr root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 24 05:08:22 MoathCenterr root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Apr 24 18:12:33 MoathCenterr kernel: CPU: 10 PID: 5903 Comm: unraidd0 Tainted: G O 4.19.107-Unraid #1 Apr 24 18:12:33 MoathCenterr kernel: Call Trace: Apr 24 18:13:04 MoathCenterr kernel: CPU: 5 PID: 1727 Comm: scsi_eh_10 Tainted: G D O 4.19.107-Unraid #1 Apr 24 18:13:04 MoathCenterr kernel: Call Trace:

>> so my system keep hang the last month from time to time and since there's no more info I could gather I didn't update my issue here sometimes some threads hang and system will keep running but other times all the threads hang which then I need to restart the system forcely: but now Fix Common Problems detect hardware errors after suddenly the parity check triggered!: error logs: Apr 16 11:57:06 MoathCenterr kernel: mce: [Hardware Error]: Machine check events logged Apr 16 11:57:06 MoathCenterr kernel: mce: [Hardware Error]: CPU 10: Machine Check: 0 Bank 5: bea0000000000108 Apr 16 11:57:06 MoathCenterr kernel: mce: [Hardware Error]: TSC 0 ADDR 14798839663c MISC d010000000000000 SYND 4d000000 IPID 500b000000000 Apr 16 11:57:06 MoathCenterr kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1587027393 SOCKET 0 APIC 5 microcode 8701013 Apr 16 12:07:25 MoathCenterr root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 16 12:07:25 MoathCenterr root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Apr 16 14:13:07 MoathCenterr kernel: Plex Script Hos[29328]: segfault at 0 ip 000014f2ee0a8d37 sp 000014f2e540e130 error 4 in libpython2.7.so.1.0[14f2edf71000+19f000] Can it be CPU failure? 😥 UPDATE: logs below keep happening from time to time and activate the Parity. moathcenterr-diagnostics-20200424-0508.zip moathcenterr-diagnostics-20200416-1648.zip

Thank you very much for your assist. Now on the fifth try the parity check completed with no issue! I didn't do much I just change the GPU to an old one and cleaned the fans, not sure if the issue fixed now or not, I will be back next month during the parity check if anything happen. Thank you everyone.

Yes, but I don't think the nginx is the reason. Mar 3 00:04:02 MoathCenterr kernel: mdcmd (63): nocheck Pause Mar 3 00:05:35 MoathCenterr nginx: 2020/03/03 00:05:35 [error] 5831#5831: *1630028 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "moathcenterr", referrer: "http://moathcenterr/Main" (Video Recording). Parity Check History didn't show the last 4 hung sessions only the one I canceled.

so the parity check will take 3 whole years to finish 😞 so this is the 4th time I tried to operate the parity then got stuck. * I just notice one of the threads is stuck also! moathcenterr-diagnostics-20200302-2154.zip

I was thinking it is very unlikely for this to be the reason so I forget about it, but I will do it this week. * Parity is stuck now for the third time in a row 😞.

Below link is a recording when I tried to pause it, and when I reboot or shut down using the system it hung so then I force shutting it down. https://drive.google.com/open?id=1I_bq1_zauobcCLPmcEK_nWyzWH2SOBYL logs which shown in the end is: Feb 19 00:03:51 MoathCenterr nginx: 2020/02/19 00:03:51 [error] 5804#5804: *3929950 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "moathcenterr", referrer: "http://moathcenterr/Main" Feb 19 00:03:57 MoathCenterr nginx: 2020/02/19 00:03:57 [error] 5804#5804: *3929942 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "moathcenterr", referrer: "http://moathcenterr/Main" Feb 19 00:04:03 MoathCenterr nginx: 2020/02/19 00:04:03 [error] 5804#5804: *3930103 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "moathcenterr", referrer: "http://moathcenterr/Main" Feb 19 00:04:12 MoathCenterr nginx: 2020/02/19 00:04:12 [error] 5804#5804: *3930061 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /logging.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/logging.htm", host: "moathcenterr", referrer: "http://moathcenterr/Main" Feb 19 00:04:23 MoathCenterr nginx: 2020/02/19 00:04:23 [error] 5804#5804: *3930278 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.100.35, server: , request: "POST /logging.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/logging.htm", host: "moathcenterr", referrer: "http://moathcenterr/Tools" moathcenterr-diagnostics-20200219-0019.zip syslog

a quick update on my issue here, so this issue is still occurring every two weeks~ (since the server working fine the rest of the almost two weeks I adapt to this issue) after last hang parity-check triggered due to forcing the shutdown, now the parity-check is stuck!! * This is not the first time happen to me, when I tried to reboot it will hang moathcenterr-diagnostics-20200216-1927.zip

Thank you very much, unfortunately, swapping MB didn't help 😔, when I had the ASrock motherboard I couldn't find how to disable it through the BIOS, I will search it now with the new motherboard at first, I added it to the append line but then the OS won't boot up. # so now, I swapped MB then upgrade unRAID to 6.8 and now OS went down 😔. the weird thing is the power draw didn't change much so it's more like OS is hung (when the OS is up and running flash stick usually blinking ) so is it maybe the USB flash need to be replaced or SAS controller is the cause of the issue? I just want to enjoy my movies 😔 btw, this issue happen after I bought second nvme m.2. and configure it as RAID 0, do you think this may cause this issue?

I noticed something just now, CPU usage went way high (~75%) which is very rare then OS stopped! * sysLog attached. syslog 2019-12-07

sorry I didn't update my current situation, I tried to clear the CMOS then update the BIOS but didn't work, then I tried to update the BIOS to a different version and still not working, then I returned back to release version and it worked and the system boot-up!. (BIOS Update page.) then the main issue happened again to me, so after some search seems there's an issue with ASrock motherboards with Linux in general, but there's some suggestion to fix the issue one of which: pcie_aspm=off to "Syslinux Configuration" (not sure if I did it correctly kindly see the picture if it's correct or not) so now server will work for a couple of days or so, then OS will stop (the main issue). I'm starting to believe the issue caused by the motherboard so I ordered another one from ASUS, and I hope it fixes the issue and the motherboard is the real cause. btw, is there something required before changing the motherboard? and for the Logs the 3 line error below keep repeating: Dec 7 08:47:10 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Dec 7 08:47:10 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Dec 7 08:47:10 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000

I've set to boot from the flash, but after the motherboard logo and attempt to boot UNRAID it goes into a black screen and all the fans work weirdly some fans speed up and other slow down or even stopped, and when I try to forcibly shut it (via the button), it does not respond! so the only way to shut it down is by PSU! I'm thinking maybe all these issues from the motherboard (ASRock X570 Steel Legend). *I remember now, any fan connect to the Motherboard don't work properly, as the picture show now CPU fan doesn't work at all after booting UNRAID. GPU fans working fine.

Well .. I've updated the BIOS and now it's not working at all 😔💔

Thank you, Seems this issue fixed it self, but main issue still remain . Does below logs help to figure the issue? Nov 17 20:01:23 MoathCenterr rsyslogd: [origin software="rsyslogd" swVersion="8.1903.0" x-pid="1934" x-info="https://www.rsyslog.com"] start Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: [ 6] BadTLP Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: [ 6] BadTLP Nov 17 20:01:35 MoathCenterr ool www[26632]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Nov 25 16:54:36 MoathCenterr rsyslogd: [origin software="rsyslogd" swVersion="8.1903.0" x-pid="2153" x-info="https://www.rsyslog.com"] start Nov 25 16:54:48 MoathCenterr ntpd[2044]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

so, after scanning the USB stick by Windows it shows no issue with it, but then when returned it to the server it works! it lasts for a weak so I thought the issue been fixed now .. but then when I upgrade it to v6.8 rc6 it worked for an hour which is better than before but still went down after 😔. I've run Fix Common Problems plug-in and no issue found. I have the things below which may cause the issue: 1- APC UPC connects via a USB. 2- (SAS9211-8I 8PORT Int 6GB Sata+SAS Pcie 2.0). logs still show the same warnings: Nov 17 17:45:48 MoathCenterr kernel: ACPI: Early table checksum verification disabled Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:02:00.0: BAR 14: failed to assign [mem size 0x00c00000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:01.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:03.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:08.0: BAR 14: failed to assign [mem size 0x00200000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:09.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:03:0a.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:04:00.0: BAR 0: failed to assign [mem size 0x00004000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:06:00.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:07:05.0: BAR 14: failed to assign [mem size 0x00100000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0a:00.0: BAR 0: failed to assign [mem size 0x00020000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0a:00.0: BAR 3: failed to assign [mem size 0x00004000] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0c:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0c:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0d:00.0: BAR 5: failed to assign [mem size 0x00000800] Nov 17 17:45:48 MoathCenterr kernel: pci 0000:0e:00.0: BAR 5: failed to assign [mem size 0x00000800] Nov 17 17:45:48 MoathCenterr kernel: floppy0: no floppy controllers found Nov 17 17:45:48 MoathCenterr kernel: random: 7 urandom warning(s) missed due to ratelimiting Nov 17 17:45:48 MoathCenterr kernel: ccp 0000:11:00.1: SEV: failed to get status. Error: 0x0 Nov 17 17:45:49 MoathCenterr rpc.statd[2051]: Failed to read /var/lib/nfs/state: Success Nov 17 17:45:49 MoathCenterr ntpd[2081]: bind(19) AF_INET6 fe80::a861:8fff:fe9b:94c9%10#123 flags 0x11 failed: Cannot assign requested address Nov 17 17:45:49 MoathCenterr ntpd[2081]: failed to init interface for address fe80::a861:8fff:fe9b:94c9%10 Nov 17 17:46:08 MoathCenterr avahi-daemon[6501]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Nov 17 19:10:05 MoathCenterr root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Nov 17 19:10:10 MoathCenterr kernel: XFS (md1): Per-AG reservation for AG 7 failed. Filesystem may run out of space. Nov 17 19:47:03 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 19:47:03 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 19:47:03 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:10 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:10 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:10 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:13 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:23 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:31 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:51 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:51 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:51 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:01:59 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:01:59 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:01:59 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:02:02 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:02:02 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:02:02 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:02:03 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:02:03 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:02:03 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:02:09 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:02:09 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:02:09 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Nov 17 20:02:12 MoathCenterr kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:01.1 Nov 17 20:02:12 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:02:12 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 There's new errors now which is: Nov 17 20:02:12 MoathCenterr kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 17 20:02:12 MoathCenterr kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 moathcenterr-diagnostics-20191117-1734.zip