/dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually

juan_f_vidal · 06-08-2011, 05:56 PM

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.

Kind regards,

Juan.

syg00 · 06-08-2011, 07:01 PM

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.

juan_f_vidal · 06-08-2011, 08:34 PM

Hi syg00, many thanks for your response.

Yes, you are right, I didn't reduced the filesystem first.

1. You mean I must remove the lv line in the fstab file after booting from the CD and typing "linux rescue", right?

2. Once booted, how should I resize the lv back? (Its original size was 15G)

Thanks and regards,

Juan.

syg00 · 06-08-2011, 10:51 PM

1) Yes - or just comment it out for now.
2) lvresize, lvextend ...

"man lvm" lists all the sub-commands. There is also a LVM howto on tldp.or - Redahat used to have one on their dococ site as well.

juan_f_vidal · 06-09-2011, 11:31 AM

Hi syg00,
I performed the following actions:

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.

Many thanks for your support.

Regards,

Juan.