Hi, I've been using an CentOS4.4 version. All was well till 2 days back. Suddenly when the PC was booted-up, it wouldn't bootup. It gets stuck displaying the following message. exec of init (/sbin/init) failed !!!: 80 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! I entered the rescue mode and attempted chroot /mnt/sysimage It spitted an error "chroot : cannot execute /bin/sh: Accessing a corrupted shared library." I tried to google-out the problem in vain Any clues as to whats the problem and the remedy? TIA, Balaji
Balaji wrote:> Hi, > I've been using an CentOS4.4 version.I dont know what the solution to your issue is - you didnt provide enough info to diagnose or even propose any fix's - however, WHY are you running such an old version of the distro ? you really should be doing yum updates and keeping your machine patched. -- Karanbir Singh CentOS Project { centos.org } irc: z00dax, #centos at irc.freenode.net
On Jan 21, 2008 9:30 AM, Balaji <balajisundar at midascomm.com> wrote:> Hi, > I've been using an CentOS4.4 version. > All was well till 2 days back. Suddenly when the PC was booted-up, it > wouldn't bootup. It gets stuck displaying the following message. > > exec of init (/sbin/init) failed !!!: 80 > umount /initrd/dev failed: 2 > Kernel panic - not syncing: Attempted to kill init! > > I entered the rescue mode and attempted > chroot /mnt/sysimage > It spitted an error > > "chroot : cannot execute /bin/sh: Accessing a corrupted shared library."It look like some of your file are corrupted. On a working machine : # ldd /bin/sh linux-gate.so.1 => (0x002a4000) libtermcap.so.2 => /lib/libtermcap.so.2 (0x00955000) libdl.so.2 => /lib/libdl.so.2 (0x0089c000) libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0x00757000) /lib/ld-linux.so.2 (0x00735000) [root at max udev]# rpm -qf /lib/libtermcap.so.2 /lib/libdl.so.2 /lib/i686/nosegneg/libc.so.6 /lib/ld-linux.so.2 libtermcap-2.0.8-46.1 glibc-2.5-18.el5_1.1 glibc-2.5-18.el5_1.1 glibc-2.5-18.el5_1.1 You shoud try to check these package : # rpm -V --root /mnt/sysimage libtermcap glibc and be ready to resinstall them if required # rpm -ivh --force --root /mnt/sysimage /yoursource/libtermcap-*.rpm /yoursource/glibc-*.rpm Then you should be able to make your chroot In anyway identify all your corrupted files using # rpm -Va And reinstall the corrupted packages Regards> > I tried to google-out the problem in vain > > Any clues as to whats the problem and the remedy? > > TIA, > Balaji > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > lists.centos.org/mailman/listinfo/centos >-- Alain Spineux aspineux gmail com May the sources be with you