log full spammed with read error during parity sync

[caplam]

It's my backup server. it was running with 8 disks without parity. Today i added a parity disk and during parity sync it started throwing read errors on disk5.

I tried to cancel parity with no luck. i see reads (150MB/S) on disks 1,2,3,4,6,7,8 and nothing on parity and disk5.

disk 5 is sdg and in attributes i have:

-	Smartctl open device	/dev/sdg failed

all disks are btrfs formatted.

 

edit: disk5 also appear as sdk under unassigned devices

z620-diagnostics-20240702-1801.zip

Edited July 2 by caplam

[JorgeB]

Syslog rotated, and is missing the start of the problem, type reboot in the CLI then post new diags after array start.

[caplam]

i rebooted and parity sync started from scratch. No more read errors.

Smart attributes are fine.

I wonder if i could have caused that when closing the case.

 

edit: i forgot to enable syslog on backup server. I changed that. I now use my main server as syslog server.

z620-diagnostics-20240702-1848.zip

Edited July 2 by caplam

[JorgeB]

Everything looks Ok for now, and disk5 looks healthy, if it happens again I would replace the cables and try again.