Hi, If you have a previous BE you should be able to boot into that and then correct the package with "pkg fix <pkg name> --be <boot environment>". The other option you can try is to download the non-AI installer CD b134 iso image, you should be able to boot up with that and copy the file over. Then boot up off of your hard drive and do a "pkg verify" to make sure the rest of your files are okay.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: [email protected] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Saadia Fatima <[email protected]> To: [email protected] Sent: Wed, March 9, 2011 3:58:11 PM Subject: [osol-help] How to fix a corrupt lib file Hi I am on nv134. My system goes in cyclic reboot after a file libsocket.so.1 got corrupted. The system does not boot in single user mode either. The message displayed is ld.so.1: bash: fatal: /lib/libsocket.so.1: wrong ELF data format: ELFDATA2MSB How can I fix this. I have another working boot environment (nv_111). Thanks SF -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list [email protected] _______________________________________________ opensolaris-help mailing list [email protected]
