trying to mount usb/hard drive

[bruce]

Hi,

The drive from the 1st system is a 640G drive

The partition data from the system monitor app gives the following:

/dev/mapper/vg_dell45_lv_root        /
/dev/mapper/vg_dell45_lv_apps        /apps
/dev/mapper/vg_dell45_lv_backup        /backup
/dev/sda1                /boot
/dev/mapper/vg_dell45_lv_home        /home

When I pop the drive into a usb drive bay to examine/view the drive
from the 2nd system, I only get the 340M slice of the drive.

when I do a "fdisk -l" on the drives in the 2nd system, it sees the "drive",

Disk /dev/sdc: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28000000

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2              64       77826   624618496   8e  Linux LVM

So the question is what do I have to "enter/type" at the cmdline to
actually mount the given partition "/apps, /home" of the 640G drive to
be able to access the underlying data??

thanks

[Mark Haney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/20/2013 11:39 AM, bruce wrote:
> Hi,
>
> The drive from the 1st system is a 640G drive
>
> The partition data from the system monitor app gives the
> following:
>
> /dev/mapper/vg_dell45_lv_root        / 
> /dev/mapper/vg_dell45_lv_apps        /apps 
> /dev/mapper/vg_dell45_lv_backup        /backup /dev/sda1
> /boot /dev/mapper/vg_dell45_lv_home        /home

Make sure you have the lvm utils installed and mount by lv name.
Here's some decent instructions I googled:

http://linuxers.org/howto/how-mount-linux-lvm-volume-partitions-linux

May or may not be precisely correct being a couple of years old, but I
believe the process is similar regardless.

- -- 
Mark Haney
Network Administrator/IT Support
Practichem
W:919-714-8428
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJStHbIAAoJEDgEuzPE0JQv/FgIAKuqr9MWWj4ev3qYSwQClR/5
> lqMTRjw1mjhRNREpCQa4tajt7VM9IpUlIu21WF39n+fmLpwWHUrpID7fEoH50o7Q
> ns6sKNlt3f/5VCYIJo2ADKsUxMNRlZi1hpL0rj/gCmYrVuUH+xSjHQK5k7vg1IA3
> nXfeGd1AFclil/w1NbHq6wy1RFALwf8aJCfd0F7Ru4QqM+YId8uaP9X6R7OfpBu8
> EfUZgtkmrncEXu/935q7Q79/ehcP0ETVQ/N8h9iC9giXBTHrWOwgWpI6gHiJnblz
> xBNjk155OvHB9sy5mxKhrND9DAM0q//Xyv0Mvtp5Xmju9fJpnkEBxA+5Oyf/FGM=
> =K50v
> -----END PGP SIGNATURE-----

[bruce]

http://serverfault.com/questions/451781/mounting-an-old-lvm-hard-drive-in-fe...

as a few people mentioned

the vgchange to activate the vol is required.

thanks

On Fri, Dec 20, 2013 at 11:56 AM, Mark Haney  wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/20/2013 11:39 AM, bruce wrote:
> > Hi,
> >
> > The drive from the 1st system is a 640G drive
> >
> > The partition data from the system monitor app gives the
> > following:
> >
> > /dev/mapper/vg_dell45_lv_root        /
> > /dev/mapper/vg_dell45_lv_apps        /apps
> > /dev/mapper/vg_dell45_lv_backup        /backup /dev/sda1
> > /boot /dev/mapper/vg_dell45_lv_home        /home
>
> Make sure you have the lvm utils installed and mount by lv name.
> Here's some decent instructions I googled:
>
> http://linuxers.org/howto/how-mount-linux-lvm-volume-partitions-linux
>
> May or may not be precisely correct being a couple of years old, but I
> believe the process is similar regardless.
>
> Mark Haney
> Network Administrator/IT Support
> Practichem
> W:919-714-8428
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJStHbIAAoJEDgEuzPE0JQv/FgIAKuqr9MWWj4ev3qYSwQClR/5
> lqMTRjw1mjhRNREpCQa4tajt7VM9IpUlIu21WF39n+fmLpwWHUrpID7fEoH50o7Q
> ns6sKNlt3f/5VCYIJo2ADKsUxMNRlZi1hpL0rj/gCmYrVuUH+xSjHQK5k7vg1IA3
> nXfeGd1AFclil/w1NbHq6wy1RFALwf8aJCfd0F7Ru4QqM+YId8uaP9X6R7OfpBu8
> EfUZgtkmrncEXu/935q7Q79/ehcP0ETVQ/N8h9iC9giXBTHrWOwgWpI6gHiJnblz
> xBNjk155OvHB9sy5mxKhrND9DAM0q//Xyv0Mvtp5Xmju9fJpnkEBxA+5Oyf/FGM=
> =K50v
> -----END PGP SIGNATURE-----
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Rick Stevens]

