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

Above error showed up after a reboot. I am able to mount another partition of this disk (content with the home directories). However I cannot mount the main partition, so cannot read the Centos 5.2 syslog.

My suspicion is that mysql service made a large amount of temporary tables flooding the hdd space.

Is there any command I can run from a live distro to fix this?

What's in /etc/fstab?

fsck ?

1 members found this post helpful.

NEVER RUN fsck ON THE PARTITION CONTAINING A Logical Volume. (Excuse the shout, but I killed a whole volume with that mistake.)

Look at your /etc/fstab. It's possible that that LV is swap space, and, therefore, not mountable. In any case, look at the lvm tools to see what they think about the volume.

Making wild generalized claims based on a single event is worse that the shouting.

fsck is a filesystem tool - it is irrelevant (to fsck) whether the filesystem is on a LV or a "real" partition. Anytime you have to run fsck to rectify problems you have the potential to lose data. Sad but true - fsck is a tool to ensure the validity of the filesystem, not your data necessarily.

Eh, Just mentioning the fsck tool. Sorry you lost a volume that way. But, I think we all have -- i mean really isn't the first line of the fsck manual page "You might lose data using this tool" or something?

anyway... fsck should not be used on mounted volumes -- use a boot-cd and make sure that the volume is not mounted. You have a good idea though for the swap space check though.

I think, when using LV's, you'll want to fsck the Logical Volume itself, which a quick google of "fsck lvm" will turn up. To find your LV's, you can do a:
Then to fsck them:

1 members found this post helpful.

lvdisplay output:

--- Logical volume ---
LV Name /dev/VolGroup01/LogVol00
VG Name VolGroup01
LV UUID 6YpwEF-wphp-i13f-VWcN-1NzS-9wLd-14WzPp
LV Write Access read/write
LV Status available
# open 0
LV Size 64.53 GiB
Current LE 2065
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup01/LogVol02
VG Name VolGroup01
LV UUID kgrW14-qfRN-dyrT-tSzg-jqCV-Kbuq-8ivg2f
LV Write Access read/write
LV Status available
# open 0
LV Size 48.84 GiB
Current LE 1563
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name /dev/VolGroup01/LogVol01
VG Name VolGroup01
LV UUID qr7g0r-kTyN-23FU-8J5J-PGQL-P9de-VpVXox
LV Write Access read/write
LV Status available
# open 0
LV Size 1.00 GiB
Current LE 32
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

Guessing the 1.0 GB /dev/VolGroup01/LogVol01 is the swap partition.

I did the following:

root@Microknoppix:~# vgscan --mknodes
Reading all physical volumes. This may take a while...
Found volume group "VolGroup01" using metadata type lvm2
root@Microknoppix:~# vgchange -ay
3 logical volume(s) in volume group "VolGroup01" now active
root@Microknoppix:~# lvscan
ACTIVE '/dev/VolGroup01/LogVol00' [64.53 GiB] inherit
ACTIVE '/dev/VolGroup01/LogVol02' [48.84 GiB] inherit
ACTIVE '/dev/VolGroup01/LogVol01' [1.00 GiB] inherit
root@Microknoppix:~# mkdir /mnt/somename
root@Microknoppix:~# mount /dev/VolGroup01/LogVol02 /mnt/somename
root@Microknoppix:~# ll /mnt/somename/
total 144

/dev/VolGroup01/LogVol02 is the volume i CAN mount.

root@Microknoppix:~# mkdir /mnt/somename2
root@Microknoppix:~# mount /dev/VolGroup01/LogVol00 /mnt/somename2
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup01-LogVol00,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or s

So the following command should be used?:

fsck.ext3 /dev/VolGroup01/LogVol02

I thought LogVol00 was the one you were having issues with?

1 members found this post helpful.

YOU ARE RIGHT!

fsck.ext3 /dev/VolGroup01/LogVol00

Should do it?

It did! After some default yesses (50 or so) I managed to mount and shortly after rebooted succesfully. Thanks!

Congrats. Please mark this thread solved, and click 'yes' on any posts you found helpful.

1 members found this post helpful.