Hi!
I have a setup with three software RAID arrays, which have been
combined into one LVM2 container in EVMS. I had some trouble with
harddisks in one of the RAID arrays, but I'm pretty sure that the
data in the array is fine.
When I boot a Live CD without EVMS and issue a 'vgdisplay --verbose'
I get the following:
--- Volume group ---
VG Name datacontainer1
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 27
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 3
Act PV 3
VG Size 2.66 TB
PE Size 32.00 MB
Total PE 87150
Alloc PE / Size 87150 / 2.66 TB
Free PE / Size 0 / 0
VG UUID y1wkSA-Mp1z-3oRj-3fTU-9aVA-ZIQN-llWqUP
--- Logical volume ---
LV Name /dev/datacontainer1/dataregion
VG Name datacontainer1
LV UUID RnmAbY-2fD6-serM-0X6g-hQVf-Vo1F-FLZhDR
LV Write Access read/write
LV Status available
# open 0
LV Size 2.66 TB
Current LE 87150
Segments 5
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Physical volumes ---
PV Name /dev/md3
PV UUID gsyju6-kCtO-0ut2-rQxb-Jj56-jQJf-WtPnKn
PV Status allocatable
Total PE / Free PE 35770 / 0
PV Name /dev/md1
PV UUID P0nWTm-7clc-Fr8n-p2Ph-UmAE-VrqD-fEqTZ0
PV Status allocatable
Total PE / Free PE 29808 / 0
PV Name /dev/md125
PV UUID HjSvH5-7zK1-udaX-CoD3-qWak-PYAv-XNtaPi
PV Status allocatable
Total PE / Free PE 21572 / 0
So I assumed that the PV on /dev/md3 is working. But back in the
installed OS EVMS tells me this:
LVM2: The PV with index 0 was not found when discovering container
lvm2/datacontainer1. An "error" object will be created in it's
place. Any regions in this container that map to this PV will return
I/O errors if they attempt to read or write to this PV. Regions that
don't map to this PV will work normally.
and thus I cannot mount the volume either. So, is /dev/md3 probably
broken even though lvdisplay list it? I do have dd-copies of the
RAID5 elements and maybe I have assembled the RAID array in the
wrong order..?
Any help is appreciated, thanks.
Nils
|