On 3/16/07, <b class="gmail_sendername">alessandro soprana</b> <<a href="mailto:alessandrosoprana@tiscali.it">alessandrosoprana@tiscali.it</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
valdagno, 16.03.07<br><br>da qualche giorno il programma fa fatica a partire, si impalla sulla<br>prima schermata di caricamento di ubuntu o, come ieri al "grub loading"<br>mi dą errore 18.<br>Se poi riesco a farlo partire dopo 5 minuti o poco pił si blocca.
<br>qualcuno ha gią avuto l'esperienza?<br>alessandro soprana (utente finale ovvero cretino informatico)<br></blockquote></div><br>Cercando su internet :<br><a href="http://wiki.linuxquestions.org/wiki/GRUB#Error_18">
http://wiki.linuxquestions.org/wiki/GRUB#Error_18</a><br><h3><span class="mw-headline">Error 18</span></h3>
<p><i><b>Error 18</b>: Selected cylinder exceeds maximum supported by BIOS</i><br>
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.
</p><p>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. </p>
<p>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.
<br>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.</p>-- <br>Carlo Augusta