Re: Locked rootvg

From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Mon May 24 2004 - 11:06:34 EDT

Certainly looks like some sort of ODM corruption.

You might try redefinevg.
Either
redefinevg -d hdisk0
or
redefinevg -i 000f8baf3322d3af 

--
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: Ignacio Vidal [mailto:ividal@BIYCSA.COM.AR]
> Sent: 24 May 2004 15:06
> To: aix-l@Princeton.EDU
> Subject: Re: Locked rootvg
>
>
> Hello:
> Regarding this topic, I can add a bit more info about.
> Here is what it happens when I execute lsvg and lspv (rootvg
> is on hdisk0 and hdisk1)
>
> # lsvg -o
> tsmdbc
> tsmdbm
> (.. more vg's ..)
> vgorastage
> 0516-304 : Unable to find device id 000f8baf3322d3af in the Device
>         Configuration Database.
> vgid=000f8baf3322d3af
>
> >>> This (the last one) should be "rootvg"
>
> #
> # lspv hdisk0
> 0516-310 lspv: Unable to find attribute lock in the Device
>         Configuration Database. Execute synclvodm to attempt to
>         correct the database.
> # lspv hdisk1
> 0516-310 lspv: Unable to find attribute lock in the Device
>         Configuration Database. Execute synclvodm to attempt to
>         correct the database.
>
>
> # synclvodm rootvg
> 0516-010 : Volume group must be varied on; use varyonvg command.
> 0516-544 synclvodm: Unable to access volume group rootvg.
> #
>
>
> Is this ODM corruption?

This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:56 EDT