I got a notice yesterday about 5.2 ML4 being available. I downloaded
the data and applied it to my 7044-260 that was on ML3. Now the box
won't boot.

Can someone advise what the recovery procedure is or am I stuck with
reinstalling AIX?

On 2004-08-26, Roy <garlic@garlic.com> wrote:

> I got a notice yesterday about 5.2 ML4 being available. I downloaded
> the data and applied it to my 7044-260 that was on ML3. Now the box
> won't boot.
>
> Can someone advise what the recovery procedure is or am I stuck with
> reinstalling AIX?

Not if you let us guess what's wrong. See
http://www.catb.org/~esr/faqs/smart-questions.html .

--
Jurjen Oskam
"I often reflect that if "privileges" had been called "responsibilities" or
"duties", I would have saved thousands of hours explaining to people why
they were only gonna get them over my dead body." - Lee K. Gleason, VMS sysadmin

Roy <garlic@garlic.com> wrote in message news:<10iqsu4m71boo29@corp.supernews.com>...
> I got a notice yesterday about 5.2 ML4 being available. I downloaded
> the data and applied it to my 7044-260 that was on ML3. Now the box
> won't boot.
>
> Can someone advise what the recovery procedure is or am I stuck with
> reinstalling AIX?

Have you tried booting into maintenance mode via CD or tape? Is your
bootlist still intact?

HTH,
Pete's

I haven't checked that yet. The machine is remote. Here's what the
console shows though. The boot image timestamp is correct.




-------------------------------------------------------------------------------
Welcome to AIX.
boot image timestamp: 17:47 08/25
The current time and date: 03:44:47 08/26/2004
number of processors: 2 size of memory: 512Mb
boot device: /pci@fef00000/scsi@c/sd@9:2
closing stdin and stdout...
-------------------------------------------------------------------------------

Pete's wrote:
> Roy <garlic@garlic.com> wrote in message news:<10iqsu4m71boo29@corp.supernews.com>...
>
>>I got a notice yesterday about 5.2 ML4 being available. I downloaded
>>the data and applied it to my 7044-260 that was on ML3. Now the box
>>won't boot.
>>
>>Can someone advise what the recovery procedure is or am I stuck with
>>reinstalling AIX?
>
>
> Have you tried booting into maintenance mode via CD or tape? Is your
> bootlist still intact?
>
> HTH,
> Pete's

Roy <garlic@garlic.com> wrote in message news:<10iru13g81dgjc7@corp.supernews.com>...
> I haven't checked that yet. The machine is remote. Here's what the
> console shows though. The boot image timestamp is correct.
>
>
>
>
> -------------------------------------------------------------------------------
> Welcome to AIX.
> boot image timestamp: 17:47 08/25
> The current time and date: 03:44:47 08/26/2004
> number of processors: 2 size of memory: 512Mb
> boot device: /pci@fef00000/scsi@c/sd@9:2
> closing stdin and stdout...
> -------------------------------------------------------------------------------
>
> Pete's wrote:
> > Roy <garlic@garlic.com> wrote in message news:<10iqsu4m71boo29@corp.supernews.com>...
> >
> >>I got a notice yesterday about 5.2 ML4 being available. I downloaded
> >>the data and applied it to my 7044-260 that was on ML3. Now the box
> >>won't boot.
> >>
> >>Can someone advise what the recovery procedure is or am I stuck with
> >>reinstalling AIX?
> >
> >
> > Have you tried booting into maintenance mode via CD or tape? Is your
> > bootlist still intact?
> >
> > HTH,
> > Pete's

