paulmorabi

Reseated the disk and re-connected the cables and its working. Fingers crossed it stays that way. Thank you!

Hi, Have noticed the above error. Fortunately, on my scratch disk so isn't affecting my main files. [7117583.530092] sd 5:0:1:0: [sdc] tag#565 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=1s [7117583.530098] sd 5:0:1:0: [sdc] tag#565 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 52 20 00 00 40 00 00 00 [7117583.530100] I/O error, dev sdc, sector 5897409056 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0 [7117583.530110] sd 5:0:1:0: [sdc] tag#566 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=1s [7117583.530113] sd 5:0:1:0: [sdc] tag#566 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 92 20 00 00 04 00 00 00 [7117583.530115] I/O error, dev sdc, sector 5897425440 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0 [7117583.530125] sd 5:0:1:0: [sdc] tag#567 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=1s [7117583.530128] sd 5:0:1:0: [sdc] tag#567 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 96 20 00 00 40 00 00 00 [7117583.530130] I/O error, dev sdc, sector 5897426464 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0 [7117583.530139] sd 5:0:1:0: [sdc] tag#568 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=1s [7117583.530144] sd 5:0:1:0: [sdc] tag#568 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 d6 20 00 00 3c 50 00 00 [7117583.530146] I/O error, dev sdc, sector 5897442848 op 0x0:(READ) flags 0x80700 phys_seg 122 prio class 0 [7117583.530194] sd 5:0:1:0: [sdc] tag#564 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=1s [7117583.530199] sd 5:0:1:0: [sdc] tag#564 Sense Key : 0x4 [current] [7117583.530201] sd 5:0:1:0: [sdc] tag#564 ASC=0x44 ASCQ=0x0 [7117583.530204] sd 5:0:1:0: [sdc] tag#564 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 12 80 00 00 3f a0 00 00 [7117583.530206] critical target error, dev sdc, sector 5897392768 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0 [7117584.123431] sd 5:0:1:0: [sdc] tag#534 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7117584.123438] sd 5:0:1:0: [sdc] tag#534 Sense Key : 0x4 [current] [7117584.123441] sd 5:0:1:0: [sdc] tag#534 ASC=0x44 ASCQ=0x0 [7117584.123444] sd 5:0:1:0: [sdc] tag#534 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 cd a0 00 00 00 80 00 00 [7117584.123446] critical target error, dev sdc, sector 5897440672 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7117584.123531] sd 5:0:1:0: [sdc] tag#535 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7117584.123537] sd 5:0:1:0: [sdc] tag#535 Sense Key : 0x4 [current] [7117584.123540] sd 5:0:1:0: [sdc] tag#535 ASC=0x44 ASCQ=0x0 [7117584.123543] sd 5:0:1:0: [sdc] tag#535 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 cd a0 00 00 00 80 00 00 [7117584.123546] critical target error, dev sdc, sector 5897440672 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7117584.354715] sd 5:0:1:0: [sdc] tag#575 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7117584.354724] sd 5:0:1:0: [sdc] tag#575 Sense Key : 0x4 [current] [7117584.354727] sd 5:0:1:0: [sdc] tag#575 ASC=0x44 ASCQ=0x0 [7117584.354730] sd 5:0:1:0: [sdc] tag#575 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 ed a0 00 00 00 80 00 00 [7117584.354733] critical target error, dev sdc, sector 5897448864 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7117584.354813] sd 5:0:1:0: [sdc] tag#513 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7117584.354822] sd 5:0:1:0: [sdc] tag#513 Sense Key : 0x4 [current] [7117584.354826] sd 5:0:1:0: [sdc] tag#513 ASC=0x44 ASCQ=0x0 [7117584.354829] sd 5:0:1:0: [sdc] tag#513 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 ed a0 00 00 00 80 00 00 [7117584.354832] critical target error, dev sdc, sector 5897448864 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7117584.370181] sd 5:0:1:0: [sdc] tag#562 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7117584.370187] sd 5:0:1:0: [sdc] tag#562 Sense Key : 0x4 [current] [7117584.370189] sd 5:0:1:0: [sdc] tag#562 ASC=0x44 ASCQ=0x0 [7117584.370192] sd 5:0:1:0: [sdc] tag#562 CDB: opcode=0x88 88 00 00 00 00 01 5f 83 ee a0 00 00 00 80 00 00 [7117584.370194] critical target error, dev sdc, sector 5897449120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.890345] scsi_io_completion_action: 19 callbacks suppressed [7120741.890352] sd 5:0:1:0: [sdc] tag#750 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.890357] sd 5:0:1:0: [sdc] tag#750 Sense Key : 0x4 [current] [7120741.890360] sd 5:0:1:0: [sdc] tag#750 ASC=0x44 ASCQ=0x0 [7120741.890363] sd 5:0:1:0: [sdc] tag#750 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 93 c0 00 00 00 80 00 00 [7120741.890364] blk_print_req_error: 19 callbacks suppressed [7120741.890366] critical target error, dev sdc, sector 5890085824 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 0 [7120741.890405] sd 5:0:1:0: [sdc] tag#751 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.890408] sd 5:0:1:0: [sdc] tag#751 Sense Key : 0x4 [current] [7120741.890410] sd 5:0:1:0: [sdc] tag#751 ASC=0x44 ASCQ=0x0 [7120741.890412] sd 5:0:1:0: [sdc] tag#751 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 93 c0 00 00 00 08 00 00 [7120741.890414] critical target error, dev sdc, sector 5890085824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.890480] sd 5:0:1:0: [sdc] tag#752 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.890485] sd 5:0:1:0: [sdc] tag#752 Sense Key : 0x4 [current] [7120741.890487] sd 5:0:1:0: [sdc] tag#752 ASC=0x44 ASCQ=0x0 [7120741.890490] sd 5:0:1:0: [sdc] tag#752 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 93 c0 00 00 00 08 00 00 [7120741.890492] critical target error, dev sdc, sector 5890085824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.914672] sd 5:0:1:0: [sdc] tag#747 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.914678] sd 5:0:1:0: [sdc] tag#747 Sense Key : 0x4 [current] [7120741.914681] sd 5:0:1:0: [sdc] tag#747 ASC=0x44 ASCQ=0x0 [7120741.914684] sd 5:0:1:0: [sdc] tag#747 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 c0 00 00 00 20 00 00 [7120741.914687] critical target error, dev sdc, sector 5890094016 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [7120741.914729] sd 5:0:1:0: [sdc] tag#748 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.914733] sd 5:0:1:0: [sdc] tag#748 Sense Key : 0x4 [current] [7120741.914735] sd 5:0:1:0: [sdc] tag#748 ASC=0x44 ASCQ=0x0 [7120741.914738] sd 5:0:1:0: [sdc] tag#748 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 c0 00 00 00 08 00 00 [7120741.914740] critical target error, dev sdc, sector 5890094016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.914797] sd 5:0:1:0: [sdc] tag#749 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.914801] sd 5:0:1:0: [sdc] tag#749 Sense Key : 0x4 [current] [7120741.914803] sd 5:0:1:0: [sdc] tag#749 ASC=0x44 ASCQ=0x0 [7120741.914806] sd 5:0:1:0: [sdc] tag#749 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 c0 00 00 00 08 00 00 [7120741.914808] critical target error, dev sdc, sector 5890094016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.928152] sd 5:0:1:0: [sdc] tag#745 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.928157] sd 5:0:1:0: [sdc] tag#745 Sense Key : 0x4 [current] [7120741.928160] sd 5:0:1:0: [sdc] tag#745 ASC=0x44 ASCQ=0x0 [7120741.928163] sd 5:0:1:0: [sdc] tag#745 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 e0 00 00 00 20 00 00 [7120741.928165] critical target error, dev sdc, sector 5890094048 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [7120741.928213] sd 5:0:1:0: [sdc] tag#746 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.928216] sd 5:0:1:0: [sdc] tag#746 Sense Key : 0x4 [current] [7120741.928218] sd 5:0:1:0: [sdc] tag#746 ASC=0x44 ASCQ=0x0 [7120741.928221] sd 5:0:1:0: [sdc] tag#746 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 e0 00 00 00 08 00 00 [7120741.928222] critical target error, dev sdc, sector 5890094048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.928298] sd 5:0:1:0: [sdc] tag#755 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.928306] sd 5:0:1:0: [sdc] tag#755 Sense Key : 0x4 [current] [7120741.928309] sd 5:0:1:0: [sdc] tag#755 ASC=0x44 ASCQ=0x0 [7120741.928312] sd 5:0:1:0: [sdc] tag#755 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b3 e0 00 00 00 08 00 00 [7120741.928315] critical target error, dev sdc, sector 5890094048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7120741.941944] sd 5:0:1:0: [sdc] tag#741 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7120741.941953] sd 5:0:1:0: [sdc] tag#741 Sense Key : 0x4 [current] [7120741.941958] sd 5:0:1:0: [sdc] tag#741 ASC=0x44 ASCQ=0x0 [7120741.941962] sd 5:0:1:0: [sdc] tag#741 CDB: opcode=0x88 88 00 00 00 00 01 5f 13 b4 00 00 00 00 60 00 00 [7120741.941968] critical target error, dev sdc, sector 5890094080 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [7121105.145490] scsi_io_completion_action: 34 callbacks suppressed [7121105.145506] sd 5:0:1:0: [sdc] tag#710 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.145512] sd 5:0:1:0: [sdc] tag#710 Sense Key : 0x4 [current] [7121105.145516] sd 5:0:1:0: [sdc] tag#710 ASC=0x44 ASCQ=0x0 [7121105.145520] sd 5:0:1:0: [sdc] tag#710 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.145522] blk_print_req_error: 34 callbacks suppressed [7121105.145527] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 3 prio class 0 [7121105.145555] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.145717] sd 5:0:1:0: [sdc] tag#711 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.145722] sd 5:0:1:0: [sdc] tag#711 Sense Key : 0x4 [current] [7121105.145726] sd 5:0:1:0: [sdc] tag#711 ASC=0x44 ASCQ=0x0 [7121105.145729] sd 5:0:1:0: [sdc] tag#711 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.145735] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0 [7121105.145794] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.146523] sd 5:0:1:0: [sdc] tag#721 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.146529] sd 5:0:1:0: [sdc] tag#721 Sense Key : 0x4 [current] [7121105.146532] sd 5:0:1:0: [sdc] tag#721 ASC=0x44 ASCQ=0x0 [7121105.146535] sd 5:0:1:0: [sdc] tag#721 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.146538] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 [7121105.146555] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.146681] sd 5:0:1:0: [sdc] tag#722 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.146686] sd 5:0:1:0: [sdc] tag#722 Sense Key : 0x4 [current] [7121105.146689] sd 5:0:1:0: [sdc] tag#722 ASC=0x44 ASCQ=0x0 [7121105.146692] sd 5:0:1:0: [sdc] tag#722 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.146695] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0 [7121105.146711] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.147030] sd 5:0:1:0: [sdc] tag#723 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.147034] sd 5:0:1:0: [sdc] tag#723 Sense Key : 0x4 [current] [7121105.147037] sd 5:0:1:0: [sdc] tag#723 ASC=0x44 ASCQ=0x0 [7121105.147039] sd 5:0:1:0: [sdc] tag#723 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.147041] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 3 prio class 0 [7121105.147054] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.147169] sd 5:0:1:0: [sdc] tag#724 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.147172] sd 5:0:1:0: [sdc] tag#724 Sense Key : 0x4 [current] [7121105.147175] sd 5:0:1:0: [sdc] tag#724 ASC=0x44 ASCQ=0x0 [7121105.147177] sd 5:0:1:0: [sdc] tag#724 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.147179] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 [7121105.147194] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.147470] sd 5:0:1:0: [sdc] tag#725 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.147474] sd 5:0:1:0: [sdc] tag#725 Sense Key : 0x4 [current] [7121105.147476] sd 5:0:1:0: [sdc] tag#725 ASC=0x44 ASCQ=0x0 [7121105.147479] sd 5:0:1:0: [sdc] tag#725 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.147481] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 [7121105.147495] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7121105.147609] sd 5:0:1:0: [sdc] tag#726 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7121105.147612] sd 5:0:1:0: [sdc] tag#726 Sense Key : 0x4 [current] [7121105.147614] sd 5:0:1:0: [sdc] tag#726 ASC=0x44 ASCQ=0x0 [7121105.147616] sd 5:0:1:0: [sdc] tag#726 CDB: opcode=0x88 88 00 00 00 00 00 af 2e e2 80 00 00 00 20 00 00 [7121105.147618] critical target error, dev sdc, sector 2939085440 op 0x0:(READ) flags 0x1000 phys_seg 3 prio class 0 [7121105.147631] XFS (sdc1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0xaf2ee240 len 32 error 121 [7122521.670756] sd 5:0:1:0: [sdc] tag#894 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.670767] sd 5:0:1:0: [sdc] tag#894 Sense Key : 0x4 [current] [7122521.670770] sd 5:0:1:0: [sdc] tag#894 ASC=0x44 ASCQ=0x0 [7122521.670774] sd 5:0:1:0: [sdc] tag#894 CDB: opcode=0x88 88 00 00 00 00 01 5f 29 f9 10 00 00 00 80 00 00 [7122521.670776] critical target error, dev sdc, sector 5891553552 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 0 [7122521.670818] sd 5:0:1:0: [sdc] tag#832 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.670824] sd 5:0:1:0: [sdc] tag#832 Sense Key : 0x4 [current] [7122521.670827] sd 5:0:1:0: [sdc] tag#832 ASC=0x44 ASCQ=0x0 [7122521.670829] sd 5:0:1:0: [sdc] tag#832 CDB: opcode=0x88 88 00 00 00 00 01 5f 29 f9 10 00 00 00 08 00 00 [7122521.670832] critical target error, dev sdc, sector 5891553552 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.670909] sd 5:0:1:0: [sdc] tag#833 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.670914] sd 5:0:1:0: [sdc] tag#833 Sense Key : 0x4 [current] [7122521.670916] sd 5:0:1:0: [sdc] tag#833 ASC=0x44 ASCQ=0x0 [7122521.670919] sd 5:0:1:0: [sdc] tag#833 CDB: opcode=0x88 88 00 00 00 00 01 5f 29 f9 10 00 00 00 08 00 00 [7122521.670921] critical target error, dev sdc, sector 5891553552 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.695413] sd 5:0:1:0: [sdc] tag#865 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.695418] sd 5:0:1:0: [sdc] tag#865 Sense Key : 0x4 [current] [7122521.695422] sd 5:0:1:0: [sdc] tag#865 ASC=0x44 ASCQ=0x0 [7122521.695424] sd 5:0:1:0: [sdc] tag#865 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 d8 00 00 00 20 00 00 [7122521.695427] critical target error, dev sdc, sector 5860739544 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [7122521.695480] sd 5:0:1:0: [sdc] tag#866 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.695483] sd 5:0:1:0: [sdc] tag#866 Sense Key : 0x4 [current] [7122521.695486] sd 5:0:1:0: [sdc] tag#866 ASC=0x44 ASCQ=0x0 [7122521.695488] sd 5:0:1:0: [sdc] tag#866 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 d8 00 00 00 08 00 00 [7122521.695490] critical target error, dev sdc, sector 5860739544 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.695565] sd 5:0:1:0: [sdc] tag#867 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.695570] sd 5:0:1:0: [sdc] tag#867 Sense Key : 0x4 [current] [7122521.695574] sd 5:0:1:0: [sdc] tag#867 ASC=0x44 ASCQ=0x0 [7122521.695576] sd 5:0:1:0: [sdc] tag#867 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 d8 00 00 00 08 00 00 [7122521.695578] critical target error, dev sdc, sector 5860739544 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.708410] sd 5:0:1:0: [sdc] tag#842 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.708417] sd 5:0:1:0: [sdc] tag#842 Sense Key : 0x4 [current] [7122521.708420] sd 5:0:1:0: [sdc] tag#842 ASC=0x44 ASCQ=0x0 [7122521.708423] sd 5:0:1:0: [sdc] tag#842 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 f8 00 00 00 20 00 00 [7122521.708427] critical target error, dev sdc, sector 5860739576 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [7122521.708469] sd 5:0:1:0: [sdc] tag#843 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.708472] sd 5:0:1:0: [sdc] tag#843 Sense Key : 0x4 [current] [7122521.708475] sd 5:0:1:0: [sdc] tag#843 ASC=0x44 ASCQ=0x0 [7122521.708478] sd 5:0:1:0: [sdc] tag#843 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 f8 00 00 00 08 00 00 [7122521.708480] critical target error, dev sdc, sector 5860739576 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.708548] sd 5:0:1:0: [sdc] tag#844 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.708555] sd 5:0:1:0: [sdc] tag#844 Sense Key : 0x4 [current] [7122521.708558] sd 5:0:1:0: [sdc] tag#844 ASC=0x44 ASCQ=0x0 [7122521.708561] sd 5:0:1:0: [sdc] tag#844 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 c9 f8 00 00 00 08 00 00 [7122521.708563] critical target error, dev sdc, sector 5860739576 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [7122521.721042] sd 5:0:1:0: [sdc] tag#877 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7122521.721051] sd 5:0:1:0: [sdc] tag#877 Sense Key : 0x4 [current] [7122521.721054] sd 5:0:1:0: [sdc] tag#877 ASC=0x44 ASCQ=0x0 [7122521.721057] sd 5:0:1:0: [sdc] tag#877 CDB: opcode=0x88 88 00 00 00 00 01 5d 53 ca 18 00 00 00 60 00 00 [7122521.721059] critical target error, dev sdc, sector 5860739608 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [7124899.594446] scsi_io_completion_action: 33 callbacks suppressed [7124899.594453] sd 5:0:1:0: [sdc] tag#875 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s [7124899.594459] sd 5:0:1:0: [sdc] tag#875 Sense Key : 0x4 [current] [7124899.594462] sd 5:0:1:0: [sdc] tag#875 ASC=0x44 ASCQ=0x0 [7124899.594464] sd 5:0:1:0: [sdc] tag#875 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 [7124899.594468] blk_print_req_error: 33 callbacks suppressed [7124899.594469] critical target error, dev sdc, sector 1954053744 op 0x1:(WRITE) flags 0x29800 phys_seg 1 prio class 0 [7124899.594491] XFS (sdc1): log I/O error -121 [7124899.594518] XFS (sdc1): Filesystem has been shut down due to log error (0x2). [7124899.594582] XFS (sdc1): Please unmount the filesystem and rectify the problem(s). I stopped the array to run xfs_repair and got the following: root@Tower:~# xfs_repair -v /dev/sdc Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval 0 fatal error -- Success Rebooted and now the disk is not detected. There were no smart errors previously. Diagnostics attached. Is my disk completely dead? tower-diagnostics-20251101-0707.zip

