Attachment 9246 Details for Bug 19010 – 19010

19010

19010 (text/plain; charset=us-ascii), 2.68 KB, created by Michael W Lucas on 2001-10-31 18:56:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michael W Lucas

Created: 2001-10-31 18:56:59 UTC

Size: 2.68 KB

patch

obsolete

>*** book.sgml-dist	Wed Oct 31 11:30:49 2001
>--- book.sgml	Wed Oct 31 13:50:57 2001
>***************
>*** 12169,12175 ****
>--- 12169,12246 ----
>            granularity.]</emphasis></para>
>          </answer>
>        </qandaentry>
>+ 
>+       <qandaentry>
>+         <question id="bad144-3x-4x">
>+           <para>I've just upgraded from 3.X to 4.X, and my first boot
>+             failed with <quote>bad sector table not
>+             supported</quote></para>
>+         </question>
>+ 
>+         <answer>
>+           <para>FreeBSD 3.X and earlier supported
>+             <command>bad144</command>, which automatically remapped
>+             bad blocks.  FreeBSD 4.X and later does not support this,
>+             as modern IDE drives include this functionality.  See
>+             <ulink URL="../install.html#install-bad-blocks">this
>+             question</ulink> for more information.</para>
>+ 
>+   	  <para>To fix this after an upgrade, you need to physically
>+ 	    place the drive in a working system and use
>+ 	    &man.disklabel.8 as discussed in the following
>+ 	    questions.</para>
>+         </answer>
>+       </qandaentry>
>+ 
>+       <qandaentry>
>+         <question id="find-bad144">
>+ 	  <para>How do I tell if my drive has
>+ 	    <command>bad144</command> on it before I try to upgrade to
>+ 	    FreeBSD 4.0 and it fails?</para>
>+ 	</question>
>+ 
>+ 	<answer>
>+ 	  <para>Use &man.disklabel.8 for this.  <command>disklabel -r
>+ 	    wd0</command> (replace wd0 with your drive device) will
>+ 	    give you the contents of your disk label.  Look for a
>+ 	    <literal>flags</literal> field.  If you see
>+ 	    <literal>flags: badsect</literal>, this drive is using
>+ 	    bad144.  For example, the following drive has
>+ 	    <command>bad144</command> enabled.:</para>
>+ 
>+ 	  <programlisting>
>+ 	    # /dev/rwd0c:
>+ 	    type: ESDI
>+ 	    disk: wd0s1
>+ 	    label: 
>+ 	    flags: badsect
>+ 	    bytes/sector: 512
>+ 	    sectors/track: 63
>+ 	  </programlisting>
>+ 	</answer>
>+       </qandaentry>
>+ 
>+       <qandaentry>
>+         <question id="disable-bad144">
>+ 	  <para>How do I remove <command>bad144</command> from my
>+ 	  pre-4.X system so I can upgrade safely?</para>
>+ 	</question>
>+ 
>+ 	<answer>
>+ 	  <para>Use <command>disklabel -e -rwd0 </command> to edit the
>+ 	    disklabel in place.  Just remove the word
>+ 	    <literal>badsect</literal> from the flags field, save, and
>+ 	    exit.  The bad144 file will still take up some space on
>+ 	    your drive, but the disk itself will be usable.
>+ 	  </para>
>+ 
>+ 	  <para>We still recommend you purchase a new disk if you have
>+ 	    a large number of bad blocks.</para>
>+ 	</answer>
>+       </qandaentry>
>+ 
>      </qandaset>
>    </chapter>
>  
>    <chapter id="acknowledgments">

Actions: View

Attachments on bug 19010: 9246