MORE repairing corrupted kernel to boot
The debian installation disks also serve as rescue floppies.
The way I read the installation menu is that if you mount previously
initalized partitions, the installation will copy the kernel & base
system onto the drive w/o disturbing other files. Is this correct?
What about dpkg? Will a base installation discard the current
package installation? Is there a way to back up the dpkg package list?
( I found hundreds of disk errors with fsck. I'll probably have to
reinstall most everything, but I'd like to keep the home directories
and some of the config files which appear ok.
I'd like to not reformat the partition if I don't have to.
)
On Sat, 2 Dec 2000, Sebastiaan wrote:
> Date: Sat, 2 Dec 2000 22:11:11 +0100 (CET)
> From: Sebastiaan <sebas@sacred-key.org>
> To: lists@elephants.org
> Cc: debian-user@lists.debian.org
> Subject: Re: repairing corrupted kernel to boot
>
> Hmm, strange. Maybe you should try to boot a rescue floppy and do the job
> from there. I do not have experience yet with Debian rescue disks, but you
> can also go to redhat and download the bootdisk and the rescue disk.
> After you have booted, you can mount whatever you want and fix it (or do a
> chroot /mnt/rootdisk).
>
> Good luck,
> Sebastiaan
>
>
> On Sat, 2 Dec 2000 lists@elephants.org wrote:
>
> >
> > My potato linux partiton won't boot - I assume it was damaged by
> > a series of power outages. I initially got a "crc checksum" error
> > upon booting.
> >
> > /boot is on /dev/hda2 & / is /dev/hda5.
> > When I use the debian boot floppy ( "rescue root=/dev/hda5" )
> > I get the usual startup messages,
> > then:
> > VFS: mounted root ( ext2 filesystem ) readonly
> > Freeing unused kernel memory: 140K freed
> >
> > after the above the computer just seems to freeze. No more display
> > messages, no response to the keyboard.
> >
> > I can get a shell by adding "init=/bin/sash" to above boot options,
> > but I get #11 kills on any commands not built into the sash shell.
> >
> > If I use the boot disk, then the root disk; I can use the install
> > menu's mount pre-initialized partions to mount my partitions. But
> > I get seg faults when I try to compile a kernel or run lilo (including
> > it's chroot option).
> >
> > I'd like to get this system bootable again because I spent a good
> > deal of time tweaking & configuring to my hardware. Where should I
> > go from here?
> >
> > jon
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
> >
>
Reply to: