Parity Errors On New Setup

[loyalsnoopdoge]

Hello,

 

I’m new to unRAID as of a week ago. I had been running Plex on my gaming PC, but switched over to an Intel NUC with unRAID to take advantage of Docker and ease of use for multiple disks. My Plex media was originally stored on the Seagate drive which used to live inside my gaming PC.

 

My disk setup is as follows:

1x 16TB Seagate Iron Wolf Pro (age 6 months) PARITY

2x 16TB WD Red Pro (age 1 week) STORAGE

These drives are in a 5 bay Sabrent USB C enclosure

 

My cache setup is as follows:

2x 2TB Samsung 980 Pro in RAID1

These drives are directly attached to the motherboard

 

Now on to the main issue:

I copied my Plex library into my drives and have set up my Docker containers. However when I initiate my parity check it returns with a ton of errors. After it returns the errors, the parity check stops and changes to a read check. Then it tells me that my parity drive is disabled and I am unable to manually initiate another parity sync, it only shows read check.

 

To attempt to remedy this I have tried the unRAID dance where I shut down the array, remove the parity drive, start the array, stop the array, re add the parity drive, and start again. However one of two things will happen when I do this. Either the parity check will start again and return a ton of errors and disable the drives again, or it will flat out just not see my drives at all until I restart unRAID again. I’ve also tried formatting the parity drive before re adding it to the array.

 

I’m also having an issue where sometimes when I try to stop the array it takes a very long time to stop and sometimes it doesn’t stop at all until I reboot.

 

I have attached diagnostics and am hoping someone can tell me how to resolve these errors and what is going wrong. Do I need to nuke my array and start over?

 

I find it very improbable that all 3 drives are damaged, since the Seagate is a known working drive and the WD Red’s are brand new.

diagnostics-20230720-0910.zip

[JorgeB]

Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: Uncorrected (Fatal) error received: 0000:02:00.0
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:02:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Jul 20 08:57:47 UnicornBarfNUC kernel: thunderbolt 0000:04:00.0: AER: can't recover (no error_detected callback)
Jul 20 08:57:47 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: AER: can't recover (no error_detected callback)
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: Root Port link has been reset (0)
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: device recovery failed
Jul 20 08:58:17 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: xHCI host controller not responding, assume dead
Jul 20 08:58:17 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: HC died; cleaning up
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2: USB disconnect, device number 2
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2.3: USB disconnect, device number 3
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2.3.1: USB disconnect, device number 4

 

We don't recommend using USB for array or pool drives, they are prone to disconnects and bad at errors handling in general, and they are the source of your issues.

[loyalsnoopdoge]

2 hours ago, JorgeB said:

Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: Uncorrected (Fatal) error received: 0000:02:00.0
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:02:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Jul 20 08:57:47 UnicornBarfNUC kernel: thunderbolt 0000:04:00.0: AER: can't recover (no error_detected callback)
Jul 20 08:57:47 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: AER: can't recover (no error_detected callback)
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: Root Port link has been reset (0)
Jul 20 08:57:47 UnicornBarfNUC kernel: pcieport 0000:00:1b.0: AER: device recovery failed
Jul 20 08:58:17 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: xHCI host controller not responding, assume dead
Jul 20 08:58:17 UnicornBarfNUC kernel: xhci_hcd 0000:38:00.0: HC died; cleaning up
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2: USB disconnect, device number 2
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2.3: USB disconnect, device number 3
Jul 20 08:58:17 UnicornBarfNUC kernel: usb 4-2.3.1: USB disconnect, device number 4

 

We don't recommend using USB for array or pool drives, they are prone to disconnects and bad at errors handling in general, and they are the source of your issues.

 

So this to you looks like a problem with either my USB cable or my enclosure.

For right now I'm locked into doing this over USB, although I could change that in the future

 

What about drivers? How do I go about updating the drivers on unRAID? 

 

What about settings in the BIOS on my NUC? are there any settings I could / should change?

 

One other thing that is really weird is that I never get any disk errors when I am scanning / analyzing my Plex library. it only happens during parity sync. It also doesn't happen during read checks

 

Edited July 20, 2023 by loyalsnoopdoge

[JorgeB]

You cannot change the drivers, you can try a newer release with a newer kernel but possibly it won't help, like mentioned this type of issues are quite common with USB.

 

13 hours ago, loyalsnoopdoge said:

it only happens during parity sync.

Possibly because it's reading and writing at the same time.

[loyalsnoopdoge]

@JorgeB I'm trying a different enclosure, Thunderbolt this time but a similar but slightly different issue is happening this time

Could you please look over my log file for this and let me know what you think the issue is?

unicornbarfnuc-diagnostics-20230722-1852.zip

[JorgeB]

Sorry for the late reply, was away, log is being spammed with PCIe errors, see if this helps:

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

 

[loyalsnoopdoge]

@JorgeB

Hi there,

 

Thanks for your help. I gave up on the USB drives in the NUC. I returned it and built a new system in the Fractal Design Define 7 XL. I got an LSI 9400 16i and some SAS to SATA breakout cables for my drives.

 

Everything works great!