I had a centos Linux 64bit installed on my server.
Unfortunately I don't know how but my OS crashed
and now I have no way to get back my DATA except for rescue disk.
I have a Linux 64bit loaded in my server with rescue
but I have tried many ways to mount my hdd in Linux and was not succeed.
please help my out of this hell. all my life achievement is in this server!

-----------------------------------------------------------------------

root@rescue ~ # fdisk -l

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000bd8fc

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 91201 732467610 8e Linux LVM

Disk /dev/sdb: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00038cb8

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 91201 732572001 8e Linux LVM

Disk /dev/dm-0: 1489.7 GB, 1489716117504 bytes
255 heads, 63 sectors/track, 181114 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 10.4 GB, 10468982784 bytes
255 heads, 63 sectors/track, 1272 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x30307800

Disk /dev/dm-1 doesn't contain a valid partition table

-------------------------------------------------------------------------------

root@rescue ~ # lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID Z2cXSX-zUZw-eLTh-am9r-PMcc-dLhz-mzJDuH
LV Write Access read/write
LV Status available
# open 0
LV Size 1.35 TB
Current LE 44397
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID SOkdvF-Z0uM-CEJR-3bBr-iejS-IjHy-3PbWkc
LV Write Access read/write
LV Status available
# open 0
LV Size 9.75 GB
Current LE 312
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

-----------------------------------------------------------------------------

i have tries many ways to mount the hdd but each gave an error

root@rescue ~ # mount /dev/VolGroup00/LogVol00 /mnt
mount: you must specify the filesystem type

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

root@rescue ~ # mount /dev/dm-0 /mnt
mount: you must specify the filesystem type

root@rescue ~ # mount -t ext3 /dev/dm-0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/dm-0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

---------------------------------------------------------------------------------

this is the instruction that datacenter has gave me to mount

root@rescue ~ # cat /proc/mdstat
Personalities : [raid1]
unused devices: <none>
root@rescue ~ # mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1
mdadm: no recogniseable superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted
root@rescue ~ # mount /dev/md0 /mnt
mount: special device /dev/md0 does not exist

---------------------------------------------------------------------------------

for the last time. please someone with the knowledge of Linux help me
i really need ma data. i have disappointed in my server OS to get repaired
but at least i have to mount my hdd to be able to transfer my data.

Are you using raid ? If not then you don't need md commands.
You have to activate LVM volumes before they can be mounted.
as root :

Depending on the results of those commands, you can then mount the volume. Don't mount it on /mnt create a subdirectory like /mnt/rescue then mount the LV on that.

You can use some of the examples from this howto, but this is not a recipe ! Only use these pages as examples of commands relevant to your needs.
http://www.howtoforge.com/linux_lvm

Hi there,

Try something like : 'mount /dev/mapper/VolGroup00-LogVol00 /mnt'

Cheers.

dear guys none of these helped me out!

------------------------------------------------------------------------

root@rescue /mnt # mount /dev/mapper/VolGroup00-LogVol00 /mnt/rescue
mount: you must specify the filesystem type
root@rescue /mnt # mount -t ext3 /dev/mapper/VolGroup00-LogVol00 /mnt/rescue
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol00,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

-----------------------------------------------------------------------

root@rescue ~ # cd /mnt
root@rescue /mnt # mkdir rescue
root@rescue /mnt # vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
root@rescue /mnt # vgchange -ay
2 logical volume(s) in volume group "VolGroup00" now active
root@rescue /mnt # mount /dev/VolGroup00/LogVol00 /mnt/rescue
mount: you must specify the filesystem type
root@rescue /mnt # mount -t ext3 /dev/VolGroup00/LogVol00 /mnt/rescue
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol00,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

-----------------------------------------------------------------

ny the way I have tried with both ext2 ext3
but none worked out and game the last error
wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol00,
please help me out of this !

Could you check your filesystem ??

fsck /dev/VolGroup00/LogVol00

Let me know

Cheers.

1 members found this post helpful.

thank you " tizzef"

you really saved my life "fsck /dev/VolGroup00/LogVol00"
i hope every guy intended to help me have a nice chrismas