On Thu, Jun 15, 2023 at 4:01 PM Rich Shepard <[email protected]> wrote:
> On Thu, 15 Jun 2023, Michael Ewan wrote: > > > sudo umount /boot/efi > > sudo fsck /dev/sda1 > > sudo mount /boot/efi > > Logged in as root: > # umount /boot/efi > # fsck /dev/sda1 > fsck from util-linux 2.27.1 > fsc.fat 3.0.28 (2015-05-16) > 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be > corrupt. > 1) Remove dirty bit > 2) No action > ? > # mount /dev/sda1 > > What's a dirty bit? It literally says right there "Fs [filesystem] was not properly unmounted [because you power cycled it, rather than reboot] and some data may be corrupt [although it won't be, because you weren't writing anything to the filesystem when you powercycled it, but the OS doesn't know that, it just noticed that the dirty bit was still set because you had not unmounted it cleanly]" > How do I remove it? > Press '1' at the prompt, like the rudimentary menu suggests. Or, alternatively (after unmounting) auto-repair with: fsck.vfat -y /dev/sda1 There is a manual page for fsck.vfat on most systems: man fsck.vfat -- Russell Senior [email protected]
