System Unbootable Post Root File System Corruption

A root file system in Linux operating system?: File (inode #8, mod time Mon Dec 26 21:40:14
contains all necessary information about the files2005) has 1 multiply-claimed block(s), shared with
required at the time of booting the system. This1 file(s):
is saved on a partition where the root directory is/: /bin/zless (inode #81297, mod time Fri Jul 8
located. Corruption in root file system can be due22:19:49 2005)
to improper system shutdown, operating system/:
malfunction, virus infection, and human errors. In/: UNEXPECTED INCONSISTENCY; RUN fsck
most cases, the system becomes unbootable,MANUALLY
resulting in inaccessibility of hard drive data. To(i.e., witjout -a or -p options)
get past root file system corruption, a user needs*fsck failed. Please repair manually and reboot"
to repair it by running FSCK command manually.The error message makes the system
However, if the corruption persists even afterunbootable and the hard drive data inaccessible.
running FSCK command, then the user needs toCause:
opt for a third-party Linux Data RecoveryAs stated in the error message, the root Files
application.system is corrupted or damaged.
To explain the above case, consider a practicalResolution:
scenario where you encounter the underneathTo get rid of the above root error message, you
error message while booting your Linux system:will need to follow the below steps:
"*Checking root file systems...Run FSCK command manually.
/contains a file system with errors, check forcedIf the command fails, restore the data from an
/:up-to-date backup. If no backup available, then
Duplicate or bad block in use!format the hard drive and reinstall the operating
/: Multiply-claimed block(s) in inode 8: 1024system. To recover formatted files post
/: Multiply-claimed block(s) in inode 81297: 1024re-installation, use an effective Linux Recovery
/: (There are 1 inodes containing multiply-claimedapplication.
blocks.)