Unexpected inconsistency run fsck manually linux operating

fsck from util-linux 2.36.2 e2fsck 1.46.2 (28-Feb-2021) fsck.ext2: No such file or directory while trying to open /dev/mapper/luks-3acb28cf-a378-4e96-a336-0df25478de40 Possibly if it is an ext4 (or ext2 or ext3) filesystem run the filesystem check more specifically targeted at the filesystem actually present. /dev/mapper/pve-root UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. When I run it, then it modified file system then it said something about 0.3% Bought a while ago, I still have varanty and I can just ask for replacement at local store. Should I ? Having to run fsck means that my harddrive them: fsck from util-linux 2.31.1 /dev/longhorn/pvc-be3c4cd8-b3be-4d2e-a4ae-9f72525706cf: One or more block group descriptor checksums are invalid. fsck MANUALLY. (i.e., without -a or -p options). ext3 - unexpected inconsistency, run fsck manually. Use root password for maintenance. Thanks and Regards. ext3 is a filesystem used in Linux operating systems, which is exactly what the MARS platform is. a fsck is a Unix/Linux command that checks the file system for irregularities, and attempts enter your root password and hit fsck. alright as you can see the filesystem was modified and you need to reboot Linux. *** Almost Every time you need to run this TWICE before you are allowed to boot, so this time lv_root has been fixed bu /dev/sda1 needs to be repaired, so run the process once more.