+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11

bosboot problem after unmirror rootvg

  1. bosboot problem after unmirror rootvg

    Hello,

    After unmirror rootvg :
    # bosboot -a
    0301-168 bosboot: The current boot logical volume, /dev/hd5,
    does not exist on /dev/hdisk0.


    The story :
    At start I had rootvg with one disk (hdisk0)
    1. I had to migrate rootvg to bigger disk (hdisk0 -> hdisk2) .
    2. I added hdisk2 to rootvg, then: mirrorvg rootvg hdisk0 hdisk2 ->
    ok.
    3. Unmirrorvg rootvg hdisk0
    4. then i wanted to do :
    bosboot -a

    but the error appeard:
    # bosboot -a
    0301-168 bosboot: The current boot logical volume, /dev/hd5,
    does not exist on /dev/hdisk0.

    There is hd5 on hdisk2 , hdisk0 was removed from rootvg.
    # lsvg -M rootvg | grep hd5
    hdisk2:1 hd5:1
    hdisk2:2 hd5:2
    hdisk2:3 hd5:3

    # lsvg -l rootvg
    hd5 boot 3 3 1 closed/syncd N/A
    hd6 paging 64 64 1 open/syncd N/A
    ....

    I have tried these (with success) :
    # bosboot -d /dev/hdisk2 -a
    bosboot: Boot image is 32984 512 byte blocks.

    # bootlist -m both hdisk2
    # chpv -c hdisk0
    # synclvodm rootvg hd5
    # savebase -v

    # bosboot -ad /dev/ipldevice
    0301-168 bosboot: The current boot logical volume, /dev/hd5,
    does not exist on /dev/hdisk0.

    I afraid to reboot.. , because bosboot -a ends with error

    Any suggestions ?

    Kmet

  2. Re: bosboot problem after unmirror rootvg

    Kmet wrote:
    > Hello,
    >
    > After unmirror rootvg :
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    >
    > The story :
    > At start I had rootvg with one disk (hdisk0)
    > 1. I had to migrate rootvg to bigger disk (hdisk0 -> hdisk2) .
    > 2. I added hdisk2 to rootvg, then: mirrorvg rootvg hdisk0 hdisk2 ->
    > ok.
    > 3. Unmirrorvg rootvg hdisk0
    > 4. then i wanted to do :
    > bosboot -a
    >
    > but the error appeard:
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    > There is hd5 on hdisk2 , hdisk0 was removed from rootvg.
    > # lsvg -M rootvg | grep hd5
    > hdisk2:1 hd5:1
    > hdisk2:2 hd5:2
    > hdisk2:3 hd5:3
    >
    > # lsvg -l rootvg
    > hd5 boot 3 3 1 closed/syncd N/A
    > hd6 paging 64 64 1 open/syncd N/A
    > ...
    >
    > I have tried these (with success) :
    > # bosboot -d /dev/hdisk2 -a
    > bosboot: Boot image is 32984 512 byte blocks.
    >
    > # bootlist -m both hdisk2
    > # chpv -c hdisk0
    > # synclvodm rootvg hd5
    > # savebase -v
    >
    > # bosboot -ad /dev/ipldevice
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    > I afraid to reboot.. , because bosboot -a ends with error
    >
    > Any suggestions ?
    >
    > Kmet

    what does
    "ipl_varyon -i" show?

    also
    "bootinfo -B hdisk2" and "lppchk -v"

    RP

  3. Re: bosboot problem after unmirror rootvg


    # ipl_varyon -i
    PVNAME BOOT DEVICE PVID VOLUME GROUP
    ID
    hdisk1 NO
    0000e0e1f3ba6d760000000000000000 0000e0e10000d600
    hdisk2 YES
    0000e0e11ce9c23f0000000000000000 0000e0e10000d600

    # bootinfo -B hdisk2
    1
    # lppchk -v

    {empty output}


    Kmet

  4. Re: bosboot problem after unmirror rootvg


    # ipl_varyon -i
    PVNAME BOOT DEVICE PVID VOLUME GROUP
    ID
    hdisk1 NO
    0000e0e1f3ba6d760000000000000000 0000e0e10000d600
    hdisk2 YES
    0000e0e11ce9c23f0000000000000000 0000e0e10000d600

    # bootinfo -B hdisk2
    1
    # lppchk -v

    {empty output}


    Kmet

  5. Re: bosboot problem after unmirror rootvg

    On 15 Feb, 15:47, Kmet wrote:
    > # ipl_varyon -i
    > PVNAME * * * * *BOOT DEVICE * * PVID * * * * * ** * * *VOLUME GROUP
    > ID
    > hdisk1 * * * * *NO
    > 0000e0e1f3ba6d760000000000000000 * * * *0000e0e10000d600
    > hdisk2 * * * * *YES
    > 0000e0e11ce9c23f0000000000000000 * * * *0000e0e10000d600
    >
    > # bootinfo -B hdisk2
    > 1
    > # lppchk -v
    >
    > {empty output}
    >
    > Kmet


    /dev/ipldevice is a hard link to the latest disk booted from I think.
    I wonder if your ipldevice is still pointing to hdisk0 even though its
    not bootable anymore.

    Try

    cd /dev
    ls -l |grep ipldevice
    (on my system - crw------- 2 root system 18, 2 15 Feb
    2005 ipldevice)
    then
    ls -l |grep hdisk0 (and also hdisk2)
    and see if the major,minor numbers relate to the ipldevice.

    I think you can delete ipldevice and relink as a hard link to hdisk2
    if its still pointing at hdisk0.

    There is plenty about this in old postings on comp.unix.aix so you may
    want to search back a bit.

    Scott

  6. Re: bosboot problem after unmirror rootvg

    > I think you can delete ipldevice and relink as a hard link to hdisk2
    > if its still pointing at hdisk0.
    >
    > There is plenty about this in old postings on comp.unix.aix so you may
    > want to search back a bit.
    >
    > Scott


    I think that this is no ipldevice problem...

    In fact ipldevices major/minor number were the same as hdisk0 (should
    be hdisk2)
    # ls -l | egrep -e 'hdisk0|hdisk2|ipldevice'
    brw------- 1 root system 17, 0 Feb 15 14:44 hdisk0
    brw------- 1 root system 17, 3 Feb 15 15:33 hdisk2
    crw------- 1 root system 17, 0 Feb 15 18:44 ipldevice

    so i have removed it :
    # rm ipldevice
    and recreated it :
    #mknod ipldevice c 17 3
    but the error is still the same.
    More, i have tried to do bosboot -a when there was no ipldevice at
    all, and the error was the same :
    0301-168 bosboot: The current boot logical volume, /dev/hd5,
    does not exist on /dev/hdisk0.

    any suggestions ?

    Kmet

  7. Re: bosboot problem after unmirror rootvg

    Kmet wrote:
    > Hello,
    >
    > After unmirror rootvg :
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    >
    > The story :
    > At start I had rootvg with one disk (hdisk0)
    > 1. I had to migrate rootvg to bigger disk (hdisk0 -> hdisk2) .
    > 2. I added hdisk2 to rootvg, then: mirrorvg rootvg hdisk0 hdisk2 ->
    > ok.
    > 3. Unmirrorvg rootvg hdisk0
    > 4. then i wanted to do :
    > bosboot -a
    >
    > but the error appeard:
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    > There is hd5 on hdisk2 , hdisk0 was removed from rootvg.
    > # lsvg -M rootvg | grep hd5
    > hdisk2:1 hd5:1
    > hdisk2:2 hd5:2
    > hdisk2:3 hd5:3
    >
    > # lsvg -l rootvg
    > hd5 boot 3 3 1 closed/syncd N/A
    > hd6 paging 64 64 1 open/syncd N/A
    > ...
    >
    > I have tried these (with success) :
    > # bosboot -d /dev/hdisk2 -a
    > bosboot: Boot image is 32984 512 byte blocks.
    >
    > # bootlist -m both hdisk2
    > # chpv -c hdisk0
    > # synclvodm rootvg hd5
    > # savebase -v
    >
    > # bosboot -ad /dev/ipldevice
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    > I afraid to reboot.. , because bosboot -a ends with error
    >
    > Any suggestions ?
    >
    > Kmet

    lsvg rootvg

    and if hdisk0 is still there then run
    reducevg rootvg hdisk0

    then try again with bosboot and bootlist accordingly...

    RP

  8. Re: bosboot problem after unmirror rootvg

    > lsvg rootvg
    >
    > and if hdisk0 is still there then run
    > reducevg rootvg hdisk0
    >
    > then try again with bosboot and bootlist accordingly...
    >
    > RP


    hdisk0 is not in rootvg. I heve removed it just after unmirror and few
    unsuccessful efforts with bosboot -a
    # lsvg -p rootvg
    PV_NAME PV STATE TOTAL PPs FREE PPs FREE
    DISTRIBUTION
    hdisk2 active 1023 265
    60..00..00..00..205

    # lspv
    hdisk0 0000e0e1deb5d3d3 None
    hdisk1 0000e0e1f3ba6d76 oravg
    active
    hdisk2 0000e0e11ce9c23f rootvg
    active

  9. Re: bosboot problem after unmirror rootvg

    Kmet wrote:
    > Hello,
    >
    > After unmirror rootvg :
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.
    >
    >
    > The story :
    > At start I had rootvg with one disk (hdisk0)
    > 1. I had to migrate rootvg to bigger disk (hdisk0 -> hdisk2) .
    > 2. I added hdisk2 to rootvg, then: mirrorvg rootvg hdisk0 hdisk2 ->
    > ok.
    > 3. Unmirrorvg rootvg hdisk0
    > 4. then i wanted to do :
    > bosboot -a
    >
    > but the error appeard:
    > # bosboot -a
    > 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    > does not exist on /dev/hdisk0.

    "bosboot -a" uses /dev/ipldevice, that's why it fails.

    >
    > I have tried these (with success) :
    > # bosboot -d /dev/hdisk2 -a
    > bosboot: Boot image is 32984 512 byte blocks.
    >
    > # bootlist -m both hdisk2
    > # chpv -c hdisk0

    This is enough.

    On the next reboot ipldevice will point at hdisk2.

  10. Re: bosboot problem after unmirror rootvg

    Jose Pina Coelho wrote:
    > Kmet wrote:
    >> Hello,
    >>
    >> After unmirror rootvg :
    >> # bosboot -a
    >> 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    >> does not exist on /dev/hdisk0.
    >>
    >>
    >> The story :
    >> At start I had rootvg with one disk (hdisk0)
    >> 1. I had to migrate rootvg to bigger disk (hdisk0 -> hdisk2) .
    >> 2. I added hdisk2 to rootvg, then: mirrorvg rootvg hdisk0 hdisk2 ->
    >> ok.
    >> 3. Unmirrorvg rootvg hdisk0
    >> 4. then i wanted to do :
    >> bosboot -a
    >>
    >> but the error appeard:
    >> # bosboot -a
    >> 0301-168 bosboot: The current boot logical volume, /dev/hd5,
    >> does not exist on /dev/hdisk0.

    > "bosboot -a" uses /dev/ipldevice, that's why it fails.
    >
    >>
    >> I have tried these (with success) :
    >> # bosboot -d /dev/hdisk2 -a
    >> bosboot: Boot image is 32984 512 byte blocks.
    >>
    >> # bootlist -m both hdisk2
    >> # chpv -c hdisk0

    > This is enough.
    >
    > On the next reboot ipldevice will point at hdisk2.

    if not then you can still invoke the bootlist cmd in maintenance mode
    good luck

    RP

+ Reply to Thread
Page 1 of 2 1 2 LastLast