January 31, 20242 yr Hi, I am looking for some assistance to identify whats going on with my new parity disk. Its hitting errors and being disbaled in unraid, I have already powered down the server and reseated the drive in a different bay just in case it was the ports that were causing the issue but I ran into the same issue when trying to rebuild the disk as parity again. Some of the errors can be seen below, I have also attached both the server diagnostics and I will attached the SMART extended self-test once it finishes. Can anyone help out at all? Thanks ```Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6716624 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 80 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6717648 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 84 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6718672 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 88 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6719696 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2``` monterrey-diagnostics-20240131-2126.zip Edited January 31, 20242 yr by Scoopsy13 details
January 31, 20242 yr Community Expert SMART looks OK so far. Disk gets disabled very soon after sync starts. Not clear if it's connection related. Usually more retries in syslog before write failure if it were.
February 2, 20242 yr Author I switched the drive to 3 different bays and on the 3rd try it seems to be rebuilding the parity now. Will most likely order replacement mini sas to sata cables. Will keep an eye on both the drive and the cables moving forward. Thanks for the help
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.