Unexpected inconsistency run fsck manually vmware

After you deploy the VA 1.1.3 for replication, the VA tires to boot but does not and show the following error "/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY". dev/sdb6: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4 The root filesystem on /dev/sdb6 requires a manual fsck modprobe: module ehci-orion not found in However, the term "unexpected inconsistency" will sometimes actually show up as a specific type of error message. Since this error message The error is usually followed with a big warning message that reads something like "/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY 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. /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). Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): KVM. A manual fsck must be performed, then the system restarted. the fsck should be performed in maintenance mode with the root filesystem mount in read-only mode But now it gives me an error. system:UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (i.e., without -a or -p options) fsck died with exit status 4 failed (code