What are advanced check/repair actions for boot partition?

Just got electricity down for about 0.6-0.9 seconds.
PC which powered directly from power outlet reboots.
Got the next journalctl items:

Dec 22 06:32:32 systemd-fsck[191]: /dev/nvme0n1p2: clean, 381232/29933568 files, 58445795/119711828 blocks
Dec 22 06:32:33 systemd-fsck[275]: fsck.fat 4.1 (2017-01-24)
Dec 22 06:32:33 systemd-fsck[275]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Dec 22 06:32:33 systemd-fsck[275]:  Automatically removing dirty bit.
Dec 22 06:32:33 systemd-fsck[275]: Performing changes.
Dec 22 06:32:33 systemd-fsck[275]: /dev/nvme0n1p1: 6 files, 78/76646 clusters

Looks like PC loads well, but what are your recommendations for advanced check/repair of boot partition? In my case I have FAT32 file system.

$ lsblk
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot/efi
├─nvme0n1p2 259:2    0 456.7G  0 part /
└─nvme0n1p3 259:3    0   8.8G  0 part [SWAP]


Then boot the USB stick with Manjaro, do not mount the partitions and try to repair the boot partition.

See fsck.fat(8) eg. man fsck.fat, because that partition is mounted on /boot/efi but not actively used by the OS you might be able to fix it while booted in your OS just unmount it temporarily just in case…

Maybe invest in a UPS?

As long as you don’t use btrfs fsck is the right tool to check fs and it has been executed acc.to your journal already, looks good as long as you can boot, so you should be fine (this time), no need for further investigations. Make sure you have a good backup strategy in case next time you might not have the same luck. :wink: