CentOS - Apr 2015 - can't mount an LVM volume inCentos 5.10

I have a degraded raid array (originally raid-10, now only two drives)  
that contains an LVM volume. I can see in the appended text that the  
Xen domains are there but I don't see how to mount them. No doubt this  
is just ignorance on my part but I wonder if anyone would care to  
direct me? I want to be able to retrieve dom-0 and one of the dom-Us  
to do data recovery, the others are of no interest.

Suggestions? Will rtfm if directed.

Dave

excerpt from failed mount attempts

--------------- starting here ------------

root at Microknoppix:/home/knoppix# vgchange -ay bulkley
   Volume group "bulkley" not found
root at Microknoppix:/home/knoppix# vgchange -ay /dev/VolGroup00/bulkley
   Invalid volume group name: VolGroup00/bulkley
   Run `vgchange --help' for more information.
root at Microknoppix:/home/knoppix# vgimport -f VolGroup00
   Volume group "VolGroup00" is not exported
root at Microknoppix:/home/knoppix# vgchange -ay VolGroup00
   8 logical volume(s) in volume group "VolGroup00" now active
root at Microknoppix:/home/knoppix# lvscan
   ACTIVE            '/dev/VolGroup00/Dom0' [40.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/babine' [100.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/centos-template' [100.00 GiB]
inherit
   ACTIVE            '/dev/VolGroup00/bulkley-old' [100.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/ubuntu' [10.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/morice' [200.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/oldserver' [80.00 GiB] inherit
   ACTIVE            '/dev/VolGroup00/bulkley' [100.00 GiB] inherit
root at Microknoppix:/home/knoppix# mount /dev/mapper/VolGroup00 aa
mount: special device /dev/mapper/VolGroup00 does not exist
root at Microknoppix:/home/knoppix# mount /dev/mapper/bulkley aa
mount: special device /dev/mapper/bulkley does not exist
root at Microknoppix:/home/knoppix# mount /dev/mapper/dev/VolGroup00 aa
mount: special device /dev/mapper/dev/VolGroup00 does not exist
root at Microknoppix:/home/knoppix# mount /dev/mapper/dev/VolGroup00/bulkley aa
mount: special device /dev/mapper/dev/VolGroup00/bulkley does not exist
root at Microknoppix:/home/knoppix# mount /dev/mapper/dev/VolGroup00/LogVol00 aa
mount: special device /dev/mapper/dev/VolGroup00/LogVol00 does not exist
root at Microknoppix:/home/knoppix# mount  
/dev/mapper/dev/VolGroup00/LogVol00/bulkley aa
mount: special device /dev/mapper/dev/VolGroup00/LogVol00/bulkley does  
not exist
root at Microknoppix:/home/knoppix# mount /dev/VolGroup00/LogVol00/bulkley aa
mount: special device /dev/VolGroup00/LogVol00/bulkley does not exist

-- 
"As long as politics is the shadow cast on society by big business,
the attenuation of the shadow will not change the substance."

-- John Dewey

Hi,

On Thu, Apr 2, 2015 at 1:40 AM, Dave Stevens <geek at uniserve.com> wrote:
> I have a degraded raid array (originally raid-10, now only two drives)
> that contains an LVM volume. I can see in the appended text that the Xen
> domains are there but I don't see how to mount them. No doubt this is
just
> ignorance on my part but I wonder if anyone would care to direct me? I want
> to be able to retrieve dom-0 and one of the dom-Us to do data recovery, the
> others are of no interest.
>
> Suggestions? Will rtfm if directed.
>
> Dave
>
> excerpt from failed mount attempts
>
> --------------- starting here ------------
>
> root at Microknoppix:/home/knoppix# vgchange -ay bulkley
>   Volume group "bulkley" not found
> root at Microknoppix:/home/knoppix# vgchange -ay /dev/VolGroup00/bulkley
>   Invalid volume group name: VolGroup00/bulkley
>   Run `vgchange --help' for more information.
> root at Microknoppix:/home/knoppix# vgimport -f VolGroup00
>   Volume group "VolGroup00" is not exported
> root at Microknoppix:/home/knoppix# vgchange -ay VolGroup00
>   8 logical volume(s) in volume group "VolGroup00" now active
> root at Microknoppix:/home/knoppix# lvscan
>   ACTIVE            '/dev/VolGroup00/Dom0' [40.00 GiB] inherit
>   ACTIVE            '/dev/VolGroup00/babine' [100.00 GiB] inherit
>   ACTIVE            '/dev/VolGroup00/centos-template' [100.00 GiB]
inherit
>   ACTIVE            '/dev/VolGroup00/bulkley-old' [100.00 GiB]
inherit
>   ACTIVE            '/dev/VolGroup00/ubuntu' [10.00 GiB] inherit
>   ACTIVE            '/dev/VolGroup00/morice' [200.00 GiB] inherit
>   ACTIVE            '/dev/VolGroup00/oldserver' [80.00 GiB] inherit
>   ACTIVE            '/dev/VolGroup00/bulkley' [100.00 GiB] inherit
> root at Microknoppix:/home/knoppix# mount /dev/mapper/VolGroup00 aa
> mount: special device /dev/mapper/VolGroup00 does not exist
> root at Microknoppix:/home/knoppix# mount /dev/mapper/bulkley aa
> mount: special device /dev/mapper/bulkley does not exist
> root at Microknoppix:/home/knoppix# mount /dev/mapper/dev/VolGroup00 aa
> mount: special device /dev/mapper/dev/VolGroup00 does not exist
> root at Microknoppix:/home/knoppix# mount
/dev/mapper/dev/VolGroup00/bulkley
> aa
> mount: special device /dev/mapper/dev/VolGroup00/bulkley does not exist
> root at Microknoppix:/home/knoppix# mount
/dev/mapper/dev/VolGroup00/LogVol00
> aa
> mount: special device /dev/mapper/dev/VolGroup00/LogVol00 does not exist
> root at Microknoppix:/home/knoppix# mount
/dev/mapper/dev/VolGroup00/LogVol00/bulkley
> aa
> mount: special device /dev/mapper/dev/VolGroup00/LogVol00/bulkley does
> not exist
> root at Microknoppix:/home/knoppix# mount /dev/VolGroup00/LogVol00/bulkley
aa
>
Please try to mount */dev/VolGroup00/oldserver *not
*/dev/mapper/dev/VolGroup00/LogVol00/bulkley
*because in your *lvscan*
result was showing /dev/VolGroup00/oldserver .

Then share the result.

 --Regards
Ashishkumar S. Yadav