[Gulli] lilo e grub

Alessandro Guarguaglini ilguargua@tiscali.it
Mer 13 Apr 2005 21:41:32 CEST


Alle 18:44, mercoledì 13 aprile 2005, dado ha scritto:
> Alle 18:20, mercoledì 13 aprile 2005, Alessandro Guarguaglini ha scritto:
>
> sorry?
>

Tra le righe si deve leggere : Kmail e' un programma di m....a!

> :-)

Vabbe', ci riprovo..

Ciao a tutti,

Mi vergogno un po', ma devo purtroppo ammettere che non mi ricordo il nome di 
chi chiedeva delucidazioni rispetto a lilo e grub ( a mia parziale discolpa 
posso dire che ho saltato qualche incontro ed era la prima volta che lo 
vedevo, ma non e' granche' come scusa).
Anyway...

Grub :

The following is a comprehensive list of error messages for the
Stage 2 (error numbers for the Stage 1.5 are listed before the colon in
each description):
[...]
25 : Disk read error
     This error is returned if there is a disk read error when trying to
     probe or read data from a particular disk.


lilo :

Disk error codes
- - - - - - - -

If the BIOS signals an error when LILO is trying to load a boot image, the
respective error code is displayed. The following BIOS error codes are
known:

[...]

   0x01   "Illegal command". This shouldn't happen, but if it does, it may
    indicate an attempt to access a disk which is not supported by the
    BIOS. See also "Warning: BIOS drive 0x<number> may not be accessible"
    in section "Warnings".


Nel caso di grub, se hai riformattato la partizione penso sia normale che 
abbia avuto problemi a leggere i dati.
Per lilo invece penso sia necessario dare un'occhiata al lilo.conf  
(/etc/lilo.conf) , ed eventualmente rimaneggiarlo. 
Altri problemi potrebbero riguardare il tipo di BIOS :

  - For yet unknown reasons, LILO may fail on some systems with AMI BIOS if
    the "Hard Disk Type 47 RAM area" is set to "0:300" instead of "DOS 1K".
  - Some disk controller BIOSes perform disk geometry/address translations
    that are incompatible with the way the device's geometry is seen from
    Linux, i.e. without going through the BIOS. Particularly, large IDE
    disks and some PCI SCSI controllers appear to have this problem. In
    such cases, either the translated geometry has to be specified in a
    DISK section or the sector address translation can be deferred by using
    the LINEAR option. In a setup where floppies are not normally used for
    booting, the LINEAR approach should be preferred, because this avoids
    the risk of specifying incorrect numbers.
  - Some BIOSes don't properly recognize disks with an unusual partition
    table (e.g. without any partition marked active) and refuse to boot
    from them. This can also affect the second hard disk and the problem
    may only occur if the system is booted in a particular way (e.g. only
    after a cold boot).
  - On some systems, using LINEAR and COMPACT or LBA32 and COMPACT together
    leads to a boot failure. The exact circumstances under which this
    happens are still unknown.

Per il momento di piu' non so dirti, prova a fare il boot con una 
'live' (knoppix, knopils, slax, etc) , monta la partizione con linux e 
controlla il contenuto del lilo.conf . Se fai delle modifiche ricorda che per 
renderle effettive devi reinstallare lilo ( da console : su (password) ; 
chroot /path/to/linux/part ; lilo -v  ; exit)

Ciao, a presto.


Maggiori informazioni sulla lista Gulli