/dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually
RHEL 5.4
Hi, I'm facing the following error after rebooting the server:
/dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually"
*** An error accurred during the file system chek.
*** Dropping you to a shell: the system wil reboot
*** when you leave the shell.
give the root password for maintenence:
-Previously I performed a lvreduce command on a LV, after the lvreduce, I reboot the server.
-After login as root I run:
e2fsck -f /dev/VolGroup01/u04
but, it shows:
the filesystem size (according to the superblock) is 5218304 blocks
the physical size of the device is 1310720 blocks
...
either the superblock or the partition table is likely to be corrupt
abort<y>? no
pass 1: cheking inodes, blocks, and sizes
error reading block 1310722 (invalid argument) while doing inode scan
inore error <y>? y
-Additionaly, trying to lvdisplay, it shows:
locking type -1 initialisation failed
I have no important data on that LV, but I would appreciate any clue or help, because I can not boot the server properly.
Before reducing the lv (or a partition in a non-LVM environment) you *must* reduce the filesystem first.
Seems you didn't.
If you must get the system booted, remove that lv from fstab - use a rescue system for that.
After that, if you're lucky, you may be able to resize the lv back to where it was and do the fsck. Depends if the disk space has been (re-)used by something else.
1. Boot from RHEL CD, linux rescue mode.
2. Edited /mnt/sysimage/etc/fstab deleting the line belonging to the failed lv "/dev/VolGroup01/u04"
3. Exctracted the CD and rebooted the server.
4. The system booted properly, but without mounting the affected LV.
5. As the LV was no longer needed and without usefull data, it was removed with
# lvremove /dev/VolGroup01/u04
6. System rebooted and started up normally without any errors.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.