Mounting secondary hardisk

[crab_com]

Hey all,

My problem is that my FC5 machine just keeps on doing a reboot on startup and loops.

What I've done is removed the hard disk an put it in my F8 machine.

I'm wondering how do i Mount this correctly so I'm able to backup the contents on the hard disk.

Cheers, Crab

[notageek]

What is the output of fdisk -ls ?

[crab_com]

fdisk -ls

Disk /dev/sda: 250.0 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf133e081

Device Boot Start End Blocks Id System
/dev/sda1 * 1 25 200781 83 Linux
/dev/sda2 26 30401 243995220 8e Linux LVM

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

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

Disk /dev/dm-0: 247.7 GB, 247732371456 bytes
255 heads, 63 sectors/track, 30118 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x30307800

Disk /dev/dm-1 doesn't contain a valid partition table

[notageek]

I'm assuming that your second hard drive from FC5 box is the one listed here.

There is a linux partition and a Linux LVM on that drive.

Mounting linux partition is easy mount /dev/sdb1 /mount/point

To mount the linux LVM I'm checking to see if there's an option (like we have in software raids) to assemble a pre-existing lvm.


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

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

Edit: I was away from my pc.

[crab_com]

[root@localhost ~]# mount /dev/sdb1 /mount/point
mount: mount point /mount/point does not exist

seems it didn't want to mount it...

[notageek]

Wait I'm confused, Is you second hard drive the 40 GB hdd, or the 250GB?

[notageek]

[root@localhost ~]# mount /dev/sdb1 /mount/point
mount: mount point /mount/point does not exist

seems it didn't want to mount it...

Was an example, I was refering to any empty directory where you'd want to mount the partition, usually /mnt is free, try mount /dev/sdb1 /mnt

[crab_com]

yeah the 40gb disk is the second drive.....

[crab_com]

mount /dev/sdb1 /mnt worked so that mounted that partition how about the other 1?


[root@localhost ~]# mount /dev/sdb1 /mnt
[root@localhost ~]# cd /mnt/
[root@localhost mnt]# ls
config-2.6.15-1.2054_FC5 lost+found
config-2.6.20-1.2307.fc5 System.map-2.6.15-1.2054_FC5
grub System.map-2.6.20-1.2307.fc5
initrd-2.6.15-1.2054_FC5.img vmlinuz-2.6.15-1.2054_FC5
initrd-2.6.20-1.2307.fc5.img vmlinuz-2.6.20-1.2307.fc5
[root@localhost mnt]#

[notageek]

Okay for the LVM partition, there's no easy one line command, this is how you'd "assemble" an LVM.

Before we go do that I want to see the output of the following commands

pvdisplay
lvdisplay
vgdisplay

Please note, since we're are working on a hdd with exisiting data, there's always a risk of losing date, so be very careful running commands that might damage data on your hdd.

I'll not be responsible for any dataloss ;)


Edit: Please run all the above commands with verbose output e.g. pvdisplay -vv

[crab_com]

hehe yes we both better be very careful because I've got a well written squid.conf file i need to recover ;)
Just running the commands now...

[crab_com]

Here you go mate

[root@localhost mnt]# pvdisplay
--- Physical volume ---
PV Name /dev/sda2
VG Name VolGroup00
PV Size 232.69 GB / not usable 4.58 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 7446
Free PE 1
Allocated PE 7445
PV UUID geZaUD-9ekk-xfn3-bs0p-2wkY-3qnf-T3tBwM



[root@localhost mnt]# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID aevge5-TmUR-zcuA-EXab-EG6b-70bI-tYQSzI
LV Write Access read/write
LV Status available
# open 1
LV Size 230.72 GB
Current LE 7383
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID RQ6fAa-iinv-HUke-SwUI-MPx3-ZMRd-5wWbbZ
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@localhost mnt]# vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 232.69 GB
PE Size 32.00 MB
Total PE 7446
Alloc PE / Size 7445 / 232.66 GB
Free PE / Size 1 / 32.00 MB
VG UUID MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9

[notageek]

Okay great, the task is far simpler than I thought. Here's how to get that lvm mounted.

1. Unmount the existing partition with umount /mnt
2. To mount the LVM try mount /dev/VolGroup00/LogVol00 /mnt

Edit:
Wait, I see that you have to logical volumes, here's how you'll get them both mounted.

1. umount /mnt
2. mkdir /mnt/lv1
3. mkdir /mnt/lv2
4. mount /dev/VolGroup00/LogVol00 /mnt/lv1
5. mount /dev/VolGroup00/LogVol01 /mnt/lv2

