On Tue, Jul 17, 2001 at 11:21:00AM +0200, Bert Vortman wrote:
> That is strange, i did a completely fresh install, not an upgrade! The
> BIOS was not changed either.
> And boot=/dev/hda is present too. This is my partition 'layout':
>
> hda1: /
> hda2: /win98 fat32
> hda3: /home
> hda4: /stuff
> hda5: /graphics fat32
> hda6: /games fat32
HAVE YOU FORMATTED AND MOUNTED YOUR EXTENDED PARTITION?
It has to be hda1, hda2, hda3 or hda4.
You will have to delete the corrupted extended partition and
everything in it. But it is corrupt and may not go easily. What
remains is to wipe out the entire disk and start over.
If you have more than 4 partitions, then one of the first 4 has to be
an extended partition. You can't format or mount an extended
partition - its only use is to contain the logical partitions hda5 and
higher.
>
> hdc1: /usr
> hdc2: /var
> hdc3: /tmp
>
> sda1: /root
> sda2: swap
>
> I can't see the reason why it does not work? The only things I changed
> is the place of /root and the swap (thats now on a scsi drive). I backed
> up everything first, resized the /home partition to have the free space
> of the swap which was on the hda drive. Then I did a completely fresh
> install, only home stayed intact. And then the lilo troubles started.
> So, what can i do about it?
>
> Bert.
>
>
> -----Original Message-----
> This can happen if the bios and linux have different
> ideas about which is the first drive, or about which
> drive the /boot partition is on.
>
> It can also happen if you change settings in the bios
> to change which is the boot drive, or to disable drives - bad ideas.
> Decide which drive and controllers you want enabled and which
> drive/controller is first, then stick to it.
>
> Yet another reason: /etc/lilo.conf does not contain
>
> boot=/dev/hda
>
> as it should if you want to boot from the MBR.
>
> On Tue, Jul 17, 2001 at 02:00:17AM +0200, Bert Vortman wrote:
> > Hi,
> >
> > I have changed some of my partitions, resized and moved them. Then I
> > decided to install a fresh Redhat 7.1. The installation went well, no
> > errors. Then I tried to reboot and LILO came back with the 'LI' Error.
>
> > So I booted from a floppy, that went well. I looked into lilo.conf, no
>
> > errors there. So, I did an new 'lilo -v'. No success after a reboot,
> > same 'LI' error. I deleted the MBR with fdisk /mbr, returned to linux,
>
> > did a 'lilo -v', rebooted again, same 'LI' error. I even tried a new
> > install, with the same result. I even re-partioned the drive, and
> > installed another install. no effect too. Same error. What ever I do,
> > I can't get lilo to work. The previous installation before 7.1 worked
> > well, no errors then. It looks like something went wrong with the
> > resizing and moving of partitions, though no errors are found. Anyone
> > having ideas what can cause this weird behaviour? And even more: how
> > do I fix it?
> >
> > Regards,
> >
> > Bert
> >
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
--
Jan Carlson janc at kubwa dot com
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
