Hi,
been Unraid user for 10+ years, from version 3 or 4 and now on 6.83.
One of my disks failed (disk2) and I started a repair from the parity by introducing a brand new disk; nothing new for me, did that in the past.
Now, during the rebuild the other disk #5 started reporting read errors:
Nov 15 22:21:08 Tower kernel: print_req_error: I/O error, dev sdg, sector 473325040
Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323952
Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323960
Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323968
Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323976......
with the total of 77,056 errors. The rebuild completed and all disks and array is green.
Now, I am running a parity check (with NO correction) and getting same read errors:
Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323952
Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323960
Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323968
Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323976.....
The parity check will complete in next couple of hours however not sure if I want to repeat the parity sync again with the correction or start looking for disk5 replacement?
The smart report for Disk5 is attached.
Please advise.
regards
Bobtower-smart-20221116-1259.zip