[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: grub: error 18



Il giorno mer, 01/08/2007 alle 07.56 +0200, heba ha scritto:
> Il 31/07/07, heba<mat.r.gl@gmail.com> ha scritto:
> > salve a tutti,
> >
> > dopo la rottura del mio  disco, l'ho sostituito con uno un po' piú
> > moderno da 160 gb, pata.
> >
> 
> ieri sera ho provato ad installarci altre due distribuzioni, mandriva
> funziona, ubunutu  e debian no, mi da errore durante la formattazione
> e non c'è verso di fargli installare quel benedettissimo grub/lilo.
> 
> Quindi il problema non è hardware come invece sosteneva il sistema
> quando me lo installava, altrimenti nessuna distro avrebbe potuto
> installarsi.
> 
> Qualcuno sa dirmi il perchè sui maxtor 160 gb pata non si può
> installare grub o lilo, per cortesia?
> 
> buona giornata a tutti.
> 
> m.
> 

cercando su google grub error 18 e selezionando il primo link ho
trovato:

Error 18
Error 18: Selected cylinder exceeds maximum supported by BIOS
This error is returned when a read is attempted at a linear block
address beyond the end of the BIOS translated area. This generally
happens if your disk is larger than the BIOS can handle (512MB for
(E)IDE disks on older machines or larger than 8GB on others.). In more
practical terms this means the BIOS is unable to start executing the
kernel because the kernel is not located within the block it can access
at boot up time.

This can be circumvented by creating a boot partition at the beginning
of the disk that is completely within the first 1023 cylinders of the
harddrive. This partition will contain the kernel. 

The kernel it self does not suffer from the same limitations as the BIOS
so after the BIOS has loaded the kernel the kernel will have no problem
accessing the whole harddrive. Newer BIOSes will automatically translate
the harddrives size in a way that it can be completely contained within
the first 1023 cylinders and hence modern computers do not suffer from
this problem. 
The same error can happen when the BIOS detects a disk in a different
way as Linux does. This can happen when changing motherboards or when
moving a GRUB-bootable disk from one computer to another. If this
happens, just boot with a GRUB floppy, read the C/H/S numbers from the
existing partition table and manually edit the BIOS numbers to match. If
using a SUSE linux and installing on VM Ware this problem is solved by
creating a small partition at the very beginning of the harddisc, and
mounting it as /boot.

ciao.
-- 
Donato Pasqualicchio <natas@natas.us>



Reply to: