From: Antonio R. (arv@VODAFONE.ES)
Date: Mon Mar 15 2004 - 08:42:28 EST
I did so, but I didnīt attach to my reply..
# synclvodm -v rootvg
synclvodm: Physical volume data updated.
synclvodm: Logical volume hd6 updated.
synclvodm: Logical volume hd8 updated.
synclvodm: Logical volume hd4 updated.
synclvodm: Logical volume hd2 updated.
synclvodm: Logical volume hd9var updated.
synclvodm: Logical volume hd3 updated.
synclvodm: Logical volume hd1 updated.
synclvodm: Logical volume hd7b updated.
synclvodm: Logical volume hd7 updated.
synclvodm: Logical volume lv00 updated.
#
> So try it without specifying the LV.
>
> --
> Simon Green
> Altria ITSC Europe Ltd
>
> AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
>
> New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
>
> N.B. Unsolicited email from vendors will not be appreciated.
> Please post all follow-ups to the list.
>
> > -----Original Message-----
> > From: Antonio R. [mailto:arv@VODAFONE.ES]
> > Sent: 15 March 2004 11:56
> > To: aix-l@Princeton.EDU
> > Subject: Re: Boot confoguration problem
> >
> >
> > Problem continue ....
> >
> > # synclvodm -v rootvg hd5
> > synclvodm: Physical volume data updated.
> > 0516-532 synclvodm: logical volume hd5 not found in volume
> > group rootvg.
> > #
> <SNIP>
> >
> >
> >
> > > Try "synclvodm rootvg hd5", or "synclvodm rootvg".
> > >
> > > If the boot information exists in the right physical
> > location, on a disk
> > > that is in the bootlist then it will get used before LVM
> > gets involved
> > > and notices that your rootvg is damaged. Once it's booted,
> > it doesn't
> > > need it again.
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:42 EDT