You are not logged in.
Pages: 1
Twice now I have gotten an error on boot that says
kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
systemd[1]: Mounted /boot. I run lsblk and this is what my partitions look like.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
zram0 253:0 0 4G 0 disk [SWAP]
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part /boot
├─nvme0n1p2 259:2 0 47G 0 part /
└─nvme0n1p3 259:3 0 428.9G 0 part /home How badly have I messed up? my system is running fine but I need to update and I am scared to do anything without fixing this.
Last edited by jolie.kate (2026-01-04 05:25:04)
Offline
Normal EFI/FAT warning. /boot wasn’t cleanly unmounted.
Boot a live USB and run:
fsck.vfat -a /dev/nvme0n1p1Reboot.
"Nothing matters" -a Nihilist
"Why bother thinking what matters?" -me
Online
Thank you! I couldn't remember what I had done the first time but this is the answer. Closing the topic, but I am curious if you know if there a reason it's failed to cleanly unmount twice now? Is there something I can do to prevent the issue from happening again?
Offline
It usually happens if the system shuts down or reboots before /boot is unmounted, not pirticularly how but happens mostly when forced shutdown or power loss . To prevent it, just let shutdowns finish normally and avoid forcing power off. Once /boot is clean again, it’s unlikely to cause any problems.
Last edited by 5hridhyan (2026-01-04 06:36:49)
"Nothing matters" -a Nihilist
"Why bother thinking what matters?" -me
Online
Ok that was my working theory, thank you for confirming!
Offline
Pages: 1