I only have one pci slot but I have removed the riser cable so maybe that could fix it? I can't see the same error in the logs. Thus far. The read errors were in the millions and I think crashed Unraid on one of the rebuild attempts. The snippet you posted above is from the rebuild attempt before I removed the riser cable and connected the HBA card directly to the pci slot. That too started to show a lot of read errors but I stopped it, removed the riser cable and started again. Thus far, ~4 hours to go, its ok and no errors on rebuilding.

here you go. Thanks. I had the LSI card connected to a PCI riser cable. As part of the rebuild, I removed that and connected it directly to the main board. Current pre-clear is still running and no errors so far. About 2/3 way through which is as far as its gotten before. If I get errors again, then I'll try replacing the card. The strange thing is the errors after after a period of time, not immediately and possibly related to high array activity (during parity check/rebuild). amiga-diagnostics-20250705-0544.zip

I've rebuilt - unplugged everything and reseated/connected. I also got two new drives. Started a pre-clear and it seems to work fine for a couple of hours and then overwhelmed with read errors from all drives. I am thinking it is possibly the LSI card itself. I got it from China originally and its 1.5 years old.

ok, unplugged and re-connected everything. Diagnostics attached. No errors so far but the disks are idle and I didn't start a check. amiga-diagnostics-20250701-1431.zip

