From owner-freebsd-doc Wed Oct 31 11: 0: 9 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 17F0237B403 for ; Wed, 31 Oct 2001 11:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9VJ02k56481; Wed, 31 Oct 2001 11:00:02 -0800 (PST) (envelope-from gnats) Date: Wed, 31 Oct 2001 11:00:02 -0800 (PST) Message-Id: <200110311900.f9VJ02k56481@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Michael Lucas Subject: re: docs/19010: Bad144 obsoletion by 4.0 is undocumented; fix is undocumented Reply-To: Michael Lucas Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/19010; it has been noted by GNATS. From: Michael Lucas 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.] + + + + I've just upgraded from 3.X to 4.X, and my first boot + failed with bad sector table not + supported + + + + FreeBSD 3.X and earlier supported + bad144, which automatically remapped + bad blocks. FreeBSD 4.X and later does not support this, + as modern IDE drives include this functionality. See + this + question for more information. + + 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. + + + + + + How do I tell if my drive has + bad144 on it before I try to upgrade to + FreeBSD 4.0 and it fails? + + + + Use &man.disklabel.8 for this. disklabel -r + wd0 (replace wd0 with your drive device) will + give you the contents of your disk label. Look for a + flags field. If you see + flags: badsect, this drive is using + bad144. For example, the following drive has + bad144 enabled.: + + + # /dev/rwd0c: + type: ESDI + disk: wd0s1 + label: + flags: badsect + bytes/sector: 512 + sectors/track: 63 + + + + + + + How do I remove bad144 from my + pre-4.X system so I can upgrade safely? + + + + Use disklabel -e -rwd0 to edit the + disklabel in place. Just remove the word + badsect 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. + + + We still recommend you purchase a new disk if you have + a large number of bad blocks. + + + --bg08WKrSYDhXBjb5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message