Mounting secondary hardisk - Page 2

notageek · #16 22nd February 2008, 09:53 AM

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 · #17 22nd February 2008, 09:55 AM

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 · #18 22nd February 2008, 09:56 AM

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 · #19 22nd February 2008, 09:58 AM

fair enough then mate....

notageek · #20 22nd February 2008, 09:58 AM

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 · #21 22nd February 2008, 10:05 AM

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 · #22 22nd February 2008, 10:08 AM

Here are the results =)

Quote:

[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 ]

Quote:

[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

Quote:

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 · #23 22nd February 2008, 10:14 AM

Here is ur edit also

Quote:

[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 · #24 22nd February 2008, 10:15 AM

Here is rest of it

Quote:

[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

Quote:

[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 · #25 22nd February 2008, 10:15 AM

Hmm...

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

crab_com · #26 22nd February 2008, 10:18 AM

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

notageek · #27 22nd February 2008, 10:30 AM

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 · #28 22nd February 2008, 10:32 AM

yer i don't wanna lose anything aye

crab_com · #29 22nd February 2008, 10:44 AM

so hows the search going found anything?

notageek · #30 22nd February 2008, 10:46 AM

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