Array Won't Start -- No Maintenance Mode Option [6.8.3]

[Officero]

Parity drive had 500-2000 errors (can't remember) after a check. Started parity rebuild/resync and now the array is offline and I can't restart it. Diagnostics attached.

 

Unraid Version 6.8.3. Docker apps: SABNzbd, Sonarr, Radarr, Tautulli, Nextcloud, MariaDB, Plex

 

Inventec mobo w/ majority WD 8tb HDDs

 

E31260L CPU

 

Any help is appreciated. Thanks!

 

tower-diagnostics-20210204-1503.zip

Edited February 5, 2021 by Officero

[JorgeB]

Replace cables on disk1 then post new diags.

[Officero]

Must've been some hang up in the GUI? I restarted and everything is green, no errors. This was the parity result:

 

"Last check completed on Thu 04 Feb 2021 07:23:20 AM CST (yesterday), finding 0 errors.
Duration: 18 hours, 2 minutes, 20 seconds. Average speed: 123.2 MB/sec"

[JorgeB]

2 hours ago, Officero said:

Must've been some hang up in the GUI?

No, there were constant ATA errors on disk1:

 

Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:10:d8:86:b8/04:00:70:00:00/40 tag 2 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/f8:18:d8:8a:b8/03:00:70:00:00/40 tag 3 ncq dma 520192 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:20:d0:8e:b8/04:00:70:00:00/40 tag 4 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bu

 

Most likely a power/connection problem.

[Officero]

8 minutes ago, JorgeB said:

No, there were constant ATA errors on disk1:

 

Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:10:d8:86:b8/04:00:70:00:00/40 tag 2 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/f8:18:d8:8a:b8/03:00:70:00:00/40 tag 3 ncq dma 520192 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:20:d0:8e:b8/04:00:70:00:00/40 tag 4 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bu

 

Most likely a power/connection problem.

 

Got it--thank you. I'll replace the power connection and see how it goes, then replace the connection later if there are still issues. Thanks again.

[Officero]

On 2/5/2021 at 11:25 AM, JorgeB said:

No, there were constant ATA errors on disk1:

 

Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:10:d8:86:b8/04:00:70:00:00/40 tag 2 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/f8:18:d8:8a:b8/03:00:70:00:00/40 tag 3 ncq dma 520192 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bus error)
Jan  1 04:42:48 Tower kernel: ata5.00: status: { DRDY }
Jan  1 04:42:48 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan  1 04:42:48 Tower kernel: ata5.00: cmd 60/00:20:d0:8e:b8/04:00:70:00:00/40 tag 4 ncq dma 524288 in
Jan  1 04:42:48 Tower kernel:         res 40/00:00:d8:82:b8/00:00:70:00:00/40 Emask 0x10 (ATA bu

 

Most likely a power/connection problem.

 

I replaced the SATA cable. I believe the same issue persists. I skimmed the logs and saw the same ATA bus error. I will try one more cable and then I will try power. 

tower-diagnostics-20210309-0842.zip