4.3.3 to 5.1 Migration Hangs on Reboot

[Ron]

I'm attempting to do a migration install to AIX 5.1 from AIX 4.3.3 ML10 and
after all files are installed and the system begins to reboot, the last
message on the console is "closing stdin and stdout..." and the system hangs
with with an LED code of 0518. The hardware is an F50 and I'm installing from
CD (dated 04/2002 LCD4-1061-03).

If I boot afterwards into maintenance mode and access a volume group and
start a shell, when its checking the /usr filesystem, I get this error;

mount /dev/hd2 on /usr: no such device or address
the mount of /dev/hd2 did not succeed.
exiting to shell

Any ideas on how to get around this??

Thanks,

Ron

[snogfest hosebeast]

Ron <ron@yuma.acns.ColoState.EDU> wrote in message news:<bjnp98$7lh6@yuma.acns.ColoState.EDU>...

> I'm attempting to do a migration install to AIX 5.1 from AIX 4.3.3 ML10 and
> after all files are installed and the system begins to reboot, the last
> message on the console is "closing stdin and stdout..." and the system hangs
> with with an LED code of 0518. The hardware is an F50 and I'm installing from
> CD (dated 04/2002 LCD4-1061-03).
>
> If I boot afterwards into maintenance mode and access a volume group and
> start a shell, when its checking the /usr filesystem, I get this error;
>
> mount /dev/hd2 on /usr: no such device or address
> the mount of /dev/hd2 did not succeed.
> exiting to shell
>
> Any ideas on how to get around this??
>
> Thanks,
>
> Ron

Hi Ron

IBM have a very detailed Redbook on migrating from 4.3 to 5L I suggest
you take a look at that.
Also, do an lppchk to see if all the Filesets are ok.
Check the ODM for bogan entries with qstate=10 as well as qstate=5

export ODMDIR=/usr/lib/objrepos
odmdelete -o product -qstate=10
export ODMDIR=/etc/objrepos
odmdelete -o product -qstate=10

HTH
Henry

[Ron]

snogfest hosebeast <snogfest_hosebeast@yahoo.com> wrote:
: Ron <ron@yuma.acns.ColoState.EDU> wrote in message news:<bjnp98$7lh6@yuma.acns.ColoState.EDU>...
:> I'm attempting to do a migration install to AIX 5.1 from AIX 4.3.3 ML10 and
:> after all files are installed and the system begins to reboot, the last
:> message on the console is "closing stdin and stdout..." and the system hangs
:> with with an LED code of 0518. The hardware is an F50 and I'm installing from
:> CD (dated 04/2002 LCD4-1061-03).
:>
:> If I boot afterwards into maintenance mode and access a volume group and
:> start a shell, when its checking the /usr filesystem, I get this error;
:>
:> mount /dev/hd2 on /usr: no such device or address
:> the mount of /dev/hd2 did not succeed.
:> exiting to shell
:>
:> Any ideas on how to get around this??
:>
:> Thanks,
:>
:> Ron

: Hi Ron

: IBM have a very detailed Redbook on migrating from 4.3 to 5L I suggest
: you take a look at that.
: Also, do an lppchk to see if all the Filesets are ok.
: Check the ODM for bogan entries with qstate=10 as well as qstate=5

: export ODMDIR=/usr/lib/objrepos
: odmdelete -o product -qstate=10
: export ODMDIR=/etc/objrepos
: odmdelete -o product -qstate=10

: HTH
: Henry


Hi Henry,

I already had the Redbook, but looked through it again without finding anything
new that I wasn't doing. Filesets are ok and ODM entries are ok as well.

Thanks for the suggestions.

Ron

[Terry Polzin]

Ron <ron@yuma.acns.ColoState.EDU> wrote in message news:<bjnp98$7lh6@yuma.acns.ColoState.EDU>...

> I'm attempting to do a migration install to AIX 5.1 from AIX 4.3.3 ML10 and
> after all files are installed and the system begins to reboot, the last
> message on the console is "closing stdin and stdout..." and the system hangs
> with with an LED code of 0518. The hardware is an F50 and I'm installing from
> CD (dated 04/2002 LCD4-1061-03).
>
> If I boot afterwards into maintenance mode and access a volume group and
> start a shell, when its checking the /usr filesystem, I get this error;
>
> mount /dev/hd2 on /usr: no such device or address
> the mount of /dev/hd2 did not succeed.
> exiting to shell
>
> Any ideas on how to get around this??
>
> Thanks,
>
> Ron

I had a similar problem when I upgraded my R40 from 4.2.1 -> 4.3.3
ended up having to send support a mksysb they did the upgrade and sent
me the upgraded mksysb and I cloned the R40. In retrospect I'm
wondering if my boot list was fubar (not having checked it prior to
upgrade) I found it to be fubar afterwards.

Can you fsck the device manually? Does lsvg -l rootvg list hd2?

[Ron]

Terry Polzin <t_polzin@yahoo.com> wrote:
: Ron <ron@yuma.acns.ColoState.EDU> wrote in message news:<bjnp98$7lh6@yuma.acns.ColoState.EDU>...
:> I'm attempting to do a migration install to AIX 5.1 from AIX 4.3.3 ML10 and
:> after all files are installed and the system begins to reboot, the last
:> message on the console is "closing stdin and stdout..." and the system hangs
:> with with an LED code of 0518. The hardware is an F50 and I'm installing from
:> CD (dated 04/2002 LCD4-1061-03).
:>
:> If I boot afterwards into maintenance mode and access a volume group and
:> start a shell, when its checking the /usr filesystem, I get this error;
:>
:> mount /dev/hd2 on /usr: no such device or address
:> the mount of /dev/hd2 did not succeed.
:> exiting to shell
:>
:> Any ideas on how to get around this??
:>
:> Thanks,
:>
:> Ron


: I had a similar problem when I upgraded my R40 from 4.2.1 -> 4.3.3
: ended up having to send support a mksysb they did the upgrade and sent
: me the upgraded mksysb and I cloned the R40. In retrospect I'm
: wondering if my boot list was fubar (not having checked it prior to
: upgrade) I found it to be fubar afterwards.

: Can you fsck the device manually? Does lsvg -l rootvg list hd2?

Thanks for the response Terry,

I believe I know what the problem is now, just not sure how to properly
fix it. Yes, I could fsck the device - no errors. The mount would fail
when selecting accessing a root vg, but when I selected the accessing without
mounting, I could mount /usr which allowed me to look at the install log and
actually see an error. This is the error;

0503-256 installp: Error: A compatibility entry in the supersedes data of
a fileset should have the same name but not the same level as the
compatible fileset. The level should be greater than all base levels
and updates released for the compatible (superseded) fileset. The
fileset in error is:
ifor_ls.libraries 5.1.0.18

I can also run lppchk from here and there are lots of filesets in an
inconsistent state. The reason for the 5.1.0.18 level is because I was
requested a while back to install an apar relating to security and this
was istalled. I don't normally do that, but obviously missed this one
going from 4 to 5.

Ron