boot problem due to failure loading libc.a

[tedans]

hi,

would it be safe to copy the file /usr/ccs/lib/libc.a of other workstations which run the same OS and application with the workstation having a problem? hardware is a 43p-150 this seems to be the file that the OS looks into which it can't load due to problems...operating panel displays 0517

 

[sbix]

Well if you haven't a better choice .... just to be sure copy the "problematic" libc.a with a different name

 

[pdperk]

Two questions.(a) what is the task you are trying to complete? (b)are you updating the OS or doing a system migration?

I have seen this before and it is a simple fix if you are trying to do what I was.

 

[tipmiser]

If the 517 is the boot code the message is this:
Mounting client remote file system during network IPL.

How did you determine it is libc.a? Especially during a boot?

 

[pdperk]

TIPMISER - I believe the message is scrolling across the terminal as ha has installed the OS or possibly migrated the OS. Once the mksysb has been isntalled if there is a mismatch in the OS the libc.a get confused because of the C mismatch. I am sure that the load process controls from the boot media or CD media which libc.a is loaded BEFORE the led message occurs.