"I just upgraded from 3.x to 4.x" > /dev/null
This commit is contained in:
parent
c59f6e783d
commit
5d0743fb63
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=24546
1 changed files with 0 additions and 67 deletions
|
@ -1554,73 +1554,6 @@ File: +DESC (ignored)</screen>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="bad144-3x-4x">
|
||||
<para>I have just upgraded from 3.X to 4.X, and my first boot
|
||||
failed with <errorname>bad sector table not
|
||||
supported</errorname></para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>FreeBSD 3.X and earlier supported
|
||||
<command>bad144</command>, which automatically remapped
|
||||
bad blocks. FreeBSD 4.X and later do not support this, as
|
||||
modern IDE drives include this functionality. See <link
|
||||
linkend="install-bad-blocks">this question</link> 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 a drive has <command>bad144</command>
|
||||
information 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
|
||||
<replaceable>drive device</replaceable></command> 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>
|
||||
|
||||
<screen>&prompt.root; <userinput>disklabel -r wd0</userinput>
|
||||
# /dev/rwd0c:
|
||||
type: ESDI
|
||||
disk: wd0s1
|
||||
label:
|
||||
flags: badsect
|
||||
bytes/sector: 512
|
||||
sectors/track: 63</screen>
|
||||
</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>
|
||||
|
||||
<qandaentry>
|
||||
<question id="boot-floppy-strangeness">
|
||||
<para>Strange things happen when I boot the install floppy!
|
||||
|
|
Loading…
Reference in a new issue