os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Manually mucking with disk geometry is obsolete.

Browse source 
Approved by:	bcr (mentor)
This commit is contained in:
Eitan Adler 2012-12-10 15:31:26 +00:00
parent 448a5c5d4b
commit 57c9aba307
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40334
1 changed files with 0 additions and 31 deletions

31
en_US.ISO8859-1/books/faq/book.xml
View file

@ -3203,37 +3203,6 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</answer>
</qandaentry>
<qandaentry>
<question id="boot-read-error">
<para>Why does &os;'s boot loader display <errorname>Read
error</errorname> and stop after the BIOS screen?</para>
</question>
<answer>
<para>&os;'s boot loader is incorrectly recognizing the hard
drive's geometry. This must be manually set within
&man.fdisk.8; when creating or modifying &os;'s
slice.</para>
<para>The correct drive geometry values can be found within
the machine's BIOS. Look for the number of cylinders, heads
and sectors for the particular drive.</para>
<para>Within &man.sysinstall.8;'s fdisk, hit
<keycap>G</keycap> to set the drive geometry.</para>
<para>A dialog will pop up requesting the number of cylinders,
heads and sectors. Type the numbers found from the BIOS
separated by forward slashes. For example, values of 5000
cylinders, 250 heads, and 60 sectors would be entered as
<userinput>5000/250/60</userinput>.</para>
<para>Press <keycap>Enter</keycap> to set the values, and hit
<keycap>W</keycap> to write the new partition table to the
drive.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="bootmanager-restore">
<para>Another operating system destroyed my Boot Manager. How