Re: Help! Debian unbootable after XP re-install :-(

[Haralambos Geortgilakis <haralambos@ihug.co.nz>]

Hi Yall & especially Doug & Pigeon,

thanx for the feedback guys  :-)

Here is what I've done so far.

In re-installing XP, I used Partition Magic & this changed the order of 
/dev/hdax

I used Knoppix, to mount my hdd's, then my Tux Boot Floppy & edited the 
latters "syslinux.cfg", to point to the new root partition, in my case 
/dev/hda3...

Why, "rescue root=/dev/hda3" failed, I dunno.

Anyhow, that last piece of magic worked  :-)

Now I get the following error message when re-running lilo....

<snip>
haralambos:/home/haralambos# lilo
Added Linux *
Skipping /vmlinuz.old
Fatal: First sector of /dev/hda3 doesn't have a valid boot signature
haralambos:/home/haralambos#
<snip>

How do I fix that mess?

My /boot is /dev/hda1   ????

*BFN*

Greek Geek  :-)

Doug MacFarlane wrote:

> I had a similar problem and never solved it.  I posted to this group and
> didn't get an answer.  It sounds like you were running a pre-packaged kernel
> version 2.4.something - at some point the pre-packaged kernels started using initrd
> images to boot and I was never able to figure out how to boot via initrd
> via the rescue floppy . . . 
>
> If you have a few hundred mb available to setup a partition, if you install
> from a CD, you should be able to get LILO back, and then enter the proper
> stanza for your full system.  Then re-run LILO to get it running from your
> full systems root partition with the initrd=/initrd.img directive.
>
> Good luck.
>
> madmac
>
>
> On 22 Nov 2002, 10:27:25, Haralambos wrote:
>  
>
> > I've tried rescue root=/dev/hda3  (this changed from the previous 
> > /dev/hda4)
> >
> > I've tried going into ash, the Bourne shell clone & re-running lilo, 
> > only go get back "invalid argument."
> >
> > But, but, there is a perfectly fine root partition @ /dev/hda3...!
> >
> > I've tried the Tux installer, to re-run lilo, same "invalid argument...."
> >
> > When I try to boot, with my boot floppy or was it rescue (?), anyways, 
> > error message reads "Kernel panic: No init found. Try passing init= 
> > option to kernel."
> >
> > Well, I am not panicking just yet (Kernel is-surely both panicking would 
> > be baaaad!), mild apprehension & some effects of sleep deprivation.....
> >
> > *BFN*
> >
> > Greek Geek  :-)
> >