LVM Mount Problem

[Euralis]

Hello openSUSE users,

perhaps some of you here can help me. Basically my situation is this, a couple of days ago I formatted a hard drive on my friends computer because I wanted to make sure that I did not do anything wrong. Anyway, I ended up formatting it, loading fedora on it, and bringing it home. Surprise Surprise, I pop it into my computer and it does not work. A failure to mount of some sort it claimed. Anyway, I dug out another hard drive and I put openSUSE on it. Currently I am using it to write this thread. My problem is simple: I need to get onto this other hard drive and pull some data off, the only problem is that I cant mount it. Since I am using open SUSE10.3 to mount this, you guys seemed like a good choice to ask about how to do this.

I am told that this hard drive is an LVM Volume, I also know that there are special rules for mounting them. I found this out through the following command line:

fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00076fa1

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 * 263 2873 20972857+ 83 Linux
/dev/sda3 2874 19457 133210980 83 Linux

Disk /dev/sdb: 300.0 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xff3cff3c

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 25 200781 83 Linux
/dev/sdb2 26 36481 292832820 8e Linux LVM

Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x107f1c04

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 14593 117218241 c W95 FAT32 (LBA)

Then after i confirmed this I typed:

pvs -- /dev/sdb2

PV VG Fmt Attr PSize PFree
/dev/sdb2 VolGroup00 lvm2 a- 279.25G 32.00M


So then, based upon that, I input this:

lvdisplay /dev/VolGroup00

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID io7mAB-O9B5-hqXU-zH4k-X9LX-BEIG-oC0qXL
LV Write Access read/write
LV Status NOT available
LV Size 277.28 GB
Current LE 8873
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID lGKM3U-dEs4-4ccU-mo05-62Eq-w1VL-R9djfj
LV Write Access read/write
LV Status NOT available
LV Size 1.94 GB
Current LE 62
Segments 1
Allocation inherit
Read ahead sectors 0


Everything looks like its going to be great right? Wait till you see what happens next, now I am going to try mounting it.

mount -t ext3 /dev/VolGroup00/LogVol01 /mnt

mount: special device /dev/VolGroup00/LogVol01 does not exist


In short, why did it do this? What should I do now?

[raghaven.kumar]

did you have any data on that lvm

or else i will suggest reformat that lvm

still if you dont get try typing

partprobe

[Dies]

LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID lGKM3U-dEs4-4ccU-mo05-62Eq-w1VL-R9djfj
LV Write Access read/write
LV Status NOT available

LV Size 1.94 GB

Now it makes a little more sense...

Notice that the one you are trying to mount is only like 2 gigs ?

That means that this is more than likely your Swap partition unless you have a 277 gig Swap.

What happens when you run the same command for the other one?

mount -t ext3 /dev/VolGroup00/LogVol00 /mnt

[Euralis]

LOL Nice to see you again Dies.

I actually tried what you suggested out of sheer "thoroughness"; no i did not notice that it could be my swap partition.

here is what I got:

mount -t ext3 /dev/VolGroup00/LogVol00 /mnt

mount: special device /dev/VolGroup00/LogVol00 does not exist

thats what I get.

raghaven, when I did partprobe -s this is what i got:
/dev/sda: msdos partitions 1 2 3
/dev/sdb: msdos partitions 1 2
/dev/sdc: msdos partitions 1

its odd that its ms dos, i have not had ms dos on any of my parts forever.

[Dies]

Hmm.. sorry, I guess I should get over my hatred of LVM and actually learn how to use it.
I've been avoiding it like the plague.

In any case check the other thread and let me know how that goes.

[Euralis]

will do Dies,

Thanx

[raghaven.kumar]

seems your disk is not initialized

i never tried this but you can try it

After rebooting the system or running vgchange -an, you will not be able to access your VGs and LVs. To reactivate the volume group, run:

# vgchange -a y my_volume_group

this is from the article
http://tldp.org/HOWTO/LVM-HOWTO