Odd one.

 

The moment I start a parity sync I start getting errors in the logs as seen below. If I remove parity drives and bring the array online it works without errors. if i add the two parity drives to the normal array they work as well.

 

This is the new RC6

 

Parity says it will take 20-30 days to complete right now.

 

Could this be due to a poor power supply?

 

It now disabled one of my parity drives and the other one is going full speed. I thought it was a bad drive but I have changed the drives already and the same thing happens.

 

Nov 16 18:25:23 NAS1 sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237
Nov 16 18:25:27 NAS1 kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 16 18:25:27 NAS1 kernel: ata9.00: supports DRM functions and may not be fully accessible
Nov 16 18:25:27 NAS1 kernel: ata9.00: supports DRM functions and may not be fully accessible
Nov 16 18:25:27 NAS1 kernel: ata9.00: configured for UDMA/133
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed to read SCR 1 (Emask=0x40)
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed to read SCR 1 (Emask=0x40)
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed to read SCR 1 (Emask=0x40)
Nov 16 18:25:28 NAS1 kernel: ata14.00: exception Emask 0x100 SAct 0x92490 SErr 0x0 action 0x6 frozen
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/40:20:c0:7f:00/05:00:00:00:00/40 tag 4 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/40:38:00:85:00/05:00:00:00:00/40 tag 7 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/40:50:40:8a:00/05:00:00:00:00/40 tag 10 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/40:68:80:8f:00/05:00:00:00:00/40 tag 13 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/40:80:c0:94:00/05:00:00:00:00/40 tag 16 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.00: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.00: cmd 60/80:98:00:9a:00/00:00:00:00:00/40 tag 19 ncq dma 65536 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b0:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.00: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.01: exception Emask 0x100 SAct 0x124900 SErr 0x0 action 0x6 frozen
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.01: cmd 60/40:40:00:85:00/05:00:00:00:00/40 tag 8 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.01: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.01: cmd 60/40:58:40:8a:00/05:00:00:00:00/40 tag 11 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.01: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.01: cmd 60/40:70:80:8f:00/05:00:00:00:00/40 tag 14 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.01: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.01: cmd 60/40:88:c0:94:00/05:00:00:00:00/40 tag 17 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.01: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.01: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.01: cmd 60/80:a0:00:9a:00/00:00:00:00:00/40 tag 20 ncq dma 65536 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:b8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.01: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: exception Emask 0x100 SAct 0x249240 SErr 0x0 action 0x6 frozen
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/40:30:c0:7f:00/05:00:00:00:00/40 tag 6 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/40:48:00:85:00/05:00:00:00:00/40 tag 9 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/40:60:40:8a:00/05:00:00:00:00/40 tag 12 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/40:78:80:8f:00/05:00:00:00:00/40 tag 15 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/40:90:c0:94:00/05:00:00:00:00/40 tag 18 ncq dma 688128 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:28 NAS1 kernel: ata14.02: failed command: READ FPDMA QUEUED
Nov 16 18:25:28 NAS1 kernel: ata14.02: cmd 60/80:a8:00:9a:00/00:00:00:00:00/40 tag 21 ncq dma 65536 in
Nov 16 18:25:28 NAS1 kernel:         res 40/00:f8:30:76:72/00:00:74:00:00/40 Emask 0x100 (unknown error)
Nov 16 18:25:28 NAS1 kernel: ata14.02: status: { DRDY }
Nov 16 18:25:38 NAS1 kernel: ata14.15: softreset failed (1st FIS failed)
 

Edited November 18, 20196 yr by Jayman6014

I have a 750W PSU coming,  right now I got a 600 but with overhead it is likely 530W

Please post the diagnostics: Tools -> Diagnostics

Logs attached.  Might not show what you want as I just rebooted it before posting this.  I suspect you want me to make it spit out all the errors and post that log. If thats the case let me know.

nas1-diagnostics-20191117-1320.zip

16 hours ago, johnnie.black said:

Please post the diagnostics: Tools -> Diagnostics

Well I think I found my issue. I got one of these cards and it worked for awhile but now when it runs a parity build the runs the drives hard at the same time the card just goes sideways and in the end takes 6 drives offline.

I guess my fault for going cheap on the PCI-E Sata Card.

Diags are after rebooting, but yes, likely the Marvell controller with SATA port multiplier, those are a double no no.

14 hours ago, johnnie.black said:

Diags are after rebooting, but yes, likely the Marvell controller with SATA port multiplier, those are a double no no.

Yeah ordered a LSI from Ebay from Art of Server.