wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== AIX error with mksysb ======

===== AIX error with mkszfile =====

Error mksysb
<cli prompt='>'>
[root@aixb211n] /root/scripts> ./mksysb.sh  failed

[root@aixb211n] /var/log/syslog> /usr/bin/mkszfile
0518-507 odmget: Could not retrieve object for CuDv, ODM error number 5904
0518-507 odmget: Could not retrieve object for CuDv, ODM error number 5904
0518-507 odmget: Could not retrieve object for PdDv, ODM error number 5904

0301-150 bosboot: Invalid or no boot device specified!
usage:  bosboot {-a | -v} [-d device] [-p proto] [-k kernel] [-l lvdev]
                   [-b file] [-M primary|standby|both] [-D|-I] [-LTqr]
</cli>

Solve it using the following commands, where hdisk3 is the boot disk
<cli prompt='#'>
# rmlv hd5
# mklv -y hd5 -t boot -a e rootvg 1 hdisk3 >>> hdisk3 is the bootable disk
# cd /dev
# rm ipldevice
# rm ipl_blv
# ln /dev/rhdisk3 /dev/ipldevice
# ln /dev/rhd5 /dev/ipl_blv
# bosboot -ad /dev/ipldevice
# bosboot -ad /dev/hdisk3
# bootlist -m normal hdisk3
# bootlist -m normal -o
</cli>
===== AIX error with savebase or bosboot =====

Check the disks

Confirm whether the bootable disks that AIX knows about are the disks listed and are contained in your current bootlist.
<cli prompt='#'>
# ipl_varyon -i
PVNAME          BOOT DEVICE     PVID                                   VOLUME GROUP ID
hdisk0          YES             00cd94a60f01c7450000000000000000        00cd94a600004c00
hdisk1          NO              00cd94a6e0bd72af0000000000000000        00cd94a600004c00
</cli>

If you find that your disk is not a bootable device in the output from the ipl_varyon command, ask yourself whether you issued a : chpv –c hdisk0 command by mistake? If you did clear the boot records of the hdisk, it will not be displayed as bootable. If this is the case, rerun a bosboot command on that disk with the following command:
<cli prompt='#'>
# bosboot –ad /dev/hdisk0
</cli>

Check that your boot logical volume which is typically hd5 resides on the bootable disk.
<cli prompt='#'>
# lslv -m hd5
hd5:N/A
LP    PP1  PV1               PP2  PV2               PP3  PV3
0001  0181 hdisk0
</cli>

If it is not, then migrate it across to the bootable disk. If hd5 is damaged and you cannot migrate it, then simply remove and re-create it afresh.
<cli prompt='#'>
# rmlv hd5
# mklv -y hd5 -t boot -a e rootvg 1 hdisk0
</cli>

Very rarely when running a bosboot command, AIX might complain about hd5 not being contiguous across the partitions it has been allocated. I have experienced this only one time. If this is the case, you have no choice but to remove hd5 and re-create it, as noted above. Then run the bosboot to the bootable disk and ipldevice, as described further on.

If AIX states that it cannot run a bosboot command because hd5 existed on a previous hdisk or it cannot find ipldevice, then the following should fix it: Confirm whether the bootable disk has the same major and minor number as the ipldevice and the ipldevice is a hard link to the bootable disk.
<cli prompt='#'>
# ls -l *hdisk0*
brw-------    1 root     system       16,  2 Jan 15 11:23 hdisk0
crw-------    2 root     system       16,  2 Oct 31 14:58 rhdisk0
# ls -l ipldevice
crw-------    2 root     system       16,  2 Oct 31 14:58 ipldevice
</cli>

In the above output, the major and minor numbers 16, 2 on hdisk0 match with that of the ipldevice, and therefore, no problems here. Issue bosboot on both: the ipldevice and the bootable disk.
<cli prompt='#'>
# bosboot –a /dev/ipldevice
# bosboot –a /dev/hdisk0
</cli>

The host can then be rebooted.

If the major and minor numbers are different on the bootable disk to ipldevice, then fix it by removing the ipldevice and relinking.
<cli prompt='#'>
# rm /dev/ipldevice
# ln /dev/rhdisk0 /dev/ipldevice
</cli>

Now that ipldevice has been relinked to the bootable disk, run bosboot, on both the ipldevice and the boot disk.
<cli prompt='#'>
# bosboot -ad /dev/ipldevice
# bosboot -ad /dev/hdisk0
</cli>

If your ipldeivce is not present at all, re-create the link as describe above.

In my experience, all conditions have been met. If you can run a bosboot command on the ipldevice and the hdisk and the major and minor numbers match with the ipldevice, the host can be rebooted. When the host comes up back, you will find that the bosboot –a command works fine.
savebase is not saving me, it is failing

The savebase command stores information in the Object Data Manager (ODM) as such and is closely linked with the bosboot command. Typically, savebase errors occur after a hardware migration or a alt_disk migration. A common error is when lspv reports that the bootable disk is not part of rootvg, but you can see it is when issuing a lsvg –p rootvg command. The savebase errors can be confusing sometime because the errors just pop up and can mask another issue. However, for this demonstration, let’s assume it is a straight-forward savebase problem. First, check whether the error is not due to space issues and run a verbose savebase command to confirm this.
<cli prompt='#'>
# savebase –v
</cli>

Next , let’s assume it is a mirrored volume group and confirm that the volume group is indeed synchronized correctly using the following command.
<cli prompt='#'>
syncvg –v rootvg
</cli>

Then force a rebuild of the logical control blocks so that they are in sync with the volume group descriptors area on the disks.
<cli prompt='#'>
synclvodm –Pv rootvg
</cli>

That should be sufficient and the savebase command should now work. Finally, run the savebase –v command, and all should be good. Then, to complete the process, run bosboot on both: the ipldevice and the bootable disk, as noted earlier.
wiki

User Tools

Site Tools

Page Tools
