<p>Found problem - please suggest solution</p>
<p>-------------------------------<br>Normal boot time error is <br>fgrep: error while loading shared libraries: /lib/libpcre.so.0: cannot read file data: invalid argument<br>-------------------------------<br>Boot with rescue disk
<br>boot: garbage <enter> !else kernel panic: same as original installation!<br>boot could not find kernel image garbage<br>boot: <enter> !normal boot starts!<br>->language: English<br>->keyboard type: us
<br>->setup networking: no<br>->rescue: continue <br>->rescue: ok !here it guides chroot /mnt/sysimage!</p>
<div>and I get prompt in rescue mode. I mean no parameters or other boot option are given.<br>-------------------------------<br># chroot /mnt/sysimage </div>
<div># ls !any command gives error like<br>ls: error while loading shared libraries: /lib/libacl.so.1: cannot read file data: invalid argument<br>If I exit from chroot or do not chroot in the first place, ls command works as normal
<br>Therefore without chroot I can see all my partitions mounted and files intact EXCEPT following</div>
<div># cd /mnt/sysimage/lib<br># ls lib* ! lists file on screen as normal <br># ls -l lib* ! lists file with few unusual listings, as screen moves too fast cannot capture it.</div>
<div> ! Found these three file corrupted; all others seem to be OK in dir lib.<br>libpcre.so.1.1.0 libacl.so.1 <a href="http://libdb-4.3.so">libdb-4.3.so</a></div>
<p>(libacl.so.1 is a link pointing to libacl.so.1.1.0)</p>
<p>ls -l on above three individual files gives</p>
<p>?rws--s-wT 65455 429148268 428933146 4289396678 Nov 2 1969 libacl.so.1.1.0<br>?rws--Sr-T 65454 4291559338 4289658823 4289396680 Oct 27 1969 libpcre.so.0 <br>?rws--S-wt 65454 4291428271 4289855432 4289331145 Oct 30 1969
<a href="http://libdb-4.3.so">libdb-4.3.so</a></p>
<p>There are three questions / concerns - in the order of priority.<br>First: How to recover from this?<br>Second: How this happened? I mean is this some freak error or hacking/virus activity.<br>Third : What measure to prevent future occurrence?
</p>
<p>In ur answer please include how do I get these individual files out from rpm packages. or I can simply download.<br>Thanks a lot in advance.<br></p><br><br>
<div><span class="gmail_quote">On 11/26/05, <b class="gmail_sendername">Anil Kumar Sharma</b> <<a href="mailto:xplusaks@gmail.com">xplusaks@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I missed second paragraph output in previous post,<br>--------------------------------------------------------------------
<br>root@1[~]# fsck /dev/sda4<br>fsck 1.38-WIP (09-May-2005)<br>e2fsck 1.38-WIP (09-May-2005)<br>Couldn't find ext2 superblock, trying backup blocks...<br>fsck.ext2: Bad magic number in super-block while trying to open /dev/sda4
<br><br>The superblock could not be read or does not describe a correct ext2<br>filesystem. If the device is valid and it really contains an ext2<br>filesystem (and not swap or ufs or something else), then the superblock
<br>is corrupt, and you might try running e2fsck with an alternate superblock:<br> e2fsck -b 8193 <device><br><br>root@1[~]#<br>--------------------------------------------------------------------<br>The second para seams to suggest something, that I do not feel
<br>confident to attemp.<br><br>-- Anil Kumar Sharma<br><br><br>--<br>Anil Kumar Shrama<br></blockquote></div><br><br clear="all"><br>-- <br>Anil Kumar Shrama