hi,
We have a RS/6000 43p0-150 that failed to boot due to an error on mounting the /usr maybe because of a corrupted file which probably points to "libc.a" as the error it displayed. Tried to recover it with system boot but failed to access the rootvg.
I have this idea that transfering the hard disk to another RS/6000 so I can access the content of the disk and probably replace only the libc.a and its related files which may have been the cause of boot failure. Afterwhich I'll put it back and try to boot. Will this idea be ok?
The failed RS has no system backup.
Last option will be to replace the OS with the backup of another RS/6000 43p with the same application but we're trying to avoid that since there is a licensed application on the failed disk. Replacing would mean loss of the license.
HELP please
We have a RS/6000 43p0-150 that failed to boot due to an error on mounting the /usr maybe because of a corrupted file which probably points to "libc.a" as the error it displayed. Tried to recover it with system boot but failed to access the rootvg.
I have this idea that transfering the hard disk to another RS/6000 so I can access the content of the disk and probably replace only the libc.a and its related files which may have been the cause of boot failure. Afterwhich I'll put it back and try to boot. Will this idea be ok?
The failed RS has no system backup.
Last option will be to replace the OS with the backup of another RS/6000 43p with the same application but we're trying to avoid that since there is a licensed application on the failed disk. Replacing would mean loss of the license.
HELP please