Date: Wed, 31 Oct 2001 11:00:02 -0800 (PST) From: Michael Lucas <mwlucas@blackhelicopters.org> To: freebsd-doc@freebsd.org Subject: re: docs/19010: Bad144 obsoletion by 4.0 is undocumented; fix is undocumented Message-ID: <200110311900.f9VJ02k56481@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR docs/19010; it has been noted by GNATS. 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-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110311900.f9VJ02k56481>