Can't access my sda2

[bigado]

I had a Centos install that corrupted the boot and would only boot to GRUB. After about a week of trying linux rescue and various measures I gave up and installed a fresh copy of Centos on /dev/hda which is a 40 GB drive. All my data was on /dev/sda which I did not overwrite and is a 1TB SATA drive. I added sda to the LVM of hda now and is recognized as part of Partition 2 - using the GUI Logical Volume Management. My problem is I can't seem to figure out how to retreive my data from the sda2 drive. This is what I've tried. Help please as I need the data.


Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4042 7830456 c W95 FAT32 (LBA)
[root at localhost ~]# mount /dev/sda2
mount: can't find /dev/sda2 in /etc/fstab or /etc/mtab
[root at localhost ~]# mount /dev/sda2
mount: mount point /mnt/sda does not exist
[root at localhost ~]# mount /dev/hda2
mount: can't find /dev/hda2 in /etc/fstab or /etc/mtab
[root at localhost ~]#
[root at localhost ~]# cd /media
[root at localhost media]# ls
KINGSTON
[root at localhost media]# mkdir sda2
[root at localhost media]# ls
KINGSTON sda2
[root at localhost media]# mount -t ext3 /dev/sda2 /media/sda2 -o defaults,umask=0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

I changed the /etc/mtab file by adding the line for /dev/sda2:
/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/hda1 /boot ext3 rw 0 0
/dev/sda2 /mnt/sda ext3 rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
/dev/sdb1 /media/KINGSTON vfat rw,noexec,nosuid,nodev,shortname=winnt,uid=0 0 0

[devils casper]

Hi and Welcome !

Post the output of fdisk -l command here.

su -
fdisk -l

[Jonathan183]

Can you post the output of

fdisk -l

and also post the output of

mount /dev/sda2 /media/sda2

if errors are produced.

You should not edit /etc/mtab, and I would use manual mounting of the drive partition and add an entry to /etc/fstab once you have things sorted

[bigado]

Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4865 38973690 8e Linux LVM

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdb: 8019 MB, 8019509248 bytes
102 heads, 38 sectors/track, 4041 cylinders
Units = cylinders of 3876 * 512 = 1984512 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4042 7830456 c W95 FAT32 (LBA)

# mount /dev/sda2 /media/sda2
mount: you must specify the filesystem type

I had tried the command earlier:
mount -t ext3 /dev/sda2 /media/sda2 -o defaults,umask=0

[devils casper]

/dev/sda2 is LVM and you can't mount it using mount command.
Execute pvs command and post output here.

[bigado]

# pvs
PV VG Fmt Attr PSize PFree
/dev/hda2 VolGroup00 lvm2 a- 37.16G 0
/dev/sda2 VolGroup00 lvm2 a- 931.41G 931.41G

[devils casper]

Execute this now :

lvdisplay /dev/VolGroup00

It will list available LogVolumes. Create mount point ( folder ) for each and mount LogVolumes.

[bigado]

lvdisplay /dev/VolGroup00
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID MDjH1r-PET2-yQy7-zxMe-ZCUw-DgnI-jSzRSZ
LV Write Access read/write
LV Status available
# open 1
LV Size 35.22 GB
Current LE 1127
Segments 1
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 oijEhS-WXGK-3FbI-0WI2-zSS8-LQT0-yqF2hC
LV Write Access read/write
LV Status available
# open 1
LV Size 1.94 GB
Current LE 62
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

I do not see the 1 TB drive listed
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

[HROAdmin26]

You have a collision - that is, the name of your NEWLY installed LVM setup is VolGroup00, and the name of the OLD volume group is the same.

Google: how to recover lvm when volume group with same name exists

Getting to the data proved challenging, both because the data was on a logical volume hidden inside a RAID device, and because the volume group on the RAID device had the same name as the volume group on the recovery system.

*Assuming* the data on /dev/sda2 is not corrupt AND that there are no other disks missing that were part of the OLD VolGroup00 volume group, you can follow the link above to try and recover. You aren't using RAID devices, so you can skip forward to page 2, just under "Listing 5" to where it says:

Recovering and Renaming the LVM2 Volume

[bigado]

I ran the command:
]# mdadm --examine --scan /dev/sda1 /dev/sda2 >> /etc/mdadm.conf

The command created the config file /etc/mdadm.conf but when opened the file was blank