Problem with bosboot

This is my problem: I couldn't create boot image for hdisk7

test02:/]lspv
hdisk2          00c8ac36cfdf99b4                    old_rootvg      
hdisk5          00c8abd6d05f83ca                    newvg           active
hdisk6          00c8abd6d4ad141f                    rootvg          active
hdisk7          00c8abd6d4ad14b6                    altinst_rootvg  active  
test02:/]bosboot -ad hdisk7     

0301-168 bosboot: The current boot logical volume, /dev/hd5,
        does not exist on /dev/hdisk7.

More infomations

bootlist -m normal -o
hdisk6 blv=hd5 pathid=0
test02:/]bootinfo -b
hdisk6
test02:/]test02:/]ipl_varyon -i
[S 2752822 3407952 11/11/14-14:52:20:940 ipl_varyon.c 1282] ipl_varyon -i 


PVNAME          BOOT DEVICE     PVID                    VOLUME GROUP ID
hdisk2          NO              00c8ac36cfdf99b40000000000000000        00c8abe600004c00
hdisk5          NO              00c8abd6d05f83ca0000000000000000        00c8abd600004c00
hdisk6          YES             00c8abd6d4ad141f0000000000000000        00c8abd600004c00
hdisk7          NO              00c8abd6d4ad14b60000000000000000        00c8abf600004c00
[E 2752822 0:088 ipl_varyon.c 1422] ipl_varyon: exited with rc=0
test02:/]lslv -m hd5
hd5:N/A
LP    PP1  PV1               PP2  PV2               PP3  PV3
0001  0001 hdisk6            

test02:/]lsvg -l altinst_rootvg
altinst_rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
bootlv00            boot       1       1       1    closed/syncd  N/A
pagelv00            paging     64      64      1    closed/syncd  N/A
loglv05             jfs2log    1       1       1    closed/syncd  N/A
fslv12              jfs2       2       2       1    closed/syncd  N/A
fslv13              jfs2       12      12      1    closed/syncd  N/A
fslv14              jfs2       4       4       1    closed/syncd  N/A
fslv15              jfs2       40      40      1    closed/syncd  N/A
fslv16              jfs2       39      39      1    closed/syncd  N/A
fslv17              jfs2       8       8       1    closed/syncd  N/A
lv01                sysdump    12      12      1    closed/syncd  N/A
test02:/]bootlist -m normal /dev/hdisk7 blv=bootlv00
0514-202 bootlist: Invalid device name (/dev/hdisk7)

Somebody knows how to fix this, please :(:(

Hmm,

The error it is throwing clearly says it cannot find /dev/hd5
There is something utterly wrong in the configuration, why are all the LV names changed? why bootlv00? it should be something like alt_hd5 .
If I am not wrong you created the alt_disk from existing rootvg (which resides on hdisk6), which has hd5 as boot logical volume.

Do you mind telling us why did you change the LV names?

Paste the output of
lsvg -l rootvg

Moreover the syntax for bootlist should be
bootlist -m normal hdiskX blv=Y
Where X=0,1,2,3 etc.., and Y=alt_hd5 or hd5, depending on rootvg or alt_rootvg.
There is NO /dev/hdiskX

ibmtech is absolutely correct: this "altinst_rootvg" might be named like it was created by alt_disk_copy, but it has either been tampered with or created by different means (i can create a Vg called "altinst_rootvg", but that will not make it a eligible target for alt_disk-operations at all).

I suggest to remove the VG and recreate it, this time using correct procedures:

# alt_disk_install -X altinst_rootvg
# alt_disk_copy -d hdisk7

then proceed from there.

Just as an aside: even when using the correct command which ibmtech told you and assuming that whatever you have on hdisk7 is bootable and legit to boot AIX at all (i doubt that, but lets assume it for the sake of the argument) you need to use "hdisk7" in the bosboot command, not "/dev/hdisk7", because you need to name the disk, not its device file (which is just a driver construct representing the disk).

I hope this helps.

bakunin

Thanks guys. Maybe there was something wrong with the altinst_rootvg. I removed it and recreated it. Then I booted the hdisk7 from SMS ( no bosboot or bootlist commands anymore ) and it worked.

I would think that as altinst_rootvg it would be varied off and therefore you cannot see logical volume hd5 on it. I did once vary on one of these and the OS naturally objected to the matching names of the LVs and promptly renamed them as seems to have happened here, making it unusable. I had to recreate it.

Robin