Device error when booting - how find device

[wkellogg]

I've had this happen before but have been able to determine device and replace it. Getting these errors scrolling during boot:

Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:    [ 0] RxErr                 
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error message received from 0000:01:00.0
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:   device [10b5:8724] error status/mask=00000001/0000a000
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:    [ 0] RxErr                 
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error message received from 0000:01:00.0
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:   device [10b5:8724] error status/mask=00000001/0000a000
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:    [ 0] RxErr                 
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error message received from 0000:01:00.0
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 16 18:13:15 Unraid001 kernel: pcieport 0000:01:00.0:   device [10b5:8724] error status/mask=00000001/0000a000

Log fills up and fills up usb drive, but I'll rant about that later. It's the only device throwing an error. I've looked through the dashboard and find nothing corresponding to the device. All drives come up as healthy. Once it's booted 1 cpu core keeps running at 90+ % and the Log shows 100%. Machine will stay running. Once I Start the Array the 'clock is ticking'. After about 5mins the machine freezes. Was thinking it's hardware (MB, CPU, RAM, etc.), which is all about 6 months old, but the fact that it stays running prior to starting the array tells me it's a drive. I've seen this before and I believe the freezing is because the CPU is having too much fun writing these errors, until it runs out of space.

Unsure if I should enter this under new features but there has got to be a better way to manage the Log file. Have been researching over the last few months, on and off, and quite a few have similar issues with cleaning/deleting/truncating , etc. There has to be a better way. Then again we still have to manually clear cookies & cache.

Thanks in advance.

Edited September 16, 2024 by wkellogg
clarification

[JorgeB]

Try this first:

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

 

[wkellogg]

Many thanks. Hope you get a big enough cut from the new licensing structure.

[wkellogg]

Would still like to know how to find that device. Since it's a single device throwing the error I'd like to proactively replace it.

Then there's the Log file issue......

[JorgeB]

49 minutes ago, wkellogg said:

Would still like to know how to find that device.

It should be visible in the diagnostics.