Woke up to a surprise in that one of the disks on my array had errors. I tried to take disk2 out of the array, restart and re-add but immediately got an error so removed it. Then, as its first day of the month, the parity check started and I noticed the logs filled with read errors for disk3. I've stopped the parity check and have ordered replacement drives. While /dev/sdc (formerly disk2) shows a smart error, I can't see anything wrong with disk3? And for rebuilding the array, given one disk is completely out of action, and the other is full of read errors, any recommended steps for how to start the rebuild process? Should I attempt a rebuild by replacing disk2 and then if that succeeds, replace disk3? EDIT: I can mount disk2 (now of out of array) from unassigned devices. I guess the issue is how to now rebuild the array with replacement disks? Can I try to re-add disk2 to the array without reformatting it? Diagnostics attached. Any help very appreciated. amiga-diagnostics-20250701-0658.zip

Thank you. That worked. I will monitor and see if I get freezes from now onwards.

Thanks for replying. Yes, it looks like the docker.img and libvert.img (VM?) are located in system and are on disk6. Should this set set to cache only? Not sure how this came about as I've been using the same Unraid setup for several years. EDIT: Primary storage is set to cache and secondary storage now to none.

did you ever get anywhere with this? Having the same issue.

Hi, I've had a persistent problem with Unraid whereby a lot of disk activity seems to freeze the server and the dockers running on the Unraid host then become unresponsive. The containers running in a VM on the same system are fine as they are using isolated CPU cores. I've been searching for possible solutions but not found anything that solves it for me. Apart from the freezing during disk activity, everything else works fine. Diagnostics attached. I'd greatly appreciate any tips or possible solutions. tower-diagnostics-20250419-0813.zip

