[comp.unix.aix] Volume groups problem...

dbeedle@ux1.cts.eiu.edu (Dave Beedle) (02/28/91)

     Hi all!  We recently had some trouble with our rs6000/530 and had to
reinstall the thing from scratch (the original floppies...all 78 of 'em).
I also restored some stuff from other backup tapes including the /usr
subdirectory, the /etc subdirectory and the /u subdirectory; to catch up
with where we were before our problems.  
     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 if 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 <numbers> in the Device Configuration
Database.     Have you, by chance, seen something like this?  The last
thing "Software Support" had to say to me was to pull the battry off the
NVram for at least 45 min.  and let it rebuld itself.  Any thoughts?
Just what is going to happen if I unplug that battery?  Is there any other
way to fix this?  This problem doesn't seem to interfere with the
functioning of the machine but I don't get any info on the volume group
(lsvg rootvg - tells me to varyon the VG and shows ????? everywhere else.)
     I talked to "Software Support about my problem...It seems
that software support is really "Software Defects Support".  Once they
decided my problems were not "defects" they told me to call my local
SE and/or CE.  Unfortunatly my SE is really a marketing rep and is little
help when it comes to problems.     Thanks for any suggestions!

TTFN

--
  Dave Beedle                                     Office of Academic Computing
                                                     Illinois State University
  Internet:  dbeedle@rs6000.cmp.ilstu.edu                     136A Julian Hall  
    Bitnet:  dbeedle@ilstu                                  Normal, Il   61761

mike (03/01/91)

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 <numbers> in the Device Configuration
>Database. 

Sounds like a reinstallation opportunity to me.  Have you been walking
disks between machines, perchance?

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.

-- 
Michael Stefanik, MGI Inc., Los Angeles| Opinions stated are not even my own.
Title of the week: Systems Engineer    | UUCP: ...!uunet!bria!mike
-------------------------------------------------------------------------------
Remember folks: If you can't flame MS-DOS, then what _can_ you flame?

julie@levell.austin.ibm.com (Julie A. Levell) (03/05/91)

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 <numbers> 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)