AIX 4.3.3 hangs after ML6 update

[test]

Hi Gurus,

I have a p150 rs6000 system. It hangs while booting at the white screen that
says "Starting Software... Please Wait". The harddisk access light is on
all the time, meaning maybe it is trying to access the hard disk. Here are
the steps I followed.

1. Installed aix 4.3.3 from scratch on this system. Rebooted and started
CDE. No problems. Runs fine.
2. Logged into the maintenance shell using F5.
3. Installed update from 4.3.3.0 no maintenance level (ML) to 4.3.3.0 ML6. I
got this update from IBM website. I followed their install suggestions such
as create a new file system for /usr/sys/inst.mages.. use inutoc, installp
etc.
4. Run bosboot -a -d /dev/ipldevice to create new boot image.
5. Reboot
6. System hangs while restarting.

Any idea what is going on? How to fix it?

Another thing is everywhere the documentation says run "oslevel -r" to get
oslevel. But when I run that command, there is no -r option. Am I missing
something? The OS cds I have are original IBM cds with 4.3.3 written on
them.

Thanks

PG

[Marrek]

why you didn't upgrade your box to ML_11 ???? ML_06 is old one and some of
new programs doesn't work with it...

Try to upgrade it to ML_11 and reboot machine then...


regards,
Mark

U¿ytkownik "test" <test@kjhsd.com> napisa³ w wiadomo¶ci
news:9S25b.1258$y3.575@ns45.bih.net.ba...

> Hi Gurus,
>
> I have a p150 rs6000 system. It hangs while booting at the white screen

that

> says "Starting Software... Please Wait". The harddisk access light is on
> all the time, meaning maybe it is trying to access the hard disk. Here are
> the steps I followed.
>
> 1. Installed aix 4.3.3 from scratch on this system. Rebooted and started
> CDE. No problems. Runs fine.
> 2. Logged into the maintenance shell using F5.
> 3. Installed update from 4.3.3.0 no maintenance level (ML) to 4.3.3.0 ML6.

I

> got this update from IBM website. I followed their install suggestions

such

> as create a new file system for /usr/sys/inst.mages.. use inutoc, installp
> etc.
> 4. Run bosboot -a -d /dev/ipldevice to create new boot image.
> 5. Reboot
> 6. System hangs while restarting.
>
> Any idea what is going on? How to fix it?
>
> Another thing is everywhere the documentation says run "oslevel -r" to get
> oslevel. But when I run that command, there is no -r option. Am I missing
> something? The OS cds I have are original IBM cds with 4.3.3 written on
> them.
>
> Thanks
>
> PG
>
>

[Mark Taylor]

oslevel -r flag was introduced at ML09, i think, or ML08...but yes,
install ML11 with updates to rule out any defects.


--
Posted via [url]http://dbforums.com[/url]

[73blazer]

Did you actualy put "/dev/ipldevice" in the bosboot. I think what you
wanted was /dev/hdisk0 or whatever disk your main rootvg is on perhaps
ipldevice is a link, I don't know, but I've never used that, I always
put the device itself in. You may have to boot from CD, start maint.
then mount a root volume group then re-run the bosboot command with the
right device name.
It's either that or youur disk took a crap. Either way, booting to
single user off the CD's the mountint a root volume group should be able
to tell you what happened.
oslevel -r is not available until a certain maint. release, it may have
been 6, but I thought it was 9, not sure.

test wrote:

> Hi Gurus,
>
> I have a p150 rs6000 system. It hangs while booting at the white screen that
> says "Starting Software... Please Wait". The harddisk access light is on
> all the time, meaning maybe it is trying to access the hard disk. Here are
> the steps I followed.
>
> 1. Installed aix 4.3.3 from scratch on this system. Rebooted and started
> CDE. No problems. Runs fine.
> 2. Logged into the maintenance shell using F5.
> 3. Installed update from 4.3.3.0 no maintenance level (ML) to 4.3.3.0 ML6. I
> got this update from IBM website. I followed their install suggestions such
> as create a new file system for /usr/sys/inst.mages.. use inutoc, installp
> etc.
> 4. Run bosboot -a -d /dev/ipldevice to create new boot image.
> 5. Reboot
> 6. System hangs while restarting.
>
> Any idea what is going on? How to fix it?
>
> Another thing is everywhere the documentation says run "oslevel -r" to get
> oslevel. But when I run that command, there is no -r option. Am I missing
> something? The OS cds I have are original IBM cds with 4.3.3 written on
> them.
>
> Thanks
>
> PG
>
>