Thanks. I've amended as recommended above and will let you know how it goes.

Hi, I've noticed after upgrading to unraid 7.0 that after several days, NFS mounts seem to hang. It seems to happen every week or 10 days but never immediately after a reboot. If I try to reconnect or mount from another host, they also fail (the daemon doesn't seem to respond). I've tried restarting nfsd on Unraid but only a reboot seems to fix it. Attaching diagnostics. Is anyone else experiencing this issue? tower-diagnostics-20250210-1251.zip

Solution is here

Hi, I've setup Immich to run off of my Unraid server and when I went to do an update, I got the following error: Error: failed to register layer: write /usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.2.1: no space left on devic I can't see any devices that are full and from searching around, previous errors were caused by a lot of logging filling up /run which doesn't seem the case for me. Have attached diagnostics. Any help would be appreciated. amiga-diagnostics-20240809-1318.zip

Apologies for the late reply. I've been ordering NIC's and cables to test. Yes, you're correct it was a bad cable. All good now.

Hi, I've installed a 10GB NIC (using an Intel 82599) and have connected it via SFP+ to my router. I've been trying different things with the settings but have gotten nowhere with enabling it, apart from needing to remove network.cfg and try again. If I want to disable the onboard NIC and use the 10G NIC instead, my understanding is this needs to be set to eth0 and then disable bonding between the eth0 and 1. I've tried this but its made unraid inaccessible. Does anyone have more info on how to do this? diagnostics attached and many thanks in advance. tower-diagnostics-20231223-1538.zip

