UhClem

Based on the info provided, I'm out of ideas.

Probably needs snapraid --test-force-content-write sync (instead of plain sync).

(Directly) after the snapraid -e fix command, you need to do a snapraid sync command (so that the "fixed" state is actually written to the content files).

(Directly) after the snapraid -e fix command, you need to do a snapraid sync command (so that the "fixed" state is actuqally written to the content files).

[Not certain on this -- I've got no errors, so can't test ...] Does snapraid -v -e check provide any info?

Sorry, but SnapRAID (and 99.999% of ALL programs) does not implement DWIM :):). Try --error-limit=0 (or -L0)

It's (Is it?) DejaVu all over again .... Link :) ::) This time, it's your DRU01 drive which SnapRAID has encountered a HARD error on, while verifying the correctness of the Content file it is in the final stage of writing to that drive I suggest that you rename that one snapraid.content.tmp file to "I_Contain_A_Bad_Sector"; all the other snapraid.content.tmp files you can delete. [If you were to delete the "bad-guy" one, then all of its sectors would be returned to the partition's free-space, and...

How can I replace disk4 without lose files on not bad sectors? Link Clarification: The Replacing instructions are intended for the situation where a WORKING disk is being replaced (typically with a larger disk). The Recovering section is for a failed/dysfunctional disk. [your situation]