df -h not showing the file system

JATA01 · 12-30-2010, 05:15 AM

Hello Friends,

I have install 5.5 kernel in rhel and after rebooting got the error to control+d to continue or root password. I have done the same but df -h not showing the lvm filesystem.
I have tried to remounnt but showing resource busy.
I have rebooted on the previous kernel but getting the same issue.
Its a VM.

df -h showing only /dev/mapper/vg_osdata-lv_root /

Kindly suggest!!

Brgds,
Shankar

EricTRA · 12-30-2010, 05:19 AM

Hello,

5.5 is not the kernel version of RHEL, but the distro version number, so to say correctly you have RHEL5.5 installed and it uses kernel 2.6.18. The problem you have is that your filesystem has been corrupted in some way, maybe unclean shutdown. When the console presents you the 'Control+D' option, type in the root password and run fsck on the filesystems affected to try to repair them. Have a look at the man page of fsck for what option(s) to use.

Kind regards,

Eric

JATA01 · 12-30-2010, 08:33 AM

Hi Eric,

You are right. I have done the same but not succeed.
Can we recover by backup or do we need to create vm then recover the data?
I want to escape from creating vm..

Thanks-

EricTRA · 12-30-2010, 08:44 AM

Hi,

It depends on how you created the backup. If you created an exact image for example with dd or with CloneZilla, then you can restore since the backup is at block level and not at filesystem level. If on the other hand you used a tool / program for example like Rsync or Bacula, then I'm afraid you'll first have to recreate your partitions and LVM group(s) and volume(s).

Kind regards,

Eric

JATA01 · 12-30-2010, 08:45 AM

Even we can't mount the mount point manually. But I can find the fdisk -l with filesystem.
also can get info about pvdisplay, vgdisplay and lvdisplay.
I can also go into that mount point using cd and ls the contents. But still not showing using df -h.

JATA01 · 12-30-2010, 08:51 AM

Using Networker full backup is taken like all subtree of /.

EricTRA · 12-30-2010, 09:11 AM

Hello,

What was the result of fsck in maintenance mode? Or didn't you run that?

You could check with the following:

Code:

pvscan
lvscan
lvchange -ay volume_group_name
lvscan

and after that run a fsck on the logical volumes

Code:

fsck -t type /dev/mapper_name/volume_name

where of course you have to indicate the type of filesystem and the correct name of your volume.

You can also force a check by rebooting with the following options and see what it does on screen:

Code:

shutdown -r -F now

Don't have knowledge of Networker backup but if it does backup as subtree of / then it's not at block level and you'll need to make your LVM available first or rebuild it I'm afraid.

Kind regards,

Eric

JATA01 · 12-30-2010, 11:33 AM

already done the mentioned steps and got the proper output. But no luck. Rebooted with init 6 and reboot command only.

EricTRA · 12-30-2010, 11:39 AM

Hello,

And what was the output when you forced the check? Was there any error mentioned and if so, what was it? When you say you performed the proper steps, to what are you referring? Running the fsck on the logical volumes? If so, what was the result?

Kind regards,

Eric

JATA01 · 12-30-2010, 11:50 AM

recovered journel..

Right now I am not in my office, will let you know the exact screen shot.

Brgds,
Shankar

EricTRA · 12-30-2010, 12:02 PM

Hello,

OK, thanks, let's hope you can get it up and running again.

Kind regards,

Eric