Perfect! That worked. Thank you!

I was holding on replying to see if some data would get written to the new disk. I've copied over a lot of files and still nothing added to disk 3. Is there anything I can do to prompt this or is it just a matter of waiting?

Hi, I've been doing some work rearranging disks on my array. In summary, I did the following: * Disk 3 was a scratch disk and not part of the media2 share. I excluded it specifically from media2. I removed it from the array and added it as a cache pool. * I added a new disk to my array and as this is the largest (20TB), made it the parity drive by removing the current disk and added it. Parity was successfully re-pgenerated. * I added the previous parity disk back to the array as disk 3. The pre-clear and formatting all worked and it was added. * I updated the media2 share to include all disks in the array (so including disk 3) After all this, I've started and stopped the array etc. but for whatever reason, it's not showing the extra space from the addition of the new drive (in terms of total capacity of the share and free space). The new disk, disk3 also seems to be empty of files so nothing is being copied there. Diagnostics is attached. Is there anything I can do to fix this? Should I remove it as disk3 and add as the next new disk? tower-diagnostics-20231121-1915.zip

Hmm on both systems the uid is 1000 and the "users" group gid is 100. Still though, if I chown to "paul:users" on Unraid, it gives me 99 and group users on the VM. This shouldn't be the case?

H, I've created a new cache and some files over to it. I have a Linux VM running that accesses the files by NFS and this is where the problems begin. I have a user paul and group users on both the Unraid machine and the Linux VM but the uid is I guess different. I can change the permissions so they are 777 and can then edit/remove files. The user is listed as 99 so its reflecting the UID of the "paul" user on the Unraid host? If I want to change the owner of the files on the VM to be the "paul" user within it, I get an operation not permitted error. Part of the reason I am looking to do this is because I am running several docker containers on the host and permissions are based off of it being this user. I'm using the public setting for the NFS share and the fstab entry for the share is as follows: I know its probably something simple here but have been searching for hours and endlessly confused.