[crab_com]

thats my F8 partition mate...

[crab_com]

hehe i see now ;) edited ur post ;)

[notageek]

My mistake, I misread the output of pvdisplay.

Hmm... so there's a possibility of data loss, lemme be absolutely sure about what we may try next.

Will be back.

[crab_com]

ok done what u said but we have run into a brick wall =(

[root@localhost /]# mount /dev/VolGroup00/LogVol01 /mnt/lv2
/dev/mapper/VolGroup00-LogVol01 looks like swapspace - not mounted
mount: you must specify the filesystem type

[notageek]

Yeah, my mistake I took you to a wrong path, like I said, I misread the output of pvdisplay. The second pv isn't listed.

[crab_com]

fair enough then mate....

[notageek]

Probably a silly question, but did you reboot your f8 box after adding the second hdd?

Lemme check how we can get the 2nd pv activated without destroying data.

[notageek]

Running pvcreate will definitely destroy data (as far as my understanding of lvm goes).

Lets run these commands to check if they can be detected (they seem to be non destructive) and run them on the same sequence.

1. pvscan
2. vgscan
3. lvscan

Lets see how that goes.

Edit: I have to stop rushing my posts.

After you've run those commands try
1. pvdisplay -vv
2. vgdisplay -vv
3. lvdisplay -vv

[crab_com]

Here are the results =)

[root@localhost ~]# pvscan
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
PV /dev/sdb2 VG VolGroup00 lvm2 [37.16 GB / 32.00 MB free]
PV /dev/sda2 VG VolGroup00 lvm2 [232.69 GB / 32.00 MB free]
Total: 2 [269.84 GB] / in use: 2 [269.84 GB] / in no VG: 0 [0 ]


[root@localhost ~]# vgscan
Reading all physical volumes. This may take a while...
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
Found volume group "VolGroup00" using metadata type lvm2
Found volume group "VolGroup00" using metadata type lvm2



WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
PV /dev/sdb2 VG VolGroup00 lvm2 [37.16 GB / 32.00 MB free]
PV /dev/sda2 VG VolGroup00 lvm2 [232.69 GB / 32.00 MB free]
Total: 2 [269.84 GB] / in use: 2 [269.84 GB] / in no VG: 0 [0 ]
[root@localhost ~]# vgscan
Reading all physical volumes. This may take a while...
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
Found volume group "VolGroup00" using metadata type lvm2
Found volume group "VolGroup00" using metadata type lvm2
[root@localhost ~]# lvscan
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
ACTIVE '/dev/VolGroup00/LogVol00' [230.72 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit

[crab_com]

Here is ur edit also

[root@localhost ~]# pvdisplay -vv
Setting global/locking_type to 1
File-based locking selected.
Setting global/locking_dir to /var/lock/lvm
Scanning for physical volume names
/dev/ramdisk: No label detected
/dev/dm-0: No label detected
/dev/ram: No label detected
/dev/sda1: No label detected
/dev/dm-1: No label detected
/dev/ram2: No label detected
/dev/sda2: lvm2 label detected
/dev/ram3: No label detected
/dev/ram4: No label detected
/dev/ram5: No label detected
/dev/ram6: No label detected
/dev/ram7: No label detected
/dev/ram8: No label detected
/dev/ram9: No label detected
/dev/ram10: No label detected
/dev/ram11: No label detected
/dev/ram12: No label detected
/dev/ram13: No label detected
/dev/ram14: No label detected
/dev/ram15: No label detected
/dev/sdb1: No label detected
/dev/sdb2: lvm2 label detected
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
/dev/sdb2: lvm2 label detected
/dev/sdb2: lvm2 label detected
/dev/sdb2: size is 77947380 sectors
Fixing up missing format1 size (37.17 GB) for PV /dev/sdb2
/dev/sda2: lvm2 label detected
/dev/sda2: lvm2 label detected
Locking /var/lock/lvm/V_VolGroup00 RB
/dev/sdb2: lvm2 label detected
/dev/sdb2: lvm2 label detected
/dev/sdb2: size is 77947380 sectors
Fixing up missing format1 size (37.17 GB) for PV /dev/sdb2
--- Physical volume ---
PV Name /dev/sdb2
VG Name VolGroup00
PV Size 37.17 GB / not usable 12.24 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 1189
Free PE 1
Allocated PE 1188
PV UUID UQogfV-TSwE-DSdz-fw8e-N456-j78Y-L9ppYB

Unlocking /var/lock/lvm/V_VolGroup00
Locking /var/lock/lvm/V_VolGroup00 RB
/dev/sda2: lvm2 label detected
/dev/sda2: lvm2 label detected
--- Physical volume ---
PV Name /dev/sda2
VG Name VolGroup00
PV Size 232.69 GB / not usable 4.58 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 7446
Free PE 1
Allocated PE 7445
PV UUID geZaUD-9ekk-xfn3-bs0p-2wkY-3qnf-T3tBwM

Unlocking /var/lock/lvm/V_VolGroup00

[crab_com]

Here is rest of it

[root@localhost ~]# vgdisplay -vv
Setting global/locking_type to 1
File-based locking selected.
Setting global/locking_dir to /var/lock/lvm
Finding all volume groups
/dev/ramdisk: No label detected
/dev/dm-0: No label detected
/dev/ram: No label detected
/dev/sda1: No label detected
/dev/dm-1: No label detected
/dev/ram2: No label detected
/dev/sda2: lvm2 label detected
/dev/ram3: No label detected
/dev/ram4: No label detected
/dev/ram5: No label detected
/dev/ram6: No label detected
/dev/ram7: No label detected
/dev/ram8: No label detected
/dev/ram9: No label detected
/dev/ram10: No label detected
/dev/ram11: No label detected
/dev/ram12: No label detected
/dev/ram13: No label detected
/dev/ram14: No label detected
/dev/ram15: No label detected
/dev/sdb1: No label detected
/dev/sdb2: lvm2 label detected
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
Locking /var/lock/lvm/V_VolGroup00 RB
Finding volume group "VolGroup00"
/dev/sdb2: lvm2 label detected
/dev/sdb2: lvm2 label detected
/dev/sdb2: size is 77947380 sectors
Fixing up missing format1 size (37.17 GB) for PV /dev/sdb2
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 37.16 GB
PE Size 32.00 MB
Total PE 1189
Alloc PE / Size 1188 / 37.12 GB
Free PE / Size 1 / 32.00 MB
VG UUID AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID HFb9EA-k8Ik-srAe-sj4v-Ca2M-w128-jbNySK
LV Write Access read/write
LV Status available
# open 1
LV Size 36.56 GB
Current LE 1170
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID P9JMV3-yU3W-uCP3-o2Le-P7FM-3OvP-Eh0sle
LV Write Access read/write
LV Status available
# open 1
LV Size 576.00 MB
Current LE 18
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1

--- Physical volumes ---
PV Name /dev/sdb2
PV UUID UQogfV-TSwE-DSdz-fw8e-N456-j78Y-L9ppYB
PV Status allocatable
Total PE / Free PE 1189 / 1

Archiving volume group "VolGroup00" metadata (seqno 3).
Archiving volume group "VolGroup00" metadata (seqno 3).
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 3).
Unlocking /var/lock/lvm/V_VolGroup00
Locking /var/lock/lvm/V_VolGroup00 RB
Finding volume group "VolGroup00"
/dev/sda2: lvm2 label detected
/dev/sda2: lvm2 label detected
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 232.69 GB
PE Size 32.00 MB
Total PE 7446
Alloc PE / Size 7445 / 232.66 GB
Free PE / Size 1 / 32.00 MB
VG UUID MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID aevge5-TmUR-zcuA-EXab-EG6b-70bI-tYQSzI
LV Write Access read/write
LV Status available
# open 1
LV Size 230.72 GB
Current LE 7383
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID RQ6fAa-iinv-HUke-SwUI-MPx3-ZMRd-5wWbbZ
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

--- Physical volumes ---
PV Name /dev/sda2
PV UUID geZaUD-9ekk-xfn3-bs0p-2wkY-3qnf-T3tBwM
PV Status allocatable
Total PE / Free PE 7446 / 1

Archiving volume group "VolGroup00" metadata (seqno 3).
Archiving volume group "VolGroup00" metadata (seqno 3).
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 3).
Unlocking /var/lock/lvm/V_VolGroup00


