On 03/08/2013 08:07 AM, SilverTip257 wrote: > On Thu, Mar 7, 2013 at 10:54 PM, Harold Pritchett <harold at uga.edu> wrote: > >> On 3/7/2013 10:10 PM, Stephen Harris wrote: >>> On Thu, Mar 07, 2013 at 09:54:59PM -0500, Harold Pritchett wrote: >>>> What other information do I need which may be available? >>> What does 'vgscan' say? 'vgchange -a y' ? >>> >> [root at mickey www]# vgscan >> Reading all physical volumes. This may take a while... >> Found volume group "VolGroup00" using metadata type lvm2 >> > Do both Volume Groups on those two sets of disks have the same name? > VolGroup00 This is all to common an issue. I make a point that all LVMs are uniquely named. > > That's odd /dev/md125 doesn't have a VG name associated with it... > * You might consider booting to a rescue environment with the 2TB disks in > a separate system. Find out what the VG name is and maybe even just > recover the data you need from the rescue environment ... rsync is your > friend. > > >> [root at mickey www]# vgchange -a y >> 2 logical volume(s) in volume group "VolGroup00" now active >> [root at mickey www]#