[ale] Ok, I'm really hosed now.

[Kevin Krumwiede]

Copy that lilo.conf and modify the image= lines so they reflect where the
kernel images are mounted:

image=/mnt/boot/vmlinuz
	label=linux
	root=/dev/hdc1
	append=" hdd=ide-scsi devfs=mount quiet"
	vga=788
	read-only

Because lilo's bootsector doesn't care about filenames, it just needs to
know the disk location of the bootable images.  Remove the entry for the
Windows partition, since it's not bootable anymore and lilo will complain
and not write a bootsector.  Then run lilo using the modified lilo.conf:

lilo -c /mnt/etc/newlilo.conf

If you're going to sacrifice the Windows drive, here's a little trick for
the reinstall.  Add an entry to lilo.conf that looks like this (assuming hdd
is your CD-ROM):

other=/dev/hdd
	label=windows-install
	map-drive=0x80
	    to=0x81
	map-drive=0x81
	    to=0x80
	unsafe

This way you can boot your Windows CD with your hard drives configured as
they are when you normally run it.  It'll write its MBR to what it thinks is
hda, but which is in actuality hdb... thus your LILO bootsector will be
untouched.  Then you can replace the Windows entry in lilo.conf and run lilo
to complete the repair.

Krum



> -----Original Message-----
> From: mebarker at icomcast.net [mailto:mebarker at icomcast.net]On Behalf Of
> Michael Barker
> Sent: Wednesday, March 20, 2002 11:45 AM
> To: Kevin Krumwiede
> Cc: ALE List
> Subject: Re: [ale] Ok, I'm really hosed now.
>
>
> Kevin Krumwiede wrote:
>
> > When you boot from the Mandrake rescue CD, can you still see
> your partitions
> > with fdisk?  Do you know/remember what all your partitions are and where
> > they are supposed to be mounted?  If so, you should be able to recover
> > everything using LILO.
>
> Yes I can see everything with fdisk...
>
> > Mount the partitions containing kernel images
> > somewhere (doesn't matter where) and create a lilo.conf file
> that specifies
> > the partitions you want to boot and the kernels *named as they
> are mounted
> > on your rescue system*.  Then use lilo -c yourlilo.conf (I
> think that's the
> > switch) to set up a new bootloader.
>
> When I boot rescue it mounts my system under /mnt.  Whenever I run lilo
> I always chroot /mnt first.  Is this not the same thing?  If it is, that
> has not worked.
>
> > This will get you back into Mandrake.  As for fixing the MBR on
> your Windows
> > drive... I am not certain, but I think it always contains
> exactly the same
> > thing, i.e., someone with the same version of Windows you're
> using could dd
> > their MBR to a file and send it to you... anyone know for sure?
> >
> > Krum
>
> Again the windows install can be sacrificed, it has no important data
> and I rarely use it.  I only need it now because my cable provider has
> not written their utility interfaces cross browser compatible and I need
> to use IE.
>
> Below is my lilo.conf
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> vga=normal
> default=linux
> keytable=/boot/us.klt
> lba32
> prompt
> timeout=50
> message=/boot/message
> menu-scheme=wb:bw:wb:bw
> image=/boot/vmlinuz
> 	label=linux
> 	root=/dev/hdc1
> 	append=" hdd=ide-scsi devfs=mount quiet"
> 	vga=788
> 	read-only
> image=/boot/vmlinuz
> 	label=linux-nonfb
> 	root=/dev/hdc1
> 	append=" hdd=ide-scsi devfs=mount"
> 	read-only
> image=/boot/vmlinuz
> 	label=failsafe
> 	root=/dev/hdc1
> 	append=" hdd=ide-scsi devfs=mount failsafe"
> 	read-only
> other=/dev/fd0
> 	label=floppy
> 	unsafe
> other=/dev/hda1
> 	label=windows
> 	table=/dev/hda
> 	map-drive=0x80
> 	    to=0x81
> 	map-drive=0x81
> 	    to=0x80
> End Of lilo.conf
>
> Below is my partition table:
>
> Device		Boot...	     ...Id	System
> /dev/hdc1	*		83	Linux
> /dev/hdc2			5	Extended
> /dev/hdc5			82	Swap
> /dev/hdc6			83	Linux
> /dev/hdc7			83	Linux
> /dev/hdc8			83	Linux
> End Of partition table


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.