Re: how to fsck at boot?

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

 



On 10/26/24 16:49, ToddAndMargo via users wrote:
On 10/25/24 15:55, Jonathan Billings wrote:
On Oct 25, 2024, at 08:15, ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

# tune2fs -E force_fsck /dev/nvme0n1p4
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: Bad magic number in super-block while trying to open /dev/ nvme0n1p4
/dev/nvme0n1p4 contains a crypto_LUKS file system

That is most likely the NVME partition you use as the storage backend for your LUKS volume.

This should go without saying, but you should only run the ext2/3/4 tools on ext2/3/4 filesystems, and not the encrypted device used in your LUKS volume.

You can look at ‘mount’ to see what device that is, most likely in / dev/mapper/.



I could not find it in mount, but I did find it with df:

# df -kPT /
Filesystem                                            Type 1024-blocks    Used Available Capacity Mounted on /dev/mapper/luks-903bc691-a0f0-42bc-aa96-4233a7edc0e9 ext4   950971044 669182320 233408360      75% /

# tune2fs -E force_fsck /dev/mapper/luks-903bc691-a0f0-42bc- aa96-4233a7edc0e9


It did run.  Took about 10 seconds.  Thank you!

Followup question: is there a flag to throw that tells fsck
to "repair"?  I never found one in "man fsck".

-T

Thank you!

Trying it now.

# tune2fs -E force_fsck repair /dev/sdXY

https://search.brave.com/search?q=tune2fs+-E+force_fsck+repair&summary=1&summary_og=5ad6fac8ba3b05432c1504

Tune2fs Force FSCK Repair

The tune2fs command is used to modify the filesystem mount options and settings for ext2, ext3, and ext4 file systems. The option -E force_fsck enables forced filesystem checks (fsck) on every reboot, while the repair option specifies that fsck should attempt to automatically repair any issues found during the check.
--
_______________________________________________
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