just setup a new system today - 9117 570, using HMC for console but not partitioned.

I installed this system twice. the first time it started off as 5300-00, then updated to ML03. before the update, I believe I mirrored the rootvg, and then altered the bootlist, at that point, the display was OK.

after I updated the ML to 03, I tried to update service boot list, that's when I noticed something weird:

display:
CURRENT BOOTLIST DEVICES FOR SERVICE MODE 802592

The following devices are listed in the order they appear
in the service mode bootlist.

hdisk0 blv=hd5 Unavailable Device
hdisk1 blv=hd5 Unavailable Device

try to alter the list:
*** WARNING ***

One or more devices in the current bootlist are
not available as IPL devices. They may not be
used when modifying the bootlist. Either ERASE
the bootlist first, or do not use these devices
in the new list.

next screen:
[FONT=Courier New]ALTER SERVICE MODE BOOTLIST DEVICES 802593

Specify the access order of the boot devices.
Indicate by placing the appropriate integer in the
bracketed [] field. (1 is first, 2 is second, etc.)

hdisk0 blv=hd5 Unavailable Device [ 1] #
hdisk1 blv=hd5 Unavailable Device [ 2] #
cd0 IDE DVD-RAM Drive [ ] #
hdisk0 16 Bit LVD SCSI Disk Drive [ ] #
hdisk1 16 Bit LVD SCSI Disk Drive [ ] #
hdisk2 16 Bit LVD SCSI Disk Drive [ ] #
hdisk3 16 Bit LVD SCSI Disk Drive [ ] #

# bootlist -m normal -o
hdisk0 blv=hd5
hdisk1 blv=hd5

# bootlist -m service -o
hdisk0 blv=hd5
hdisk1 blv=hd5

needless to say, I reissued bosboot command, no difference, and then tried reinstall; this time, using a media that has 5300-03, and the problem is still there. This is the first 5300-03 system I have installed, previously, I have worked on 5300-02, no problem. Is this something with 5300-03? I searched google and IBM site, but no luck..

Assistance greatly appreciated!

dave

Forgot to mention - I can reboot the system with this symptom without any problem whatsoever. it comes up fine.

dave

Some things you can check

lqueryvg -Atp hdisk0
lqueryvg -AtP -p /dev/hdisk0
lslv -l hd5
also check the ODM
odmget -q "name=hd5" CuAt |pg

I have used this before to fix ODM problems

1. Fix the odm view of the root
   ========================
   if you can run this command it try this prosedure

redefinevg -d hdisk0 rootvg
synclvodm -v rootvg

The first thing you should do is to report the problem to IBM to fix if it is a new BUG.
I never try to go to the new releas of ML on AIX I wait atleast a month or more for other s to find out about the bugs etc...
stay one behind until it looks ok.

Sorry had to just say make sure you have a mksysb copy save some where

and then you can also recreate the boot hd5

recreating hd5

rmlv hd5
mklv -y hd5 -t boot -a e rootvg 1 hdisk0

lslv hd5
1 pps now, so should have enough space
but will extend it
extendlv hd5 1

when doing mksysb backup make sure no error come up

Hi Ravager, thanks for the response.

we had a chance to install AIX 5.3 ML 3 on a test server, a stand alone 170 machine, and it did the same thing with these strange response when looking at bootlist.

I think this might be a bug, so we will post this to IBM for suggestions, recommendation.

thanks again,
dave