I suspect that you lost your bootlist. You say it's remote, can
someone look at the lcd panel(I'm not sure if the 7044 has one) while
it boots and see what the last string displayed is? If it's E1F1,
odds are you lost your boot list and AIX doesn't know where to boot
from. In that case, boot to maintenance mode, set the boot list and
reboot.

HTH,
Pete's

Pete's wrote:

> Roy <garlic@garlic.com> wrote in message news:<10iru13g81dgjc7@corp.supernews.com>...
>
>>I haven't checked that yet. The machine is remote. Here's what the
>>console shows though. The boot image timestamp is correct.
>>
>>
>>
>>
>>-------------------------------------------------------------------------------
>> Welcome to AIX.
>> boot image timestamp: 17:47 08/25
>> The current time and date: 03:44:47 08/26/2004
>> number of processors: 2 size of memory: 512Mb
>>boot device: /pci@fef00000/scsi@c/sd@9:2
>>closing stdin and stdout...
>>-------------------------------------------------------------------------------
>>
>>Pete's wrote:
>>
>>>Roy <garlic@garlic.com> wrote in message news:<10iqsu4m71boo29@corp.supernews.com>...
>>>
>>>
>>>>I got a notice yesterday about 5.2 ML4 being available. I downloaded
>>>>the data and applied it to my 7044-260 that was on ML3. Now the box
>>>>won't boot.
>>>>
>>>>Can someone advise what the recovery procedure is or am I stuck with
>>>>reinstalling AIX?
>>>
>>>
>>>Have you tried booting into maintenance mode via CD or tape? Is your
>>>bootlist still intact?
>>>
>>>HTH,
>>>Pete's
>
>
> I suspect that you lost your bootlist. You say it's remote, can
> someone look at the lcd panel(I'm not sure if the 7044 has one) while
> it boots and see what the last string displayed is? If it's E1F1,
> odds are you lost your boot list and AIX doesn't know where to boot
> from. In that case, boot to maintenance mode, set the boot list and
> reboot.
>
> HTH,
> Pete's

I can reboot the box remotely by power cycling it so I was able to go in
and check the bootlist. It seems correct. I added the CD before the
hard drive and will be inserting the system CD to get it into
maintenance mode.

I guess the question is what is the next step. Do I reinstall AIX in
preservation mode? How does one recover from a failed upgrade?

Roy

Little bit of a follow up.

Summary of my previous notes

I installed 5.2ML4 on a 7043-260 and the system failed to boot. It
hangs with the message "AIX is starting" in the operator display window

Current status:

I can boot a installation CD but when I enter maintenance mode and mount
/usr, the system starts giving messages like shown below. All commands
fail with the same messages.

Two different install CDs fail with the same messages. fsck on /usr
(and the other filesystems) runs clean.

Could not load program sh:
Symbol resolution failed for /usr/lib/libc.a(shr.o) because:
Symbol projctl (number 143) is not exported from dependent
module /unix.
Symbol getpeereid (number 239) is not exported from dependent
module /unix.
Symbol shm_open (number 305) is not exported from dependent
module /unix.
Symbol shm_unlink (number 306) is not exported from dependent
module /unix.
Symbol mq_close (number 307) is not exported from dependent
module /unix.
Symbol mq_unlink (number 308) is not exported from dependent
module /unix.
Symbol mq_getattr (number 309) is not exported from dependent
module /unix.
Symbol mq_setattr (number 310) is not exported from dependent
module /unix.
Symbol mq_send (number 311) is not exported from dependent
module /unix.

Before I give up and reinstall, does anyone have any ideas on how to
avoid the reinstall process?

Has anyone successfully installed 5.2ML4 or has IBM screwed the pooch on
this?

Roy

Roy <garlic@garlic.com> wrote:
R> Little bit of a follow up.

R> Summary of my previous notes

R> I installed 5.2ML4 on a 7043-260 and the system failed to boot. It
R> hangs with the message "AIX is starting" in the operator display window

R> Current status:

R> I can boot a installation CD but when I enter maintenance mode and mount
R> /usr, the system starts giving messages like shown below. All commands
R> fail with the same messages.

R> Two different install CDs fail with the same messages. fsck on /usr
R> (and the other filesystems) runs clean.

R> Could not load program sh:
R> Symbol resolution failed for /usr/lib/libc.a(shr.o) because:
R> Symbol projctl (number 143) is not exported from dependent
R> module /unix.
R> Symbol getpeereid (number 239) is not exported from dependent
R> module /unix.
R> Symbol shm_open (number 305) is not exported from dependent
R> module /unix.
R> Symbol shm_unlink (number 306) is not exported from dependent
R> module /unix.
R> Symbol mq_close (number 307) is not exported from dependent
R> module /unix.
R> Symbol mq_unlink (number 308) is not exported from dependent
R> module /unix.
R> Symbol mq_getattr (number 309) is not exported from dependent
R> module /unix.
R> Symbol mq_setattr (number 310) is not exported from dependent
R> module /unix.
R> Symbol mq_send (number 311) is not exported from dependent
R> module /unix.

R> Before I give up and reinstall, does anyone have any ideas on how to
R> avoid the reinstall process?

R> Has anyone successfully installed 5.2ML4 or has IBM screwed the pooch on
R> this?

R> Roy

Chances are, the symlink, /unix -> /usr/lib/boot/unix_mp (or unix_64) is hosed.
If that's the case, you might try (after booting from CD):

mount /dev/hd4 /mnt
mount /dev/hd2 /mnt/usr
cd /mnt

ln -s /usr/lib/boot/unix_mp /mnt/unix

If unix_mp is wiped out, at this point, you'd have to restore it from a
mksysb backup.

P.S.: I have AIX 5.1, and, if this is different for 5.2, then, please disregard
my post.

--
Bela Gazdy, EUCLID/AIX Systems Support

Roy <garlic@garlic.com> wrote in message news:<10itjbu8n255h32@corp.supernews.com>...
> Little bit of a follow up.
>
> Summary of my previous notes
>
> I installed 5.2ML4 on a 7043-260 and the system failed to boot. It
> hangs with the message "AIX is starting" in the operator display window
>
> Current status:
>
> I can boot a installation CD but when I enter maintenance mode and mount
> /usr, the system starts giving messages like shown below. All commands
> fail with the same messages.
>
> Two different install CDs fail with the same messages. fsck on /usr
> (and the other filesystems) runs clean.
>
> Could not load program sh:
> Symbol resolution failed for /usr/lib/libc.a(shr.o) because:
> Symbol projctl (number 143) is not exported from dependent
> module /unix.
> Symbol getpeereid (number 239) is not exported from dependent
> module /unix.
> Symbol shm_open (number 305) is not exported from dependent
> module /unix.
> Symbol shm_unlink (number 306) is not exported from dependent
> module /unix.
> Symbol mq_close (number 307) is not exported from dependent
> module /unix.
> Symbol mq_unlink (number 308) is not exported from dependent
> module /unix.
> Symbol mq_getattr (number 309) is not exported from dependent
> module /unix.
> Symbol mq_setattr (number 310) is not exported from dependent
> module /unix.
> Symbol mq_send (number 311) is not exported from dependent
> module /unix.
>
> Before I give up and reinstall, does anyone have any ideas on how to
> avoid the reinstall process?
>
> Has anyone successfully installed 5.2ML4 or has IBM screwed the pooch on
> this?
>
> Roy

Have you looked at the error report?

errpt -a | more

How about checking out the boot log?

alog -t boot -o | more

Check out the other logs that 'alog -L' gives you, i.e. like

boot
bosinst
nim
console
dumpsymp

These are all logs. Then at this point you best bet may be to contact
IBM Support before re-installing.

HTH,
Pete's

Roy <garlic@garlic.com> wrote in message news:<10itjbu8n255h32@corp.supernews.com>...
> Little bit of a follow up.
>
> Summary of my previous notes
>
> I installed 5.2ML4 on a 7043-260 and the system failed to boot. It
> hangs with the message "AIX is starting" in the operator display window
>
> Current status:
>
> I can boot a installation CD but when I enter maintenance mode and mount
> /usr, the system starts giving messages like shown below. All commands
> fail with the same messages.
>
> Two different install CDs fail with the same messages. fsck on /usr
> (and the other filesystems) runs clean.
>
> Could not load program sh:
> Symbol resolution failed for /usr/lib/libc.a(shr.o) because:
> Symbol projctl (number 143) is not exported from dependent
> module /unix.
> Symbol getpeereid (number 239) is not exported from dependent
> module /unix.
> Symbol shm_open (number 305) is not exported from dependent
> module /unix.
> Symbol shm_unlink (number 306) is not exported from dependent
> module /unix.
> Symbol mq_close (number 307) is not exported from dependent
> module /unix.
> Symbol mq_unlink (number 308) is not exported from dependent
> module /unix.
> Symbol mq_getattr (number 309) is not exported from dependent
> module /unix.
> Symbol mq_setattr (number 310) is not exported from dependent
> module /unix.
> Symbol mq_send (number 311) is not exported from dependent
> module /unix.
>
> Before I give up and reinstall, does anyone have any ideas on how to
> avoid the reinstall process?
>
> Has anyone successfully installed 5.2ML4 or has IBM screwed the pooch on
> this?
>
> Roy

I was thinking, could you be having a bootblk issue? Once into
maintenance mode, you may want to try bosboot, lookup the man page, I
don't recall the exact parameters you need.

HTH,
Pete's