Hi,
Someone corrupted my libc.so file and linux now refuses to boot, giving a kernel panic. the kernel kills the init process!!!
Now I wish to reinstall glibc. The problem is I have no CD drive attached to the machine. I have a floppy drive though. And the "pseudo-corrupted" kernel is the only kernel on the machine. the machine is attached to a network.
Is there anyway I can boot into the machine in rescue mode using floppies? The boot images in the CD are installation ones. and other boot images of other machines won't work because it again runs init which contacts libc.so file.
Thanks,
»-----Original Message----- »From: linuxers-bounces@mm.ilug-bom.org.in On Behalf Of Goldwyn »Rodrigues »Subject: [ILUG-BOM] Corrupted kernel »Someone corrupted my libc.so file and linux now refuses to boot, »giving a kernel panic. the kernel kills the init process!!! » »Now I wish to reinstall glibc. The problem is I have no CD drive »attached to the machine. I have a floppy drive though. And the »"pseudo-corrupted" kernel is the only kernel on the machine. the »machine is attached to a network. » »Is there anyway I can boot into the machine in rescue mode using »floppies? The boot images in the CD are installation ones. and »other boot images of other machines won't work because it again »runs init which contacts libc.so file.
You have following options, afik 1. attach the hdd to a linux machine, mount the filesystem somewhere and copy the libc.so file from that machine.
this should work if the files are identical
2. attach an cd-rom temporarily and use the installation cd-rom
3. i think u can create a minimal linux disk with the file libc.so on it then u can boot with this and perform operation similar to suggestion 1 but here i dont know size of liso.c and process to create the disk also :0)
4. (this is looong method in case u dont wish to open the cabinet but are ready to fiddle around) setup linux diskless client server on another machine and boot a client on your machine. once the client booted using remote server, u can mount local hdd and transfer the file from the remote server
:-) HTH n HTW(orks)
Thanks and Regards, Kiran Ghag Web Page: http://kiran7.freeservers.com _________________________________________________ Computers are like air conditioners. They work fine until you start opening windows.
Someone corrupted my libc.so file and linux now refuses to boot, giving a
Someone?
Is there anyway I can boot into the machine in rescue mode using floppies?
The boot images in the CD are installation ones. and other boot images of
Write the boot.img from the CD to the floppy and boot from it. It will start the installation process. Before it actually does anything (after keyboard and language set up), do Alt+F2 - you'll get a command prompt.
Create a mnt directory, and mount your root partition under that.
You can now write a safe libc.so file to /lib
Reboot.
On Mon, 2004-04-05 at 17:51, Goldwyn Rodrigues wrote:
Hi,
Someone corrupted my libc.so file and linux now refuses to boot, giving a kernel panic. the kernel kills the init process!!!
libc.so is provided to me by glibc on my SuSe system, that should be the same on your system as well. Create a bootable linux floppy (many are available online) and then boot using that, network your machine, download glibc foryour distribution, and install it. Simple. The doubt, how to you know that libc.so is the corrupted file.
-- Goldwyn :o)
libc.so is provided to me by glibc on my SuSe system, that should be the same on your system as well. Create a bootable linux floppy (many are available online) and then boot using that, network your machine, download glibc foryour distribution, and install it. Simple.
Actually the subject of the mail should be corrupted libc.so
Thanks a lot, it worked! Got a bootable image called RIP (Rescue is possible). Its a nice self contained distro with some good packages. I found another one by tom, but din't have the time to customize it.
Since the libc.so.6 was corrupted I could not try any linux floppy which requires the disk. Making a boot disk finally resorts to init, which requires libc.so.6. RIP uses a RAM disk.
Opening the system was kept as the last option. So attaching the CD Drive or removing the HDD were not an option as of now.
The doubt, how to you know that libc.so is the corrupted file.
The last message the kernel showed "libc.so.6 file too short. Trying to kill init.". Yes the kernel killed init!! .....stopped. libc.so.6 is required by init.
-
Amish Munshi -
goldwyn Rodrigues -
Goldwyn Rodrigues
-
Kiran Ghag -
Philip Tellis