carnold6 wrote:
[color=blue]
Device Boot Start End Blocks Id System
/dev/sdb1 63 112454 56196 de Dell Utility
/dev/sdb2 112640 16889855 8388608 8e Linux LVM
/dev/sdb3 * 16900380 17318069 208845 83 Linux
/dev/sdb4 17318070 488279609 235480770 f W95 Ext’d
(LBA)
/dev/sdb5 17318133 20402549 1542208+ 82 Linux swap /
Solaris
/dev/sdb6 20402613 488279609 233938498+ 8e Linux LVM[/color]
sdb1 is ~27 MB Dell Utility
sdb2 is 4 GB LVM
sdb3 is 100 MB boot
sdb4 is ~112 GB extended partition
sdb5 is ~753 MB Linux swap
sdb6 is ~111 GB LVM
Let’s look at what we have and maybe we can determine where / is:
-
sdb3 is the partition we boot from. It could be / but because it is
only 100 MB I expect it is just a boot partition (/boot).
-
sdb4 is an extended partition. It is just a container for sdb5 and
sdb6 so we don’t have to worry about it.
-
sdb1 and sdb4 are the Dell and swap partitions so they can be
excluded.
-
sdb2 and sdb6 are managed by LVM and likely contain one or more
logical volumes.
Since that’s all there is, my guess would be that / is a LV on sdb2 or
sdb6.
If we know the names of the volume groups and logical volumes, we can
then mount the logical volumes. It’s been a while since I did this, and
I am unable to boot into rescue mode at this time to try it but here is
how to get the VG/LV names…
First scan the disk to find the Volume Groups:
server:~ # lvm pvscan
PV /dev/sdc VG vg200 lvm2 [1.33 TB / 0 free]
PV /dev/sdb1 VG vg100 lvm2 [488.26 GB / 143.26 GB free]
Total: 2 [1.81 TB] / in use: 2 [1.81 TB] / in no VG: 0 [0 ]
The name of the volume group is shown immediately after the “VG”
(e.g.vg200). There may be more than one volume group shown.
To see the logical volumes in a volume group, the volume group must be
activated with the vgchange command. For substitute the
Volume Group name returned by your pvscan command. (e.g. vg200).
server:~ # lvm vgchange -ay <Volume Group>
Now, we scan for Logical Volumes with the lvscan command.
server:~ # lvm lvscan
ACTIVE '/dev/vg200/v200' [1.33 TB] inherit
In this example we see the logical volume name is v200. Your LV name is
probably different but We now have the information needed to mount the
volume.
Finally we can mount the LV using the information returned by the
lvscan command. For example:
server:~ # mount /dev/vg200/v200 /mnt
Of course you would substitute your own volume group and logical volume
name. If the name of the LV used for / is not obvious, you may have to
unmount the volume and try another one from the same or a different
Volume Group.
When you are finished working with a particular Volume Group you should
deactivate it so it is no longer accessible:
server:~ # lvm vgchange -an <Volume Group>
Note the difference from the first time: “-an” will deactivate; “-ay”
will activate.
This is pretty much from memory and few reference documents. I hope it
helps.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are using the web interface,
show your appreciation and click on the star below…
