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