"volume can't start" somebody help me - Veritas Volume Manager

This is a discussion on "volume can't start" somebody help me - Veritas Volume Manager ; Well, has something changed ? Like added another path to the same disks ? without telling Volume Manager about it ? The error you're getting is because starting the volume menas that the state needs to change on all the ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: "volume can't start" somebody help me

  1. Re: "volume can't start" somebody help me

    Well, has something changed ? Like added another path to the same disks
    ? without telling Volume Manager about it ?


    The error you're getting is because starting the volume menas that the
    state needs to change on all the disks with configuration copies (see
    User's Guide). What is happening now is that the kernel contains
    possible duplicate disk information, and when it tries to update all the
    disks with config copies, it gets 2 (or more) disks to update (but these
    2 or more disks have the same disk id in the kernel). That is wy you get
    this starnge error.

    Now, the next question would be, how to fix it ?

    Well, the easy way is to reboot (this will clear the kernel)
    The way to do it if you can not reboot, is a bit of a round-about way,
    and there could be a problem if this node is part of a Cluster Volume
    Manager cluster (or RAC).

    OK, so how to do this:

    1. vxddladm exclude array all
    2. vxdctl initdmp
    3. vxdctl enable
    4. vxddlamd include array all
    5. vxdctl initdmp
    6. vxdctl enable


    Now try looking at the volume again and try to start it.
    (your will have to use a "-f" option with starting because this volume
    has only a single plex.)


    If this still did not do the trick, the next step is to kill and reset
    the config copy in memory

    vxconfgf -k -r reset -m enable




    As mentioned before, if all else fails, reboot will do it for you (yep,
    we live in a Windows world)


    vic wrote:
    > Dear All,
    >
    > I started the volume, it gave some error :
    > " VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration
    > "
    >
    > Would somebody tell me how to solve the ploblem ?
    >
    > Thanks.
    >
    > following Message is vxprint -ht
    >
    > #vxprint -g ljdbdg -ht
    > dg ljdbdg default default 16000 1117528139.17.LJSPDS01
    >
    > dm ljdbdg01 c4t0d1s2 auto 2048 409564928 -
    >
    > v ljdbvol - DISABLED EMPTY 102400000 SELECT -
    > fsgen
    > pl ljdbvol-01 ljdbvol DISABLED EMPTY 102400000 CONCAT -
    > RW
    > sd ljdbdg01-01 ljdbvol-01 ljdbdg01 0 102400000 0 c4t0d1
    > ENA
    > dc ljdbvol_dco ljdbvol ljdbvol_dcl
    > v ljdbvol_dcl - ENABLED ACTIVE 14960 SELECT -
    > gen
    > pl ljdbvol_dcl-01 ljdbvol_dcl ENABLED ACTIVE 14960 CONCAT -
    > RW
    > sd ljdbdg01-02 ljdbvol_dcl-01 ljdbdg01 209715200 14960 0 c4t0d1
    > ENA
    >
    > # vxvol -g ljdbdg start ljdbvol
    > VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
    > #


  2. "volume can't start" somebody help me


    Dear All,

    I started the volume, it gave some error :
    " VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration
    "

    Would somebody tell me how to solve the ploblem ?

    Thanks.

    following Message is vxprint -ht

    #vxprint -g ljdbdg -ht
    dg ljdbdg default default 16000 1117528139.17.LJSPDS01

    dm ljdbdg01 c4t0d1s2 auto 2048 409564928 -

    v ljdbvol - DISABLED EMPTY 102400000 SELECT -
    fsgen
    pl ljdbvol-01 ljdbvol DISABLED EMPTY 102400000 CONCAT -
    RW
    sd ljdbdg01-01 ljdbvol-01 ljdbdg01 0 102400000 0 c4t0d1
    ENA
    dc ljdbvol_dco ljdbvol ljdbvol_dcl
    v ljdbvol_dcl - ENABLED ACTIVE 14960 SELECT -
    gen
    pl ljdbvol_dcl-01 ljdbvol_dcl ENABLED ACTIVE 14960 CONCAT -
    RW
    sd ljdbdg01-02 ljdbvol_dcl-01 ljdbdg01 209715200 14960 0 c4t0d1
    ENA

    # vxvol -g ljdbdg start ljdbvol
    VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
    #

+ Reply to Thread