Re: e2fsck malfunction?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 13, 2025 at 7:48 PM Dave Close <dave@xxxxxxxxxxx> wrote:
>
> I have been trying to create an SDcard to use with an Raspberry
> Pi. The card is created using the rpi-imager program on Fedora (41)
> and that program reports the creation as successful. Later, after
> mounting the ext4 partition on the card under Fedora and doing two or
> three minutes of exploration, I encounter a bad block. So I unmount
> the partition and use e2fsck to locate any bad blocks and mark them:
>
>   e2fsck -y -c /dev/sdb2
>
> But after that when I try to remount the partition, it seems that
> e2fsck has destroyed the filesystem!
>
>   # mount /dev/sdb2 /mnt
>   mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb2,
>   missing codepage or helper program, or other error.
>   dmesg(1) may have more information after failed mount system call.
>
> Checking dmesg, I see that the mount has tried several possible
> filesystem types without success, including several lines like,
> "EXT4-fs (sdb2): VFS: Can't find ext4 filesystem". Explicitly adding
> "-t ext4" to the mount does not help.
>
> I've repeated this process, again getting success, including
> verification, from rpi-imager. This time I omitted the -c from the
> e2fsck command and was able to mount the partition after.
>
> So it appears that asking e2fsck to check for and mark bad blocks
> causes it to destroy the superblock(s). Is there another explanation?

Throw the old SDcard away, and use a new one. The old SDcard is clapped out.

I used to do a lot of testing of C and C++ libraries on ARM SBCs, like
BeagleBoards, BananaPi's, Raspberry Pi's and WandBoards. The low
resources (like 512 MB or 1 GB or RAM) and C++ compiler ensured I
needed a swap file to build the libraries. I used to go through
SDcards like they were dirty underwear. Once I started seeing
filesystem errors I threw away the old card and used a new card with
the board.

Jeff
-- 
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux