I am running a parity check in preparation to replace a smaller drive with a larger.  The newer drive is running a pre clear and I kicked of a Parity check.

 

I have all my app data on the NVME cache... with docker running I had 7-10 MB/sec with docker off more reasonable at 75 butt....... I noticed this in my log:

 

May 31 17:30:37 infinity  emhttpd: spinning down /dev/sdd
May 31 17:30:41 infinity  emhttpd: read SMART /dev/sdd
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:   device [8086:7ac4] error status/mask=00000001/00002000
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:   device [8086:7ac4] error status/mask=00000001/00002000
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:   device [8086:7ac4] error status/mask=00000001/00002000
May 31 17:31:15 infinity kernel: pcieport 0000:00:1b.4:    [ 0] RxErr    

 

I will attach the diagnostics zip file as well if I can figure it out

 

I am very new to unraid thanks for any help

 

J

infinity-diagnostics-20230531-1727.zip

This may help with the PCIe errors, then post new diags if the parity check is still slow.

 

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009