From owner-freebsd-questions Thu May 14 13:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09121 for freebsd-questions-outgoing; Thu, 14 May 1998 13:52:19 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from panix2.panix.com (4K0W0GwpNJqlm5W84gy+XZz63G05HhSP@panix2.panix.com [166.84.1.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09116 for ; Thu, 14 May 1998 13:52:14 -0700 (PDT) (envelope-from lsmarso@panix.com) Received: (from lsmarso@localhost) by panix2.panix.com (8.8.5/8.8.8/PanixU1.4) id QAA26873; Thu, 14 May 1998 16:52:11 -0400 (EDT) Message-ID: <19980514165210.33511@panix.com> Date: Thu, 14 May 1998 16:52:10 -0400 From: Larry Marso To: questions@FreeBSD.ORG Subject: bad block scan without reformating? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The FreeBSD installation procedure permits you to conduct a bad block scan on an existing FreeBSD partition, and to download the OS into existing slices mounted as /, /var, /usr, etc. If you don't create new file systems on these slices, but rely on newfs executed *before* the bad block scan, do you risk compromising the integrity of the slice? I fell into this trap when I reinstalled (rather than upgrading) on top of an existing installation. I've been suffering from unexplained lock-ups and rebooting. I'm wondering if this is the result of the bad block scan (which did detect bad sectors) messing up the partition file systems. Should the installation procedure compel making new file systems after a bad block scan? lsmarso@panix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message