From bharat@menalto.com  Mon Jun  5 00:31:03 2000
Return-Path: <bharat@menalto.com>
Received: from menalto.com (www.menalto.com [198.144.206.35])
	by hub.freebsd.org (Postfix) with ESMTP id 7F76137B7E7
	for <FreeBSD-gnats-submit@freebsd.org>; Mon,  5 Jun 2000 00:31:01 -0700 (PDT)
	(envelope-from bharat@menalto.com)
Received: (from bharat@localhost)
	by menalto.com (8.10.0/8.10.0) id e557V5u21760;
	Mon, 5 Jun 2000 00:31:05 -0700 (PDT)
Message-Id: <200006050731.e557V5u21760@menalto.com>
Date: Mon, 5 Jun 2000 00:31:05 -0700 (PDT)
From: bharat@menalto.com
Reply-To: bharat@menalto.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: Bad144 obsoletion by 4.0 is undocumented; fix is undocumented
X-Send-Pr-Version: 3.2

>Number:         19010
>Category:       docs
>Synopsis:       Bad144 obsoletion by 4.0 is undocumented; fix is undocumented
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 05 00:40:01 PDT 2000
>Closed-Date:    Wed Oct 31 12:02:34 PST 2001
>Last-Modified:  Wed Oct 31 12:03:32 PST 2001
>Originator:     Bharat Mediratta
>Release:        FreeBSD 4.0-STABLE i386
>Organization:
Menalto.com
>Environment:

	3.4-STABLE i386, 4.0-RELEASE/4.0-STABLE i386

>Description:

When I installed FreeBSD 3.4-STABLE on my machine there was no 
indication that bad144 (bad sector forwarding) was not a good idea.
Support for bad144 went away in 4.0, so if you are using it in 3.4 
this will get in the way of upgrading.  After you reinstall the
kernel and reboot it will not let you remounte your root partition
and will give you an error message like this:

	wd0: bad sector table not supported
	wd0s1: bad sector table not supported

>How-To-Repeat:

Turn on bad144 at install time of 3.4-STABLE or 3.4-RELEASE, then
attempt to source upgrade the machine to any 4.0 branch.

>Fix:

Q:	How do I tell if my drive has bad144 on it, BEFORE I
	try to upgrade to FreeBSD 4.0 and have it fail on me?

A:	Use the disklabel utility.  'disklabel -r wd0' (replace
	wd0 with your drive device) will give you the contents of
	your disk label.  For example:

		# /dev/rwd0c:
		type: ESDI
		disk: wd0s1
		label: 
		flags: badsect		<--- NOTE!
		bytes/sector: 512
		sectors/track: 63

Q:	How do I remove bad144?

A:	The easiest way to do this is to use disklabel.  You can
	dump the current label out to disk and then reload it, or
	you can just edit it in place with 'disklabel -e -r wd0'.
	All you have to do is remove 'badsect' from the flags line
	and you're all set.  This won't affect any of your data.
	bad144 is probably still taking up some space on your disk	
	but it is no longer in effect.




>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: murray 
State-Changed-When: Mon Sep 3 17:25:14 PDT 2001 
State-Changed-Why:  
This looks like FAQ material.  Is there any reason why this shouldn't 
go into the FAQ? 


http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19010 

From: Michael Lucas <mwlucas@blackhelicopters.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: re: docs/19010: Bad144 obsoletion by 4.0 is undocumented; fix is undocumented
Date: Wed, 31 Oct 2001 13:56:59 -0500

 --bg08WKrSYDhXBjb5
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 Here's a patch for this PR.
 
 -- 
 Michael Lucas
 mwlucas@blackhelicopters.org
 http://www.blackhelicopters.org/~mwlucas/
 Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons
 
 --bg08WKrSYDhXBjb5
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename=19010
 
 *** 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">
 
 --bg08WKrSYDhXBjb5--

From: Udo Erdelhoff <ue@nathan.ruhr.de>
To: freebsd-doc@freebsd.org
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: docs/19010: Bad144 obsoletion by 4.0 is undocumented; fix is undocumented
Date: Wed, 31 Oct 2001 20:28:19 +0100

 --TB36FDmn/VVEgNH/
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Oct 31, 2001 at 11:00:02AM -0800, Michael Lucas wrote:
 >  Here's a patch for this PR.
 
 [3 new entries snipped]
 
 The content looks good, I'll add it and fix the markup while I'm there.
 
 /s/Udo
 --=20
 Cocaine is nature's way of telling you you have too much money.
 
 --TB36FDmn/VVEgNH/
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iQCVAwUBO+BQ00Poh1XnT6hxAQE4xAQAkQ4C6xC1uvxC1N7eZcaE7NwckOKsVgDy
 HFEUXGINgKsUa33YWT5pHuKe+hU9UNDukBzOEAp8ZwzlM5TV6Kwl8UGvCTNv64Sr
 j3p8wbFI5Zs2LANYhjUKuSr6v9NFPlJ8rkzV60QeKbHx7CSNIcAmmT0Iu55cH1gu
 mVl6roqlNnE=
 =by0w
 -----END PGP SIGNATURE-----
 
 --TB36FDmn/VVEgNH/--
State-Changed-From-To: analyzed->closed 
State-Changed-By: ue 
State-Changed-When: Wed Oct 31 12:02:34 PST 2001 
State-Changed-Why:  
Fixed in revision 1.278 of the FAQ. Thanks for your feedback and 
submissions. 


http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19010 
>Unformatted:
