I'm pretty new to Unraid, this is my first build out and I've been tinkering for a few months.   I have an array with 7 3TB drives and 1 3TB parity drive. Recently drive 6 had failed so I purchased two 4TB drives, one to replace drive 6 and one to replace the parity drive.  I am following the Parity Swap Procedure documented here...

 

https://wiki.unraid.net/The_parity_swap_procedure

 

The procedure is failing on step 14 "Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Copy button"

It seems that the copy is failing after about 30 minutes.  Here is the log...

 

Dec 3 06:40:24 Tower emhttpd: copy: disk6 to disk0 running
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 Sense Key : 0x3 [current] [descriptor]
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 ASC=0x11 ASCQ=0x0
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 CDB: opcode=0x7f, sa=0x9
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Dec 3 07:13:52 Tower kernel: sd 5:0:2:0: [sdd] tag#1369 CDB[10]: 25 46 c2 40 25 46 c2 40 00 00 00 00 00 00 04 00
Dec 3 07:13:52 Tower kernel: print_req_error: critical medium error, dev sdd, sector 625394723
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 Sense Key : 0x3 [current] [descriptor]
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 ASC=0x11 ASCQ=0x0
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 CDB: opcode=0x7f, sa=0x9
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Dec 3 07:13:55 Tower kernel: sd 5:0:2:0: [sdd] tag#1791 CDB[10]: 25 46 c4 23 25 46 c4 23 00 00 00 00 00 00 00 01
Dec 3 07:13:55 Tower kernel: print_req_error: critical medium error, dev sdd, sector 625394723
Dec 3 07:13:55 Tower kernel: Buffer I/O error on dev sdd1, logical block 625394659, async page read
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 Sense Key : 0x3 [current] [descriptor]
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 ASC=0x11 ASCQ=0x0
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 CDB: opcode=0x7f, sa=0x9
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Dec 3 07:13:57 Tower kernel: sd 5:0:2:0: [sdd] tag#1816 CDB[10]: 25 46 c4 23 25 46 c4 23 00 00 00 00 00 00 00 01
Dec 3 07:13:57 Tower kernel: print_req_error: critical medium error, dev sdd, sector 625394723
Dec 3 07:13:57 Tower kernel: Buffer I/O error on dev sdd1, logical block 625394659, async page read
Dec 3 07:13:57 Tower emhttpd: error: pswap_dsbl_copy, 5907: Input/output error (5): read: /dev/sdd1

 

"Dev SSD" is the old parity drive.  How bad is this? Am I going to lose all of my data? Does anyone have anything they can recommend?  Please let me know if you need any further info from me.  Thank you in advance for any assistance you can offer.

 

Diagnostics attached...

 

tower-diagnostics-20201203-0731.zip

Can I go back to using the original 3TB parity drive and rebuild drive 6 with a new 3TB drive? Once I get drive 6 working, then try to replace the now failing 3TB parity drive?  Once everything is working then worry about possibly upgrading to the 4TB drives? 

 

Can I replace a 3Tb drive with a 4TB drive if my parity is only 3TB, can I limit the 4TB drive to only use 3TB?

 

 

Old parity is also failing, so you have two failing disks with single parity, is old disk6 still connected? If not connect it and post a SMART report.