Linux bad superblock on /dev/mapper/VolGroup-lv_root

Linux and Unix-Like Red Hat
1

Hi Friends . my linux try to start very slowly after give it this error:

mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root,
missing codepage or helper program, or other error
in some cases useful info is found in syslog - try
dmesg : tail or so

Kernel panic - not syncing : Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-358.6.2.el6.x86_64 #1
Call Trace :
? panic+0xa7/0x16f
? do exit+0x862/0x870
? fput+0x25/0x30
? do_group_exit+0x58+0xd0
? sys_exit_group+0x17/0x20
? system_call_fastpath+0x16/0/0x1b

panic occurred, switching back to text console ( and computer froze on this screen )

and after i use it centos 6.4 setup cd and try to open with rescue mode its giving another error:

you don't have any linux partitions. press return to get a shell.
the system will reboot automatically when uou exit from the shell

its just 1 HDD : WD 1TB and no partition for data . i just installed it for the operating system. its a squid and dhcp server.

pls help me guys im stucked and idont know to much about linux. what can i do ? thanx

fdisk -l

Disk /dev/sda : 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size logical / physical = 512 bytes / 1096 bytes
I/O Size minimum optimal : 4096 bytes / 4096 bytes
Disk label type : dos
Disk identifer : 0x0bcea944

Device Boot        Start        End                 Blocks       Id     System  
/dev/sda1 *        2048        1026047           512000      83   Linux
/dev/sda2      1026048   1953519615      976246784      8e   Linux LVM

Disk /dev/mapper/live-rw : 2147MB
Disk /dev/mapper/live-base : 2147MB
2

Instead of fdisk -l can you use

parted -l

?

3

Hi mod ty for answer i check it parted -l just like this :

---------- Post updated at 10:35 AM ---------- Previous update was at 10:29 AM ----------

parted -l

Model : ATA WDC WD10EURX-73F
Disk /dev/sda: 1000GB
Sector size logical/physical : 512/4096
Partition table : msdos

Disk Flags:

Number      Start       End         Size        Type        File system      Flags
1              1049KB    524MB     524MB      primary    ext4               boot  
2              525MB     1000GB    1000GB    primary                         lvm

Partition Table : loop
Number      Start     End         Size        File system     Flags
1              0.00B     2147MB   2147MB   ext4
4

So it's the partion 2, in Linux accessable as /dev/sda2,
but under lvm control, so you should try to repair it from a resuce system with lvm.
Stop the boot process with a few key strokes, so you get a grub menu that offers a rescue system.

If there is none, you can try to edit the normal linux system, and add rd.break to the kernel parameters, then continue the boot. It then spawns a rescue shell.

In the rescue system or in the rescue shell you must try to access the disk
The lsblk command should list a tree.
You can try to mount a part of it, probably /dev/mapper/VolGroup-lv_root,
(create an empty directory for example with mkdir -p /mnt )
so the command is

mount /dev/mapper/VolGroup-lv_root /mnt

If the mount fails with "bad superblock", then run fsck on it.

Pardon if my knowledge is rather theoretical.