Re: msito bootu vypisuje lilo "40"
To |
czdebian-l zavinac debian bod cz |
From |
Vaclav Ovsik <Vaclav bod Ovsik zavinac i bod cz> |
Date |
Tue, 13 Aug 2002 09:40:42 +0200 |
Mail-followup-to |
Vaclav Ovsik <Vaclav bod Ovsik zavinac i bod cz>, czdebian-l zavinac debian bod cz |
User-agent |
Mutt/1.3.28i |
On Tue, Aug 13, 2002 at 09:23:21AM +0200, Vlasák Jaroslav wrote:
> Dobry den,
>
> nesetkal se nekdo s nasledujici situaci:
>
> mam Potato a po instalaci na disk (SCSI 2GB disk, 3 partitiony, 800 MB
> Win95, 30 MB swap, zbytek Potato), lilo v MBR, po rebootu misto bootu
> systemu zacne pocitac na obrazovku vypisovat same "40" a nenabootuje. Z
> bootovaci diskety nabehne system normalne.
> System nainstalovany ze stejnych CD na jinem disku ve stejnem pocitaci i v
> jinem pocitaci funguje normalne.
> Pravdepodobne to nejak souvisi s diskem (velikost ?, poloha partiton na
> disku ?), muze nekdo, prosim, poradit?
Viz manual k lilo.
-----<cut>-----
When LILO loads itself, it displays the word "LILO". Each letter is printed
before or after performing some specific action. If LILO fails at some
point, the letters printed so far can be used to identify the problem. This
is described in more detail in the technical overview.
Note that some hex digits may be inserted after the first "L" if a
transient disk problem occurs. Unless LILO stops at that point, generating
an endless stream of error codes, such hex digits do not indicate a severe
problem.
(<nothing>) No part of LILO has been loaded. LILO either isn't installed
or the partition on which its boot sector is located isn't active.
L <error> ... The first stage boot loader has been loaded and started,
but it can't load the second stage boot loader. The two-digit error
codes indicate the type of problem. (See also section "Disk error
codes".) This condition usually indicates a media failure or a geometry
mismatch (e.g. bad disk parameters, see section "Disk geometry").
LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
-----<cut>-----
-----<cut>-----
0x40 "Seek failure". This might be a media problem. Try booting again.
-----<cut>-----
Takze asi to bude ten "geometry mismatch".
-----<cut>-----
Generally, invalid geometry and attempts to use more than two disks without
a very modern BIOS may yield misleading error codes. Please check carefully
if /sbin/lilo doesn't emit any warnings. Then try using the LINEAR or LBA32
option (see section "Global options").
-----<cut>-----
Tak zkuste ten linear ...
--
Zito
Partial thread listing: