Tuesday, February 2, 2010

dev volgroup00 logvol00 unexpected inconsistency

SkyHi @ Tuesday, February 02, 2010
So today I ran Synaptic to get the current batch of updates. One of the updates was a new Kernel for Fedora systems, yay. I reboot so I can use the new kernel (and possibly uninstall the old one) but an error occurs.

As the machine is starting up it does it's usual detecting hardware and setting hostname. After that, it goes to check the root filesystem and bombs with this error:

Checking root filesystem

*** An error occured during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
*** {Some stuff about disabling SELinux here}

So I log into the shell as root and run fsck with the option to check for bad blocks and answer yes to all questions about relocating sectors. It goes through and claims to fix some orphaned sectors and nodes, relocates some sectors that seem to have to references (or something along those lines) and some other things which I did not catch completely. It seems to loop and start itsself again, so after the second time it did this I interrupted it and rebooted. Alas, I have the same error and do not know how to fix this. Please help me.

Thank you in advance.


I'm having the same issues. I tried adding a second hard disk to my volume group. I ran the following commands

fdisk /dev/hdb
n (new)
p (primary)
1 (first partition)
t (type)
8e (lvm)
w (write to disk)

pvcreate /dev/hdb1

vgextend VolGroup00 /dev/hdb1

lvextend /dev/VolGroup00/LogVol00 /dev/hdb1

#rebooted with rescue cdrom

lvm vgchange -a y Volume00

lvm lvchange -a y /dev/VolGroup00/LogVol00

e2fsck -y -f /dev/VolGroup00/LogVol00 (competed without errors)

resize2fs -f /dev/VolGroup00/LogVol00 (added the -f because it was complaing that I should run e2fsck -f and I had already done that)

e2fsck -f /dev/VolGroup00/LogVol00

This is where I started getting the errors described above. I can access my files from the rescue disk, but I can not boot because of LVM inconsistancy errors.


Step by step solution:
Your system appears to shut down uncleanly

Checking file system

/dev/VolGroup00/LogVol00: Reside inode is not valid


(i.e., without -a or -p options)

*** Run 'setenforce 1' to reenable.
Give root password for maintenance
(or type Control-D to continue): Type root password

(Repair filesystem) df
File System 1K -block Use Available Use% Mount
37864976 13675768 22265728 39% /
/dev/hda1 37864976 13675768 22265728 39% /boot

#(Repair filesystem) fsck -f -y /dev/VolGroup00/LogVol00

Resize inode not valid. Recreate? (yes)

/dev/VolGroup00 contain a file sytem with errors, check forced.

Pass 1: Checking inodes, blocks, and sizes
Duplicate blocks found... invoking duplicate block passed
Pass 1B: Rescan for duplicate/bad blocks

File /usr/src/linux-2.6.9/arch/s390/appldata/Makefile
Duplicateed blocks already reassigned or cloned

Pass 2: checking directory structure
Pass 3: checking directory connectivity
Pass 4: checking reference counts
Pass 5: checking group summary information
Free blocks count wrong for group #0 (19039,counted = 19040)
Fix? Yes

/dev/VolGroup00/LogVol00: ***** FILE SYSTEM WAS MODIFIED *****
/dev/VolGroup00/LogVol00: ***** REBOOT LINUX *****
/dev/VolGroup00/LogVol00 428503/4816896 files (2.3 % non-contiguous), 3570106/9617408

(Repair filesystem) fsck /dev/hda1
/boot clean, 39/26104 files 12402/104308 blocks

#(Repair filesystem) reboot