On Mon, 17 Dec 2001 15:51:38 +0800
Stephen Liu <[EMAIL PROTECTED]> implied:
Alright. 30 minutes was a bit long (usually 1 minute if it's a hostname
problem). I guess I should have specified.
Does a bootdisk work? If so, it's probably a geometry mismatch. If not,
or if you didn't make a bootdisk to try it with, there's more work.
Here's what's needed if you can't test it with a bootdisk or it failed
using that, too.
Here what the Bootdisk HOWTO says about the error:
LIL
The second stage boot loader has been started, but it can't load the
descriptor table from the map file. This is typically caused by a media
failure or by a geometry mismatch.
I'd first look at the "geometry mismatch" part to see if that's it. If
it's "media failure" that's so broad as to be almost impossible to track
down. But if it meant that the drive was bad (one possible definition)
then you'd never be able to get it to boot all of the way no matter
what.
The easiest way to check the geometry is to first find out what the
geometry of the drive should be. Most times it's labelled right on it.
In some, you'll need to lok on the website somewhere to find out.
Then restart the installation. When you get to disk partitioning, choose
fdisk. At the commandline enter "p" to see what you have. 3 things that
you should note. First, does it have the right number of CHS specified
for what you know it should be? Second, take a look at the "blocks"
column and see if there are any plus (+) signs attached to any of the
numbers. Third, are there any overlaps of partitions (i.e. sda1 ends on
100 and sda2 starts on 100)?
If the first instance is a problem, you'll need to go into expert mode
and fix it (too long of an explanation on how, so grab some howtos and
start reading). If the second one is a problem, you'll need to
repartition (maybe even manually) to fix it. (I allowed the installer to
auto partition for me once and it ended up like this. I used it that way
for over 1.5 years before I finally fixed it. A bootdisk will usually
still work if it's this problem.) If the third part is it, same as the
second part: repartition and likely do so manually to prevent the
problem
That's about the best shot I can make at this point.
> Hi,
>
> Thanks for your advice.
>
> I waited for 30 mins without a hope to start Linux
>
>
> I re-installed RH7.2 choosing LILO bootloader instead of Drub. After
> installation completed PC re-started and halted on
>
> LIL-
>
> I used the boot disk to start RH 7.2. This time it went straight
> through without problem with KDE started (default).
>
> My questions are ;
>
> 1) How to correct LIL- to boot Linux
> 2) What are the advantage and disadvantage between LILO and Drub
>
> Thanks in advance.
>
> B.R.
> Stephen
>
>
> At 12:01 PM 12/16/2001 -0600, you wrote:
> >On Mon, 17 Dec 2001 00:25:32 +0800
> >Stephen Liu <[EMAIL PROTECTED]> implied:
> >
> > > Hi All People,
> > >
> > > I newly installed RH 7.2 as workstation on an AMD PC with ATA-66
> > > card(ABIT Hot Rod 66 adapter card) as SCSI adapter. Installation
> > > went through without problem. At re-starting it moved on smoothly
> > > until it came to :
> > >
> > > INIT : Switching to runlevel : 3
> > > INIT : Sending processes to TERM signal
> > > tStarting automount : No Mountpoint Defined [OK]
> > > Starting lpd : No printers Defined [OK]
> > > Starting Wine [Failed]
> > >
> > > then the PC halted.
> > >
> > > I force-re-set (re-started) the PC. It halted again at the same
> > > point.
> > >
> > > Any remedy or pointer ?
> >
> >Halted. As in? Minutes? Seconds? Hours?
> >
> >If you only waited seconds, wait longer. This happens many times when
> >no hostname is assigned. That is the default and is something you can
> >take care of after the boot completes.
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
--
Secret hacker rule #11: hackers read manuals.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
