[97610] in RedHat Linux List
Re: LIL- problems
daemon@ATHENA.MIT.EDU (Jose M. Sanchez)
Wed Nov 4 03:53:00 1998
From: "Jose M. Sanchez" <opjose@ex-pressnet.com>
To: <redhat-list@redhat.com>, <redhat-list@elanco.k12.pa.us>
Cc: <kevin_myer@elanco.k12.pa.us>
Date: Wed, 4 Nov 1998 04:03:49 -0500
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
The master parameter block is not initialized properly by linux.
To avoid this problem you need to make, if even, a small DOS partition
first. Format it, then delete it.
From then on Linux will get the correct information it needs from the BIOS
at bootup...
Lilo will also then correctly deal with the drive...
I had the same problem...
-JMS
-----Original Message-----
From: Kevin Myer <kevin_myer@elanco.k12.pa.us>
To: redhat-list@elanco.k12.pa.us <redhat-list@elanco.k12.pa.us>
Date: Tuesday, November 03, 1998 10:15 AM
Subject: LIL- problems
>Hi,
>
>I've been bedeviled by LILO ever since I've started using Linux.
>Sometimes, it works fine when I do a fresh install, other times I'm forced
>to boot from a floppy. And most of the time, I haven't been able to
>figure out how to fix it.
>
>On my current machine, I get:
>
>LIL-
>
>Digging around in some FAQ, I find the following:
>
>LIL- The descriptor table is corrupt. This can either be caused by a
>geometry mismatch or by moving /boot/map without running the map
>installer.
>
>However, I don't know how to remedy the situation. How do I go about
>checking for a geometry mismatch? And suppose I did /boot/map - how do I
>go about running the map installer (is that LILO?)
>
>Currently, kernels and junk like that does reside in /boot which is part
>of the root directory and mounted off of /sda1.
>
>Here's relevant information:
>
>I have a 4.3Gb Quantum SCSI drive and I'm using an Adaptect 2940UW SCSI
>card. The drive was partitioned with Disk Druid since at the time I
>didn't know how to use fdisk.
>
>My /etc/lilo.conf is:
>
>boot = /dev/sda1
>delay = 5 # optional, for systems that boot very quickly
>vga = ASK # force sane state
>append="mem=128M"
>root = current # use "current" root
>map = /boot/System.map
>image = /boot/vmlinuz
> label = linux
>
>The partition table from fdisk is:
>
>Disk /dev/sda: 255 heads, 63 sectors, 553 cylinders
>Units = cylinders of 16065 * 512 bytes
>
> Device Boot Begin Start End Blocks Id System
>/dev/sda1 * 1 1 42 337333+ 83 Linux native
>/dev/sda2 43 43 553 4104607+ 5 Extended
>/dev/sda5 43 43 166 995998+ 83 Linux native
>/dev/sda6 167 167 290 995998+ 83 Linux native
>/dev/sda7 291 291 414 995998+ 83 Linux native
>/dev/sda8 415 415 497 666666 83 Linux native
>/dev/sda9 498 498 513 128488+ 82 Linux swap
>/dev/sda10 514 514 553 321268+ 83 Linux native
>
>I'm at my wits end how to remedy this - the first partition is toggled as
>bootable, the kernel and other info reside there, yes I have indeed run
>lilo after installing the kernel and everything seems like it should be.
>Is this only solveable by a fresh reinstall with a brand new partition
>table? I don't mind booting from a floppy but sometimes I take it out
>while duplicating disks and forget to replace it and find my machine hung
>at LIL- when rebooting.
>
>Any ideas?
>
>I apologize if this is covered somewhere - I've dug and dug and what
>documentation is out there is good if its very specific to what problem
>you're having but I can't seem to find anything specific to my problem.
>
>Thanks,
>
>Kevin
>
>--
>Kevin M. Myer
>Technical Services Specialist
>ELANCO School District
>
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
