Dev/volgroup00/logvol00 unexpected inconsistency run fsck manually

 · /dev/sda1 G G G 4percnt; /boot Actually /dev/sda1 on boot partition contains less size about to M,right now is showing is equal to LogVol00(showing wrong inf.) www.doorway.ru with dumpe2fs for knowing the super block status.  · And to recover the corrupted root filesystem, please follow the steps below: 1. Boot the system from the DVD of the same major release as the system. Once the system has successfully booted from the ISO image and boot screen will appear. Type: “ linux rescue ” without the quotes, and hit enter at the prompt. 2.  · There is always a possibility of data corruption, no matter what security measures we apply. For a Linux system, root partition is the most important one. If the data in the root partition is corrupted, you can't boot up your device. If your system is CentOS/RHEL, learn how to recover corrupted partition.

And to recover the corrupted root filesystem, please follow the steps below: 1. Boot the system from the DVD of the same major release as the system. Once the system has successfully booted from the ISO image and boot screen will appear. Type: “ linux rescue ” without the quotes, and hit enter at the prompt. 2. (Repair filesystem) 1 # fsck -y / The fsck utility displays several messages during the repair process. If you are running Unidesk through , there are now two partitions on the boot disk, and you must run two commands: (Repair filesystem) 1 # fsck -y /dev/sda1 (Repair filesystem) 1 # fsck -y /dev/sda3. There is always a possibility of data corruption, no matter what security measures we apply. For a Linux system, root partition is the most important one. If the data in the root partition is corrupted, you can't boot up your device. If your system is CentOS/RHEL, learn how to recover corrupted partition.

Inodes that were part of a corrupted orphan linked list found /dev/VolGroup00/LogVol UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. 5 may /dev/VolGroup00/LogVol UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) [FAILED] *** An error occurred. Then I tried with fsck /dev/mapper/VolgroupLogvol00 again it shows same error as “The physical size (according to the superblock) is blocks the.