While i agree with your statement here, i still think that is bad as solution, because:
-
I see no logic in what happened at all and why it’s not resolved with just
defaultsafterwards -
This doesn’t look like how auto-fsck failure mechanism should work
-
It looks a lot like either bug or system saying something like:
ok, there were some failure, so i’ve tried (not sure even how to check it?) to auto-fix problem, but now to remove warning regardless you need to set
rwor disable whole mechanismSo i’m afraid that problem is just still actually there

Hopefully someone else who may had previous experience could clarify what happened and what we maybe missing here…