Parity Sync keeps crashing on brand new setup

[artsy99]

I'm setting up a new system with 3X8TB (1x8TB drive for parity) drives in drive bay enclosure with an ASMedia controller. Also using 1 SSD 1TB drive for cache.  My parity syncs keep failing/crashing and freezing up the entire system to where I have to do hard resets by holding the power button and when it is running the parity check it is moving very slow (40MB/s) This is my first time dealing with UnRaid and Linux so I am completely a NOOBY. Any help would be very greatfull. I'm going on 4 days and have not been able to get this thing to finish a parity sync. I have attached logs.

 

http://localhost/tower-diagnostics-20220725-1903.zip

tower-diagnostics-20220725-1903.zip

[artsy99]

I'm also posting a screenshot of the syslog readout that forced me into panic mode..

 

l 25 19:20:21 Tower kernel: ata6.00: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.01: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.02: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.03: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.04: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.05: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.06: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.07: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.08: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.09: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.10: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.11: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.12: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.13: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.14: failed to read SCR 1 (Emask=0x40)
Jul 25 19:20:21 Tower kernel: ata6.03: exception Emask 0x100 SAct 0x1f80 SErr 0x0 action 0x6 frozen
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/40:38:20:d1:eb/05:00:6d:02:00/40 tag 7 ncq dma 688128 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/40:40:60:d6:eb/05:00:6d:02:00/40 tag 8 ncq dma 688128 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/40:48:a0:db:eb/05:00:6d:02:00/40 tag 9 ncq dma 688128 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/40:50:e0:e0:eb/05:00:6d:02:00/40 tag 10 ncq dma 688128 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/40:58:20:e6:eb/05:00:6d:02:00/40 tag 11 ncq dma 688128 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:21 Tower kernel: ata6.03: failed command: READ FPDMA QUEUED
Jul 25 19:20:21 Tower kernel: ata6.03: cmd 60/80:60:60:eb:eb/00:00:6d:02:00/40 tag 12 ncq dma 65536 in
Jul 25 19:20:21 Tower kernel:         res 40/00:50:e0:e0:eb/00:00:6d:02:00/40 Emask 0x100 (unknown error)
Jul 25 19:20:21 Tower kernel: ata6.03: status: { DRDY }
Jul 25 19:20:22 Tower kernel: ata6.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 19:20:23 Tower kernel: ata6.00: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 19:20:23 Tower kernel: ata6.01: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 19:20:24 Tower kernel: ata6.02: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 19:20:24 Tower kernel: ata6.03: hard resetting link
Jul 25 19:20:24 Tower kernel: ata6.03: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 19:20:24 Tower kernel: ata6.04: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:25 Tower kernel: ata6.05: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:25 Tower kernel: ata6.06: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:25 Tower kernel: ata6.07: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:26 Tower kernel: ata6.08: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:26 Tower kernel: ata6.09: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:26 Tower kernel: ata6.10: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:27 Tower kernel: ata6.11: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:27 Tower kernel: ata6.12: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:27 Tower kernel: ata6.13: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:27 Tower kernel: ata6.14: SATA link down (SStatus 0 SControl 330)
Jul 25 19:20:27 Tower kernel: ata6.00: configured for UDMA/133
Jul 25 19:20:27 Tower kernel: ata6.01: configured for UDMA/133
Jul 25 19:20:27 Tower kernel: ata6.02: configured for UDMA/133
Jul 25 19:20:27 Tower kernel: ata6.03: configured for UDMA/133
Jul 25 19:20:27 Tower kernel: ata6: EH complete

[JorgeB]

Controller is using or connected to a SATA port multiplier, don't use those, use one of the recommended controllers.

[artsy99]

11 hours ago, JorgeB said:

Controller is using or connected to a SATA port multiplier, don't use those, use one of the recommended controllers.

Ok..I am using one of the recommended ASMEDIA controllers (1062). It definitely does have a port multiplier on it. I switched the card to a different PCIe slot and it is running the parity sync faster than it had the last 3 times. I'll let it run again and see if the system crashes...again.

 

Also, I have a SYBA 4 bay SATA drive enclosure. It has one USB and one eSATA connector. How would I use that without a controller card that supports port multipliers?

[JonathanM]

15 minutes ago, artsy99 said:

I have a SYBA 4 bay SATA drive enclosure. It has one USB and one eSATA connector. How would I use that without a controller card that supports port multipliers?

You don't. That enclosure is going to be an issue for parity check or disk rebuilds, it will be speed limited. If you can internally change the wiring so you have 1 external SATA connection per drive it would be ok, or if you could switch out its backplane to one that supports SAS and connect it to a SAS HBA that would work too.

[artsy99]

1 hour ago, JonathanM said:

You don't. That enclosure is going to be an issue for parity check or disk rebuilds, it will be speed limited. If you can internally change the wiring so you have 1 external SATA connection per drive it would be ok, or if you could switch out its backplane to one that supports SAS and connect it to a SAS HBA that would work too.

Yikes...I just bought all of this stuff. Damn, I guess I should've researched a little better. I did move the Parity Drive to one of the mobo SATA ports and the Parity Sync is running twice as fast as it did before...(from 45 mb/s to 90 mb/s) Maybe, I can get it to finally complete the  Parity sync and get it up and running until I can buy a new controller and a different (independent drive bay)  SAS type of drive enclosure....

Thanks for the help.