Re: Cannot mount old drive with LVM partition - help!



noi <noi@xxxxxxxx> wrote in news:dLLTg.10191$6S3.7321
@newssvr25.news.prodigy.net:

Hard time following what you've done. All I see is one 200GB HD
/dev/hdb1 as a FC5 LVM Are you mount /dev/hda as you old drive are
you
adding /dev/hdb to the LVM volume group? Have you reviewed the
command
set for LVM and FAQs at FC5 or LVM web sites?

I want to mount /dev/hdb2, that is where the LVM is located, containing
my original FC3 installation. That is what I am unable to do. /dev/hda is
the current FC5 installation, is active, and is visible.

Well, I am learning about LVMs now. That was the default Fedora install,
I don't remember being asked if I wanted LVM or not. I just installed FC5
and took the default install and ended up with an LVM again. I think that
a serious problem is that both LVM volumes have the same name. I really
don't understand this stuff enough to get the volume mounted though.

Could post lvdisplay, pvdisplay, fdisk -l /dev/hda and /dev/hdb ?

Sure. It is a bit difficult now as the new setup is not complete. I don't
have the domains setup, ssh is not setup, samba is not working yet, etc.,
so I think I can run those commands and catch the output, email that to
myself, then post them for you here. AT least I got my desktop terminals
back. FC5 does not even offer term windows in x anymore by default and I
went back to booting to run level 3 instead of run level 5 and starting x
with startx.
---------------------------------------------------------------------
root@ohmster ~]# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID AEkIRn-4p4I-pjo1-OI8I-GPGx-RUzf-K7iI9G
LV Write Access read/write
LV Status available
# open 1
LV Size 184.22 GB
Current LE 5895
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID ghCyjf-gFRp-qN2Z-QyBc-eEl3-TAO0-ReRTnz
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 0
Block device 253:1

[root@ohmster ~]#
---------------------------------------------------------------------
[root@ohmster ~]# pvdisplay
--- Physical volume ---
PV Name /dev/hda2
VG Name VolGroup00
PV Size 186.19 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 5958
Free PE 1
Allocated PE 5957
PV UUID 85v0Vl-MK33-Kbhl-mW22-kBhT-Uv6B-967SbT

[root@ohmster ~]#
---------------------------------------------------------------------
[root@ohmster ~]# fdisk -l /dev/hda

Disk /dev/hda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 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 24321 195254010 8e Linux LVM
[root@ohmster ~]#
---------------------------------------------------------------------
[root@ohmster ~]# fdisk -l /dev/hdb

Disk /dev/hdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 24792 199037317+ 8e Linux LVM
[root@ohmster ~]#
---------------------------------------------------------------------
This is freaking me out man. I really need to get the servers up and
running and all the rest of the stuff that is on the old FC3 disk drive.
All the configs are there and the old system will boot and run again if I
pull the IDE cable from the new drive and plug it back to the old drive
as first in line (Cable select method.). There has got to be some way to
mount that old system, I was googling and reading and someone else had
this problem and they figured that they could not mount the partition
because the volume group had the same name as the current volume group.
That is the situation that I have because I went with the default Fedora
install.

In x, there is an admin tool for Logical Volume Managment. It is
graphical and it shows my current volume groups as well as "Uninitialized
Entries". /dev/hdb1 and /dev/hdb2 are shown. The only thing that the
application will do for me is to "Initialize the Entry". If I try to do
that, I get a warning that "All data on disk entry /dev/hdb2 will be
lost, continue?" Hell no!

Please help me with this.
--
~Ohmster
theohmster at comcast dot net
Put "messageforohmster" in message body
to pass my spam filter.
.



Relevant Pages

  • Re: lvm re-install strategy
    ... The other machine is just have to be able to see the disk. ... You might find that if you go back and re-read the documentation for LVM ... If that is the case then with the DVD install just create a new logical ... My idea is to devote sda to the system, so one vg on sda2 with logical ...
    (Fedora)
  • Re: fedora-list Digest, Vol 53, Issue 291
    ... network configuration file ... Re: New support lists? ... LVM - Install F9 without LVM ...
    (Fedora)
  • Re: How to fix two disks with the same Volume Group?
    ... disk drive was slowly failing. ... need root password then (it seems a little redundant but anyway... ... you'll have to prefix the lvm commands with lvm, ... Is this under repair on the install cd? ...
    (Fedora)
  • Installing Lenny on LVM using debootstrap
    ... I followed the instruction in Appendix D of the installation manual, but they seem to have changed since I installed Lenny the first time and there is no mention of how to install on LVM volumes. ... but I can not access the LVM volumes to mount them within the chroot. ...
    (Debian-User)
  • Re: Data transfer from one HD to another
    ... Install new disk as primary master. ... Boot from CD and install minimal system (you can even abort once it has created the file system, the only purpose of this step is to create the slices and newfs. ... mount /dev/ad1s1a /mnt ... Do the same sequence of steps for /tmp, mounting /tmp read/write and using L switch in dump. ...
    (freebsd-stable)