Array and WebUI failing to start

[dptech21]

Hello,

 

I recently changed my parity disk and an array disk at the same time. The re-sync was going well, then about halfway through the operation I received millions of errors. The actual data is still intact it seems. After the re-sync I pulled several files at random from multiple shares and all look good. I also have a backup worst case.

 

From what I can tell the issue is related to an ATA bus. I am getting this repeating error in the log:

 

Jan 30 23:09:50 fork kernel: ata7.00: irq_stat 0x00400000, PHY RDY changed
Jan 30 23:09:50 fork kernel: ata7: SError: { RecovComm PHYRdyChg }
Jan 30 23:09:50 fork kernel: ata7.00: failed command: READ FPDMA QUEUED
Jan 30 23:09:50 fork kernel: ata7.00: cmd 60/01:40:63:00:00/00:00:00:00:00/40 tag 8 ncq dma 512 in
Jan 30 23:09:50 fork kernel:         res 40/00:58:65:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Jan 30 23:09:50 fork kernel: ata7.00: status: { DRDY }
Jan 30 23:09:50 fork kernel: ata7.00: failed command: READ FPDMA QUEUED
Jan 30 23:09:50 fork kernel: ata7.00: cmd 60/08:48:d0:00:00/00:00:00:00:00/40 tag 9 ncq dma 4096 in
Jan 30 23:09:50 fork kernel:         res 40/00:58:65:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Jan 30 23:09:50 fork kernel: ata7.00: status: { DRDY }
Jan 30 23:09:50 fork kernel: ata7.00: failed command: READ FPDMA QUEUED
Jan 30 23:09:50 fork kernel: ata7.00: cmd 60/01:50:67:00:00/00:00:00:00:00/40 tag 10 ncq dma 512 in
Jan 30 23:09:50 fork kernel:         res 40/00:58:65:00:00/00:00:

 

Thanks in advance!

Daniel

 

 

Edited January 31, 2021 by dptech21
update

[Squid]

Reseat all the sata and power cables.

 

Also, you can directly attach the diagnostics to the posts. 

[dptech21]

Looks like the errors were non-impactful. I did change out the SATA cable for the drive throwing the errors. But honestly I think the source of the problem was pulling a data and a parity drive at the same time and letting it rebuild from the second parity. 

 

At this time the array is green and the drive with the errors is syncing as the second parity once more.

 

I will repost if there is an issue.

 

Thanks!