On Mar 15, 2025, at 07:26, Dave Close <dave@xxxxxxxxxxx> wrote: > So, again, "e2fsck -c" seems to destroy the superblock. In this case, I > had no suspicion of any problem with the card; I only ran e2fsck to see > if the same problem would occur. It did. > > I'm not directly formatting the card, rpi-imager does that, so choosing a > different filesystem is not reasonable. I am confident that the card has > the advertised capacity; SanDisk is not a fly-by-night vendor. > > The e2fsck %done and elapsed time numbers did increment during the process > but were evidently reset on completion before I copied the output. That's > a different issue, not terribly important, but annoying. Perhaps it isn’t the media but the SD card reader? It could be that the device is going offline due to some hardware problem. Have you checked dmesg? While the badblocks operation is read-only, it does produce a lot of I/O operations on a new filesystem. If the problem is fsck corrupting disks, that seems like a pretty major problem and you should file a bug. -- Jonathan Billings -- _______________________________________________ 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
