Hi,

 

I got some files on disk2 that I could not copy. I got massive read errors, so I decided to replace this drive (3Tb) with a new one (4Tb). I knew I had good parity from the last check.

 

However, during the rebuild I got 768 errors on disk 8. I got following errors in the syslog:

 

Feb 22 23:32:04 Norco_Tower kernel: sd 0:0:2:0: [sdc] Unhandled sense code

Feb 22 23:32:04 Norco_Tower kernel: sd 0:0:2:0: [sdc]  Result: hostbyte=0x00 driverbyte=0x08

Feb 22 23:32:04 Norco_Tower kernel: sd 0:0:2:0: [sdc]  Sense Key : 0x3 [current]

Feb 22 23:32:04 Norco_Tower kernel: Info fld=0x353608a0

Feb 22 23:32:04 Norco_Tower kernel: sd 0:0:2:0: [sdc]  ASC=0x11 ASCQ=0x0

Feb 22 23:32:04 Norco_Tower kernel: sd 0:0:2:0: [sdc] CDB: cdb[0]=0x28: 28 00 35 36 06 a0 00 04 00 00

Feb 22 23:32:04 Norco_Tower kernel: end_request: critical target error, dev sdc, sector 892733088

Feb 22 23:32:04 Norco_Tower kernel: md: disk8 read error

Feb 22 23:32:04 Norco_Tower kernel: handle_stripe read error: 892733024/8, count: 1

Feb 22 23:32:04 Norco_Tower kernel: md: parity incorrect: 892733024

Feb 22 23:32:04 Norco_Tower kernel: md: disk8 read error

Feb 22 23:32:04 Norco_Tower kernel: handle_stripe read error: 892733032/8, count: 1

Feb 22 23:32:04 Norco_Tower kernel: md: parity incorrect: 892733032

Feb 22 23:32:04 Norco_Tower kernel: md: disk8 read error

Feb 22 23:32:04 Norco_Tower kernel: handle_stripe read error: 892733040/8, count: 1

Feb 22 23:32:04 Norco_Tower kernel: md: parity incorrect: 892733040

Feb 22 23:32:04 Norco_Tower kernel: md: disk8 read error

Feb 22 23:32:04 Norco_Tower kernel: handle_stripe read error: 892733048/8, count: 1

Feb 22 23:32:04 Norco_Tower kernel: md: parity incorrect: 892733048

Feb 22 23:32:04 Norco_Tower kernel: md: disk8 read error

etc....

 

Got this type of error 6 times (Unhandled sense code). See attached syslog.

 

 

 

Now my worry is:

 

Is disk2 correctly rebuild? In other words, did unraid eventually correctly read disk 8 and thus rebuild disk 2 correctly? I assume yes because:

Feb 23 13:43:01 Norco_Tower kernel: md: sync done. time=57036sec

Feb 23 13:43:02 Norco_Tower kernel: md: recovery thread sync completion status: 0

 

 

If no, how can I see which files are affected  using the affected blocks (ie sector 892733088).

 

I did not yet do a parity rebuild. Can I do this now. I want to replace also disk8.

 

Please advice.

 

Thanks

syslog.zip

Nobody has an idea if rebuild was correct? I can just start checking parity without worrying if files are corrupt?

 

Disk2 was rebuilt with errors. I know of no way to determine which files may be corrupt. The errors may occur on an unused portion of the disk depending on disk utilization. To be certain restore disk2 from backup. If the content is music or video the errors may only be noticeable as momentary static.