'bosboot' hangs

######################################################################
PROBLEM: 'bosboot' hangs

CAUSE: The major/minor number of the hdiskX(rootvg) in the odm is different from the /dev directory.

SOLUTION: Rectifying the odm entry using 'odmdelete' 'odmadd' commands. Explanation given below.
Please note that odm commands have to be handled very carefully; it is at the SAs own risk.
########

Here's a strange problem.

bosboot hangs. If you can do a "ps -ef | grep bootinfo", you'll see "/usr/sbin/bootinfo -g /dev/hd5". Or, if you run "ksh -x /usr/sbin/bosboot -ad /dev/hdisk0", you'll see it hang at "valid_dev /dev/hdisk0".

Here's the solution (assuming hdisk0):
cd dev
ls -l hdisk0 -> 26, 1

odmget -q value3=hdisk0 CuDvDr  -> 24, 1

looks like odm thinks that hdisk0 is a different major/minor number then /dev thinks it is      [root cause for the bosboot hang]
see if any other devices are in ODM at 26,1

odmget -q 'value1=26 value2=1' CuDvDr

if there is, and it is something that you can live without, get rid of it from the odm

odmdelete -q 'value1=26 value2=1' -o CuDvDr

Now, let's fix hdisk0.

odmget -q value3=hdisk0 CuDvDr >hdisk0.out

vi the file and change the major/minor number to reflect /dev

odmdelete -q value3=hdisk0 -o CuDvDr ->to delete old entry

odmadd hdisk0.out

synclvodm -Pv rootvg -> OK

odmget -q value3=hdisk0 CuDvDr  ->looks good

bosboot -ad /dev/hdisk0 -> OK this time

bootlist -m normal hdisk0 ->OK

odmget info ex(on one machine):
# odmget -q value3=hdisk0 CuDvDr|more

CuDvDr:
        resource = "devno"
        value1 = "22"
        value2 = "0"
        value3 = "hdisk0"
#