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

Whitespace cleanup from last commit.

Browse source 
No content changes.
This commit is contained in:
Michael Lucas 2005-05-12 14:24:10 +00:00
parent 78104eb5d4
commit 4c6b10478c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24536
1 changed files with 30 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

56
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -1958,41 +1958,44 @@ sectors/track: 63</screen>
</question>
<answer>
<para>This error comes from confusion between the boot block's
and the kernel's understanding of the disk devices. The error
usually manifests on two-disk IDE systems, with the hard disks
arranged as the master or single device on separate IDE
controllers, with FreeBSD installed on the secondary IDE
controller. The boot blocks think the system is installed on
ad0 (the second BIOS disk) while the kernel assigns the first
disk on the secondary controller device, ad2. After the device
probing, the kernel tries to mount what the boot blocks think
is the boot disk, ad0, while it is really ad2, and
<para>This error comes from confusion between the boot
block's and the kernel's understanding of the disk
devices. The error usually manifests on two-disk IDE
systems, with the hard disks arranged as the master or
single device on separate IDE controllers, with FreeBSD
installed on the secondary IDE controller. The boot blocks
think the system is installed on ad0 (the second BIOS
disk) while the kernel assigns the first disk on the
secondary controller device, ad2. After the device
probing, the kernel tries to mount what the boot blocks
think is the boot disk, ad0, while it is really ad2, and
fails.</para>
<para>To fix the problem, do one of the following:</para>
<orderedlist>
<listitem>
<para>Reboot the system and hit
<keycap>Enter</keycap> at the <literal>Booting kernel
in 10 seconds; hit [Enter] to interrupt</literal> prompt.
This will drop you into the boot loader.</para>
<para>Reboot the system and hit <keycap>Enter</keycap>
at the <literal>Booting kernel in 10 seconds; hit
[Enter] to interrupt</literal> prompt. This will
drop you into the boot loader.</para>
<para>Then type
<literal>
set root_disk_unit="<replaceable>disk_number</replaceable>"
set
root_disk_unit="<replaceable>disk_number</replaceable>"
</literal>. <replaceable>disk_number</replaceable>
will be <literal>0</literal> if FreeBSD is installed on
the master drive on the first IDE controller,
<literal>1</literal> if it is installed on the slave on
the first IDE controller, <literal>2</literal> if it is
installed on the master of the second IDE controller, and
<literal>3</literal> if it is installed on the slave of
the second IDE controller.</para>
will be <literal>0</literal> if FreeBSD is installed
on the master drive on the first IDE controller,
<literal>1</literal> if it is installed on the slave
on the first IDE controller, <literal>2</literal> if
it is installed on the master of the second IDE
controller, and <literal>3</literal> if it is
installed on the slave of the second IDE
controller.</para>
<para>Then type <literal>boot</literal>, and your system
should boot correctly.</para>
<para>Then type <literal>boot</literal>, and your
system should boot correctly.</para>
<para>To make this change permanent (ie so you do not
have to do this every time you reboot or turn on
@ -2003,8 +2006,9 @@ sectors/track: 63</screen>
</listitem>
<listitem>
<para>Move the FreeBSD disk onto the primary IDE controller,
so the hard disks are consecutive.</para>
<para>Move the FreeBSD disk onto the primary IDE
controller, so the hard disks are
consecutive.</para>
</listitem>
</orderedlist>
</answer>