Hi All and thanks for reading,

 

My original parity was a 6TB Seagate Ironwolf which started getting UDMA errors ......

Sent the disk back to Seagate direct, which they replaced with an '8TB Pro Ironwolf Recertified Disk' ..... as they had no 6TB available for replacement.

 

Checked this morning 29th Jan 2020 to find that this 'new' parity show on the GUI as "PARITY DEVICE IS DISABLED" and tha the drive has write errors..

The disk log infomatation Shows:

 

ErrorWarningSystemArray

Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] 4096-byte physical blocks
Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Write Protect is off
Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Mode Sense: 7f 00 10 08
Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 27 11:16:16 Tower-02 kernel: sdd: sdd1
Jan 27 11:16:16 Tower-02 kernel: sd 2:0:1:0: [sdd] Attached SCSI disk
Jan 27 11:16:33 Tower-02 emhttpd: ST8000NE0021-2EN112_ZA184WJY (sdd) 512 15628053168
Jan 27 11:16:33 Tower-02 kernel: mdcmd (1): import 0 sdd 64 7814026532 0 ST8000NE0021-2EN112_ZA184WJY
Jan 27 11:16:33 Tower-02 kernel: md: import disk0: (sdd) ST8000NE0021-2EN112_ZA184WJY size: 7814026532
Jan 27 11:16:36 Tower-02 root: /usr/sbin/wsdd
Jan 27 11:16:38 Tower-02 emhttpd: shcmd (25): /usr/local/sbin/set_ncq sdd 1
Jan 27 11:16:38 Tower-02 root: set_ncq: setting sdd queue_depth to 1
Jan 27 11:16:38 Tower-02 emhttpd: shcmd (26): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 27 11:25:43 Tower-02 emhttpd: shcmd (595): /usr/local/sbin/set_ncq sdd 1
Jan 27 11:25:43 Tower-02 emhttpd: shcmd (596): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 27 11:26:04 Tower-02 root: /usr/sbin/wsdd
Jan 27 19:18:10 Tower-02 emhttpd: shcmd (764): /usr/local/sbin/set_ncq sdd 1
Jan 27 19:18:10 Tower-02 emhttpd: shcmd (765): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 27 21:00:09 Tower-02 emhttpd: shcmd (790): /usr/local/sbin/set_ncq sdd 1
Jan 27 21:00:09 Tower-02 emhttpd: shcmd (791): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 27 21:00:10 Tower-02 emhttpd: shcmd (806): /usr/local/sbin/set_ncq sdd 1
Jan 27 21:00:10 Tower-02 emhttpd: shcmd (807): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 27 23:39:05 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#3341 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Jan 27 23:39:05 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#3341 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00
Jan 27 23:39:05 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 15628052992
Jan 28 15:35:34 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#612 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00
Jan 28 15:35:34 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#612 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 Sense Key : 0x2 [current]
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 ASC=0x4 ASCQ=0x0
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jan 28 15:35:35 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 0
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 Sense Key : 0x2 [current]
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 ASC=0x4 ASCQ=0x0
Jan 28 15:35:35 Tower-02 kernel: sd 2:0:1:0: [sdd] tag#613 CDB: opcode=0x8a 8a 08 00 00 00 00 74 75 45 78 00 00 00 08 00 00
Jan 28 15:35:35 Tower-02 kernel: print_req_error: I/O error, dev sdd, sector 1953842552
Jan 29 07:19:53 Tower-02 emhttpd: shcmd (1042): /usr/local/sbin/set_ncq sdd 1
Jan 29 07:19:53 Tower-02 emhttpd: shcmd (1043): echo 128 > /sys/block/sdd/queue/nr_requests
Jan 29 07:20:51 Tower-02 emhttpd: shcmd (1058): /usr/local/sbin/set_ncq sdd 1
Jan 29 07:20:51 Tower-02 emhttpd: shcmd (1059): echo 128 > /sys/block/sdd/queue/nr_requests

 

I've attached Sys log and Dia files, any help please ...

 

Regards ..

 

 

 

tower-02-diagnostics-20200129-0719.zip tower-02-syslog-20200129-0711.zip

Disk looks fine, but there are already a lot of UDMA CRC errors, these are a connection problem, usually a bad SATA cable.

Hi johnnie.black, tee-tee jorge

 

Thanks for the reply

 

I had the errors building up on the previous disk (UDMA) that's why I sent it back for replacement (under warranty)..

When I got the replacement disk and after running 'Preclear' I installed the disk, unfortunately I forgot to change the 'sata' cable :-(

When I realised my mistake I cancelled 'Pclear' shut down the server, changed the cable, then the 'parity build' started again, with the "1032 UDMA errors" ..

 

Things have worked ok up to this morning, when I saw the message (via GUI) that the "PARITY DEVICE IS DISABLED" the question is "How do I go Forward"?

 

regards

 

 

18 minutes ago, numpkin said:

with the "1032 UDMA errors" ..

Currently there are more

199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    1238

So likely there's still a problem, swap ports with another disk and see if errors stop increasing.

Hi again johnnie.black

 

Don't know whats happening today :-) Old age I guess .....

 

I did think i'd put the correct number of errors, you are correct "1238" is what I should have typed sorry ....

 

regards

 

 

OK, in that case suggest swapping both cables (or slot) with another disk to rule that out and then re-sync parity.