Re: Accidentially Removed a Volume Group

From: Bill Verzal (BVerzal_at_KOMATSUNA.COM)
Date: 04/28/04

  • Next message: Tim Muller: "Re: gcc Installation" 
    Date:         Wed, 28 Apr 2004 10:46:20 -0500
To: aix-l@Princeton.EDU

    Actually, we see that alot on our systems because we buy most of our stuff
    used with OEM drives in them :(

    I have that on all of my S80 internal drives.

    BV
    --------------------------------------------------------

    "If everything is coming your way, then you are in the wrong lane"

    Bill Verzal
    AIX Administrator, Komatsu America
    (847) 970-3726 - direct
    (847) 970-4184 - fax

                 "Gipson, Mat"
                 <Mat.Gipson@AMERI
                 CREDIT.COM> To
                 Sent by: IBM AIX aix-l@Princeton.EDU
                 Discussion List cc
                 <aix-l@Princeton.
                 EDU> Subject
                                           Re: Accidentially Removed a Volume
                                           Group
                 04/28/2004 10:35
                 AM

                 Please respond to
                      IBM AIX
                  Discussion List
                 <aix-l@Princeton.
                       EDU>

    After conferring with a colleague it is very rare that you would every see
    ".. Other SCSI Disk Drive" output from an lsdev output. You may want to
    check the health of the SCSI controller for these disks. Have these drives
    always showed this output? Do you have all your device drivers installed?
    All these might be shots in the dark if these lv's and disks worked with no
    problem before your remove....but that then prompts me to ask why did you
    want to delete the VG in the first place.

    HTH,
    Mathew Gipson

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
    Lieberg, Patrick
    Sent: Wednesday, April 28, 2004 10:10 AM
    To: aix-l@Princeton.EDU
    Subject: Re: Accidentially Removed a Volume Group

    Did you try this command:

    recreatevg -y vgname hdiskxxx hdiskxxx hdiskxxx

    as suggested by John? The importvg will not work if the disks are missing
    the VG descriptor area info.

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
    Bengt Mutén
    Sent: Tuesday, April 27, 2004 4:42 PM
    To: aix-l@Princeton.EDU
    Subject: Re: Accidentially Removed a Volume Group

    I appreciate Bob, John, and Bills' suggestions. However, I am still stuck

    I managed to remove the volume group information on these three physical
    drives by running this script from smit:

       xlist () { VGID=`getlvodm -v $1`; if test $? -ne 0
       then
         exit 1
       fi
       Q1=`getlvodm -w $VGID | cut -f2 -d' '`; echo $Q1; }; xlist ''

    I can then not import volume groups from:

    hdisk0 Available 04-B0-00-0,0 Other SCSI Disk Drive
    hdisk1 Available 04-B0-00-1,0 Other SCSI Disk Drive
    hdisk2 Available 04-B0-00-2,0 Other SCSI Disk Drive

    For each one I get:

    0516-066 lqueryvg: Physical volume is not a volume group member.
            Check the physical volume name specified.
    0516-066 lqueryvg: Physical volume is not a volume group member.
            Check the physical volume name specified.
    0516-562 redefinevg: Unable to access physical volume hdisk0

    I am looking for these logical volumes:

    /dev/lv01 -- /opt jfs --
    rw yes no
    /dev/lv02 -- /home/dns jfs --
    rw yes no

    Since I have been having trouble with my backups, I am tempted to try a
    data recovery company. However, if anybody has a way of undoing the
    damage, or suggestion as to where to turn, it would be great.

    Bengt

    _____________________________________________________________________
    Message scanned for viruses

    _____________________________________________________________________
    This message has been checked for all known viruses

  • Next message: Tim Muller: "Re: gcc Installation"

    Relevant Pages

    • Re: Must be important.
      ... malware or viruses these days. ... strength" wiping technique on odd files won't remove malware. ... erase today's modern hard drives, ... technical analysis of drive encoding techniques. ...
      (talk.origins)
    • Re: Must be important.
      ... malware or viruses these days. ... strength" wiping technique on odd files won't remove malware. ... erase today's modern hard drives, ... technical analysis of drive encoding techniques. ...
      (talk.origins)
    • Re: new computer using old data-filled drives runs XP-PRO and shuts do
      ... By your own admission your computer is infested with viruses. ... The C drive holds the Win XP-Pro OS. ... > slowly brought over data files from the old (now E and F drives) HDs and ... > The computer is almost useless and is corrupting many important files. ...
      (microsoft.public.windowsxp.general)
    • RE: Planning a Upgrade (5.2.1 --> 5.3)
      ... Or is the encryption of passwords one way?? ... Are you just adding in extra drives, ... that you have on your existing system as it is, after the cvsup. ... This email has been scanned for all viruses by the MessageLabs SkyScan ...
      (freebsd-questions)
    • Re: Must be important.
      ... malware or viruses these days. ... strength" wiping technique on odd files won't remove malware. ... erase today's modern hard drives, ... technical analysis of drive encoding techniques. ...
      (talk.origins)