On 12/20/2013 08:56 AM, Mark Haney issued this missive:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/20/2013 11:39 AM, bruce wrote:
> > Hi,
> >
> > The drive from the 1st system is a 640G drive
> >
> > The partition data from the system monitor app gives the
> > following:
> >
> > /dev/mapper/vg_dell45_lv_root        /
> > /dev/mapper/vg_dell45_lv_apps        /apps
> > /dev/mapper/vg_dell45_lv_backup        /backup /dev/sda1
> > /boot /dev/mapper/vg_dell45_lv_home        /home
>
> Make sure you have the lvm utils installed and mount by lv name.
> Here's some decent instructions I googled:
>
> http://linuxers.org/howto/how-mount-linux-lvm-volume-partitions-linux
>
> May or may not be precisely correct being a couple of years old, but I
> believe the process is similar regardless.

True. In a nutshell:

# vgchange -ay		(Makes the VG known to the kernel)
    # ls /dev/mapper	(To find the VG-LV name of the LVM)
    # mount /dev/mapper/<lvname> /mountpoint
    			(Mount the LVM at /mountpoint)

Example:

# vgchange -ay
    # ls /dev/mapper
    /dev/mapper:
    control  VolGroup00-LogVol00  VolGroup00-LogVol01
    # mount /dev/mapper/VolGroup00-LogVol01 /mountpoint

WARNING:
If system2 uses LVMs that were created using Anaconda's defaults (the
above is an example of such a beast) AND the USB drive was done in a
similar manner, you may have duplicate VG and LV names and that won't
work. You will need to (at least) change the VG name on the USB drive
(see "man vgrename" for help there).

For this reason, I generally name the VGs after the hostname of the
machine they were created on. For example, my laptop, "golem4", has:

[root@golem4 ~]# ls /dev/mapper
    control  vg_golem4-lv_home  vg_golem4-lv_root  vg_golem4-lv_swap

so I can move its drive to another machine if necessary and not have a
VG name conflict.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-  "Men occasionally stumble over the truth, but most of them pick"  -
-     themselves up and hurry off as if nothing had happened."       -
-                                  -- Winston Churchill              -
----------------------------------------------------------------------

[Robert Moskowitz]

On 12/20/2013 11:39 AM, bruce wrote:
> Hi,
>
> The drive from the 1st system is a 640G drive
>
> The partition data from the system monitor app gives the following:
>
> /dev/mapper/vg_dell45_lv_root        /
> /dev/mapper/vg_dell45_lv_apps        /apps
> /dev/mapper/vg_dell45_lv_backup        /backup
> /dev/sda1                /boot
> /dev/mapper/vg_dell45_lv_home        /home
>
> When I pop the drive into a usb drive bay to examine/view the drive
> from the 2nd system, I only get the 340M slice of the drive.

Here is my notes on working with LVMs:

LVM partitions

I used the following to figure it out.
http://tldp.org/HOWTO/LVM-HOWTO/

You'll probably need to do /sbin/vgscan to figure out the lvm name then
run

/sbin/vgchange -a y;
mount /dev/VolGroup00/LogVol00 /mnt/whatever

To find the mount point try

ls /dev/LVM_Group_name/