svn commit: r40908 - head/en_US.ISO8859-1/books/faq

[Eitan Adler]

Author: eadler
Date: Fri Feb  8 00:22:40 2013
New Revision: 40908
URL: http://svnweb.freebsd.org/changeset/doc/40908

Log:
  Remove out of date question
  
  Noted by:	scottl
  Approved by:	bcr (mentor, implicit)

Modified:
  head/en_US.ISO8859-1/books/faq/book.xml

Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml	Thu Feb  7 18:02:01 2013	(r40907)
+++ head/en_US.ISO8859-1/books/faq/book.xml	Fri Feb  8 00:22:40 2013	(r40908)
@@ -1421,66 +1421,6 @@
       </qandaentry>
 
       <qandaentry>
-	<question id="panic-on-install-reboot">
-	  <para>Why do I get a <errorname>panic: can't mount
-	      root</errorname> error when rebooting the system after
-	    installation?</para>
-	</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 &os; installed on the
-	    secondary IDE controller.  The boot blocks think the system
-	    is installed on <devicename>ad0</devicename> (the second
-	    BIOS disk) while the kernel assigns the first disk on the
-	    secondary controller device, <devicename>ad2</devicename>.
-	    After the device probing, the kernel tries to mount what the
-	    boot blocks think is the boot disk,
-	    <devicename>ad0</devicename>, while it is really
-	    <devicename>ad2</devicename>, 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>Then type
-		<userinput>set root_disk_unit="<replaceable>disk_number</replaceable>"</userinput>.
-		<replaceable>disk_number</replaceable> will be
-		<literal>0</literal> if &os; 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 <userinput>boot</userinput>, and your
-		system should boot correctly.</para>
-
-	      <para>To make this change permanent (i.e, so you do not
-		have to do this every time you reboot or turn on your
-		&os; machine), put the line
-		<userinput>root_disk_unit="<replaceable>disk_number</replaceable>"</userinput>
-		in <filename>/boot/loader.conf.local</filename>.</para>
-	    </listitem>
-
-	    <listitem>
-	      <para>Move the &os; disk onto the primary IDE
-		controller, so the hard disks are consecutive.</para>
-	    </listitem>
-	  </orderedlist>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="memory-limits">
 	  <para>What are the limits for memory?</para>
 	</question>