Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

mksysb say: unable to identify boot disk

Status
Not open for further replies.

mikri

Technical User
Dec 16, 2003
39
0
0
DE
Hi,

one of my AIX Lpar say "unable to identify boot disk" if i make a mksysb.

Code:
root::p5-1db3::/>>lspv
hdisk1          005250aacbd65b66                    PAGE_VG1        active
hdisk8          005250aa03e9fb05                    SAPDB3PBS_VG1   active
hdisk9          005250aacb91adbd                    SAPDB3_VG1      active
hdisk10         005250aa03e8ad73                    SAPDB3LOG_VG1   active
hdisk11         005250aacb91ae69                    SAPDB3_VG1      active
hdisk12         005250aacb91af15                    SAPDB3_VG1      active
hdisk14         00ce6ffd28bace5c                    rootvg          active

root::p5-1db3::/>>bootlist -m normal hdisk14
root::p5-1db3::/>>bosboot -ad hdisk14
unable to identify boot disk
unable to identify boot disk
unable to identify boot disk
unable to identify boot disk

bosboot: Boot image is 24584 512 byte blocks.

root::p5-1db3::/>>lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
hd5                 boot       4     4     1    closed/syncd  N/A
hd6                 paging     318   318   1    open/syncd    N/A
hd8                 jfslog     1     1     1    open/syncd    N/A
hd4                 jfs        59    59    1    open/syncd    /
hd2                 jfs        434   434   1    open/syncd    /usr
hd9var              jfs        90    90    1    open/syncd    /var
hd3                 jfs        74    74    1    open/syncd    /tmp
hd1                 jfs        634   634   1    open/syncd    /home
hd10opt             jfs        69    69    1    open/syncd    /opt


root::p5-1db3::/>>lspv -l hdisk14
hdisk14:
LV NAME               LPs   PPs   DISTRIBUTION          MOUNT POINT
hd8                   1     1     00..01..00..00..00    N/A
hd6                   318   318   00..318..00..00..00   N/A
hd5                   4     4     04..00..00..00..00    N/A
hd3                   74    74    74..00..00..00..00    /tmp
hd9var                90    90    84..00..06..00..00    /var
hd2                   434   434   00..31..403..00..00   /usr
hd4                   59    59    00..59..00..00..00    /
hd10opt               69    69    00..00..00..69..00    /opt
hd1                   634   634   248..00..00..340..46  /home

root::p5-1db3::/>>oslevel -r
5300-03
root::p5-1db3::/>>

Can any one help?

THX
Mikri
 
Did you perhaps migrate rootvg to another disk?

What I do at that point is on next boot, go through SMS menu and choose the boot disk manually, then afterwards:

bosboot -a -d /dev/hdiskXX -l /dev/hd5

HTH,

p5wizard
 
Yes, the rootvg was migrate.
But i have migrate a lot of Systems and this is the first who makes this problem.

I will try your Tip after the next reboot.


THX
Mikri
 
You could also try

cd /dev
ls -l rhdisk*
ls -l ipldevice

You'll see that ipldevice has identical major and minor device numbers as your old boot disk (in fact it is just a second name for that rhdisk as indicated by the link count of 2), so:

rm ipldevice
ln rhdisk14 ipldevice

Then try bosboot again. If it still doesn't work, try my first suggestion via SMS menu on boot.


HTH,

p5wizard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top