Thanks. I don't have another disk handy so I am going to try moving the 4TB disk to a separate pool as this is the lone disk assigned to the downloads share. I've started backing up its contents to another share on the array. I will remove the disk from the current array (following these instructions) and then add it to its own pool. I understand this will format the data on the disk so I'll need to delete and recreate the downloads share on the new pool and then copy the stuff back over? Is that correct? EDIT: Above operation seems to have worked reducing the overall server load.

Thanks for this. I've just done the mover operation but there is no way to know its completed? The current downloads disk is 4TB and its a WD drive. My cache is currently 1TB. I knew this was an option but its probably too small for now. What does moving the downloads share to a new array entail and how does or can it improve performance? My final option is to move Plex to a separate host but its the last resort option, if possible.

I've noticed that a lot of disk activity on the array is causing Plex especially to hang and become very slow to complete unresponsive. This mostly happens when sabnzbd is decompressing files or they are being transferred to the share on the array by Sonarr/Radarr. When the two are happening together, everything slows to a crawl. I've tried a few different things - pinning cpu cores to Plex didn't do anything but tweaking sabnzbd to pause downloading while decompressing and use fewer threads as remediated the issue somewhat. Currently, I have my downloads/scratch disk as part of the array but it is its own share so not spread across disks. Can I take this out of the array and make it its own disk? Is there anything further I can do to eradicate this? Diagnostics attached. tower-diagnostics-20231112-1034.zip