On Thu, 2025-03-13 at 22:05 -0700, Dave Close wrote:"e2fsck -c" said it didn't find any bad blocks. If it didn't find any, why would it modify the card at all? "e2fsck -y" (by itself) did not report any problem.Perhaps it didn't. If the card was failing, a read operation could be enough to trigger another failure. It wouldn't matter what was doing the read.
I have a lot of experience with bad/flaky USB/SDCards- often they seem just fine as the onboard controller conceals signs of creeping-death, until they suddenly take a nose-dive.
I'm not sure about your case, but each time I run "e2fsck -v -c -y /dev/sde1" (note -v Verbose switch), the summary always reports "***** FILE SYSTEM WAS MODIFIED *****". So the filesystem IS being modified, but the media still mounts successfully in my case.
Do you see the same issue if you try other SDCards or USB
FlashDrives? Any difference if you format the media as plain ext2
vs ext4 FS? Any difference if you use "e2fsck -cc"
(Write+Read/Verify) test? As asked earlier, does running f3probe,
f3write, f3read produce anything interesting?
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
