ok i entered the command of `grep /proc/mounts` then i am rechecked if the lvm is mounted and then i wrote `rpm --nodeps --nodigest --noscripts --nosignature --dbpath /tmp/LogVol01/var/lib/rpm --root /tmp/LogVol00/ -Vva 2>&1|tee -a /tmp/rpm_verify.log; rpm --nodeps --nodigest --noscripts --nosignature --dbpath /tmp/LogVol01/ --root /tmp/LogVol01/var/lib/rpm -Vva 2>&1|tee -a /tmp/rpm_verify.log`

rpm_verify.log seems empty. Am i did something wrong?

That shouldn't return anything because you need to grep for something.


What is your mount point? If you didn't mount LogVol00 at /tmp/LogVol00/, then using "--root /tmp/LogVol00/" will show nothing. Then the rpm_verify.log will be empty.

Ok then i am re-trying that:
i wrote your first command mentioned above and that is the outcome

[root@localhost ~]# mkdir /tmp/LogVol0{0,1}; for n in 0 1; do mount "/dev/VolGroup00/LogVol0$n" "/tmp/LogVol0$n"; done
mount: /dev/VolGroup00/LogVol00 already mounted or /tmp/LogVol00 busy
/dev/VolGroup00/LogVol01 looks like swapspace - not mounted
mount: you must specify the filesystem type

It means that he filesystem is already mounted right?

You should be able to check that using the 'mount' command.
If you 'mount|grep LogVol' it could show:
- /dev/VolGroup00/LogVol00 being mounted on /tmp/LogVol00, or
- something different being mounted on /tmp/LogVol00, or
- /dev/VolGroup00/LogVol00 being mounted on another mount point.
As long as you can mount it anywhere where you can read the filesystem it's OK, just adjust the mount point in the commands you use. And since LogVol01 is a swap partition you do not have to mount it.

What does 'rpm --nodeps --nodigest --noscripts --nosignature --dbpath /tmp/LogVol00/var/lib/rpm -qa' return? If it returns package names all is OK. If it shows nothing then something is wrong and you should show the output of 'ls -al /tmp/LogVol00/var/lib/rpm'.

* At this point you are able to access the contents of your Logical Volume. It appears it takes more time to try to repair your VM guest than it took us to access it. So, if you can access your "valuable data" (I think that's what you wrote in your other thread) then you might also decide this is the time to cut your losses, copy the data and configuration to an external backup medium (say an USB stick or harddisk) and build a new VM guest. Just a suggestion, OK?

I am installed a new server and i copied all the important data from the old server to the new server and now all is ok!
Thanks a lot again..

You're welcome. Please don't forget to mark this thread [SOLVED].