<div>Thanks Jeff and all list,</div>
<div> </div>
<div>I could manage run e2fsck on three out of four logical volumes, Fourth one is swap!. (after umount)</div>
<div>Results are </div>
<div>1of4 root -> clean</div>
<div>2f 4 home -> clean, </div>
<div>3of4 is a backup file storage - has no system files at all (is not placed in fstab but used manually.)</div>
<div>3/3 shows -> mounted 156 times without being checked, heck forced. Pass 1 - - - Pass 5 -> (no message) ----48/434592 files 31.3% non-contiguous.</div>
<div>4of4 swap could not umount it to run e2fsck on it (- says it is busy)</div>
<div>After doing this, I rebooted into rescue mode again to check the files and find no change in status.</div>
<div> </div>
<div>/lib/libacl.so.1.1.0 is a corrupted file pointed from a healthy link /lib/libacl.so.1 ( ls -l lists it OK)</div>
<div>/lib/libpcre.so.0 is a corrupted link pointing to a healthy file libpcre.so.0.0.1</div>
<div>/lib/libdb.4.3.so is a corrupted file. NO link in /lib pointing to it but there are healthy files /lib/libdb-<a href="http://4.1.so">4.1.so</a> and /libdb-4-2.so</div>
<div> </div>
<div>Please suggest repair method - can these two faulty files be deleted ! and put healthy (new) files in /lib and recreate faulty link.</div>
<div>Or any other way</div>
<div>Please guide....many thanks in advance.<br><br> </div>
<div><span class="gmail_quote">On 11/27/05, <b class="gmail_sendername">Jeff Vian</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jvian10@charter.net" target="_blank">jvian10@charter.net</a>
> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Sat, 2005-11-26 at 22:35 +0530, Anil Kumar Sharma wrote:<br>> Found problem - please suggest solution
<br>><br>> -------------------------------<br>> Normal boot time error is<br>> fgrep: error while loading shared libraries: /lib/libpcre.so.0: cannot<br>> read file data: invalid argument<br>> -------------------------------
<br>> Boot with rescue disk<br>> boot: garbage <enter> !else kernel panic: same as original<br>> 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!<br>><br>> and I get prompt in rescue mode. I mean no parameters or other boot
<br>> option are given.<br>> -------------------------------<br>> # chroot /mnt/sysimage<br><br>here you need to look at the mounted filesystems or at the content<br>of /etc/fstab to get the name of the *logical volumes* in sda4. You
<br>*cannot* run e2fsck on an lvm partition. You instead run e2fsck on the<br>logical volume within that partition..<br><br>for example, on mine the mount command gives:<br>[jeff@eye-gore ~]$ mount<br>/dev/mapper/VG00-LV01 on / type ext3 (rw)
<br>/dev/proc on /proc type proc (rw)<br>/dev/sys on /sys type sysfs (rw)<br>/dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620)<br>/dev/hda1 on /boot type ext3 (rw)<br>/dev/shm on /dev/shm type tmpfs (rw)<br>/dev/mapper/VG00-LV02 on /home type ext3 (rw)
<br><br>and to run e2fsck on / I would need to use<br>e2fsck /dev/mapper/VG00-LV01 (With it unmounted of course).<br><br><br>> # ls !any command gives error like<br>> ls: error while loading shared libraries: /lib/libacl.so.1: cannot
<br>> read file data: invalid argument<br>> If I exit from chroot or do not chroot in the first place, ls command<br>> works as normal<br>> Therefore without chroot I can see all my partitions mounted and files
<br>> intact EXCEPT following<br>> # 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<br>> too fast cannot capture it.
<br>> ! Found these three file corrupted; all others seem to<br>> be OK in dir lib.<br>> libpcre.so.1.1.0 libacl.so.1 <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://libdb-4.3.so/" target="_blank">
libdb-4.3.so</a><br>> (libacl.so.1 is a link pointing to libacl.so.1.1.0)<br>><br>> ls -l on above three individual files gives<br>><br>> ?rws--s-wT 65455 429148268 428933146 4289396678 Nov 2<br>
> 1969 libacl.so.1.1.0<br>> ?rws--Sr-T 65454 4291559338 4289658823 4289396680 Oct 27 <br>> 1969 libpcre.so.0<br>> ?rws--S-wt 65454 4291428271 4289855432 4289331145 Oct 30<br>> 1969
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://libdb-4.3.so/" target="_blank">libdb-4.3.so</a><br>><br>> 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<br>> hacking/virus activity.<br>> Third : What measure to prevent future occurrence?<br>><br>> In ur answer please include how do I get these individual files out
<br>> from rpm packages. or I can simply download.<br>> Thanks a lot in advance.<br>><br>><br>><br>><br>> On 11/26/05, Anil Kumar Sharma <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:xplusaks@gmail.com" target="_blank">
xplusaks@gmail.com</a>> wrote: <br>> 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
<br>> open /dev/sda4 <br>><br>> The superblock could not be read or does not describe a<br>> correct ext2<br>> filesystem. If the device is valid and it really contains an<br>
> ext2<br>> filesystem (and not swap or ufs or something else), then the <br>> superblock<br>> is corrupt, and you might try running e2fsck with an alternate<br>> superblock:
<br>> e2fsck -b 8193 <device><br>><br>> root@1[~]#<br>> --------------------------------------------------------------------<br>> The second para seams to suggest something, that I do not
<br>> feel<br>> confident to attemp.<br>> <br>> -- Anil Kumar Sharma<br>><br>><br>> --<br>> Anil Kumar Shrama<br>><br>><br>><br>> --<br>> Anil Kumar Shrama
<br>> --<br>> fedora-list mailing list<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:fedora-list@redhat.com" target="_blank">fedora-list@redhat.com</a><br>> To unsubscribe: <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">
https://www.redhat.com/mailman/listinfo/fedora-list</a><br><br>--<br>fedora-list mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:fedora-list@redhat.com" target="_blank">fedora-list@redhat.com
</a><br>To unsubscribe: <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-list</a><br></blockquote>
</div><br><br clear="all"><br>-- <br>Anil Kumar Shrama