[root@localhost ~]# lvdisplay -vv
Setting global/locking_type to 1
File-based locking selected.
Setting global/locking_dir to /var/lock/lvm
Finding all logical volumes
/dev/ramdisk: No label detected
/dev/dm-0: No label detected
/dev/ram: No label detected
/dev/sda1: No label detected
/dev/dm-1: No label detected
/dev/ram2: No label detected
/dev/sda2: lvm2 label detected
/dev/ram3: No label detected
/dev/ram4: No label detected
/dev/ram5: No label detected
/dev/ram6: No label detected
/dev/ram7: No label detected
/dev/ram8: No label detected
/dev/ram9: No label detected
/dev/ram10: No label detected
/dev/ram11: No label detected
/dev/ram12: No label detected
/dev/ram13: No label detected
/dev/ram14: No label detected
/dev/ram15: No label detected
/dev/sdb1: No label detected
/dev/sdb2: lvm2 label detected
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
Locking /var/lock/lvm/V_VolGroup00 RB
/dev/sda2: lvm2 label detected
/dev/sda2: lvm2 label detected
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID aevge5-TmUR-zcuA-EXab-EG6b-70bI-tYQSzI
LV Write Access read/write
LV Status available
# open 1
LV Size 230.72 GB
Current LE 7383
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID RQ6fAa-iinv-HUke-SwUI-MPx3-ZMRd-5wWbbZ
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

Unlocking /var/lock/lvm/V_VolGroup00

[notageek]

Hmm...

Good news is your second physical volume is detected, the bad news is you've 2 VG's with same name.

[crab_com]

hehe explains why it won't detect way of changing the name?

[notageek]

Hmm.. there's no easy solution, there's data loss at stake here.

My thoughts on the issue are

1. Create another volume group.
2. Add the 2nd partion from the send hdd to the new volume group.
3. Create a logical volume.
4. Mount the logical volume.

The the biggest question here is... Will creating new volume group and logical volume destroy data?

Let me google this.

[crab_com]

yer i don't wanna lose anything aye

[crab_com]

so hows the search going found anything?

[notageek]

Q. Will creating new volume group and logical volume destroy data?
A. I guess not, since we're not making any changes at block level or creating a new file system.

But as I said before, I'll not be responsible for any data loss. ;)

So here's how to go about it.

1. vgcreate volume_group_name /dev/sdb2
2. vgdisplay -v volume_group_name
3. lvcreate -nlogical_volume2 volume_group_name
4. lvdisplay -v logical_volume2
5. mount /dev/volume_group_name/logical_volume2 /mnt/lv2

Edit: Replace volume_group_name with your favourite volume group name ;)

[crab_com]

[root@localhost ~]# vgcreate volume_group_name /dev/sdb2
WARNING: Duplicate VG name VolGroup00: Existing MJLN2Q-X3Va-kW4s-l9jj-d2kR-60yZ-emh4K9 (created here) takes precedence over AxOSH3-u5G1-1Qyt-xhdB-QNKT-Q8Vy-ghl13q
Physical volume '/dev/sdb2' is already in volume group 'VolGroup00'
Unable to add physical volume '/dev/sdb2' to volume group 'volume_group_name'.

[crab_com]

come up with anything champion?

[notageek]

Hey, I'm back. Lemme see what can I find as your solution.

[crab_com]

thankyou mate

[notageek]

Still looking, in the meantime post the output of

# cat /etc/lvmtab

[notageek]

I think I have a solution, however for that we need a second system (is your FC5 system no good at all?).

Well the process is listed here (http://docs.hp.com/en/5991-6481/ch03s03.html#bajbfead) and here (http://docs.hp.com/en/5991-6481/ch03s03.html#bajhhfje) .

Okay the process is little "twisted" let me try to explain the gist of it.

On a second sytem (preferably on the original FC5 on single user mode) try the following.

1. Deactivate the volume group.
2. Export the volume group.

On the target system (where the hdd will finally reside)

1. Importt the volume group to a new volume group.
2. Activate the volume group.
3. Mount the logical volume

Under no circumstances should the "pvcreate" command be executed if data preservation is required.

[crab_com]

no such file mate did u mean

cat /etc/lvm ??

[notageek]

Nope I meant lvmtab

[notageek]

Hey by the way, there's a GUI to manipulate LVM, but I've never used it so you're on you own on the GUI thing.

try

# system-config-lvm

If the system complains about the command and if you've logged in as "su -" then try

# yum install system-config-lvm

Not sure if this utility will help you fix the issue but its worth a try.

[crab_com]

nah mate this is no good won't help me mount the disk basically same trouble as before....

Thanks for the help mate but I might give this one to my mate hes also a linux admin like ur self he can work on it and get me my backup if possible.

Thanks for the help mate..

Cheers, Crab

[notageek]

Cheers mate.