Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!levell.austin.ibm.com!julie From: julie@levell.austin.ibm.com (Julie A. Levell) Newsgroups: comp.unix.aix Subject: Re: Volume groups problem... Message-ID: <5736@awdprime.UUCP> Date: 5 Mar 91 02:31:07 GMT References: <1991Feb28.143052.15422@ux1.cts.eiu.edu> <491@bria> Sender: news@awdprime.UUCP Organization: IBM AWD, Austin Lines: 35 In article <491@bria> uunet!bria!mike writes: >In an article, ux1.cts.eiu.edu!dbeedle (Dave Beedle) writes: >>Anyway, I've still got one problem with the volume group. When I boot >>I get measseges saying : lvaryon: the volume group cannot be varied on >>because there are no good copies of the descripter area. This message >>results when I do a varyonvg rootvg. Other messages I get while in smit: >>getlvodm: Unable to find device if in the Device Configuration >>Database. > >Sounds like a reinstallation opportunity to me. Have you been walking >disks between machines, perchance? Don't say "The R-word" for a database problem!! > >Failing that ... > >Switch it to service and run diags (the ``advanced'' set) on the system. >It could be that you have a problem with the NVRAM or the adapter. If it >fails diags, (I imagine that it will) give IBM hardware a jingle. > And diags won't help you out here either, sorry. It's just a matter of clearing out the database and re-syncing it. Switching disks is a different problem, but the database will stay with the disk, so I'm not sure what the problem was. If the disk isn't rootvg, then use importvg. I don't think it's a security thing. -- *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Julie A. Levell IBM Advanced Workstation Division Austin, Texas Internet: julie@aixwiz.austin.ibm.com IBM VMNET: JULIEL at AUSVMQ DeskNet: 4C-29/994 SpeakNet: 823-5178 (Tie 793-5178)