From owner-freebsd-stable Wed Nov 22 21:26:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wilson.acpub.duke.edu (wilson.acpub.duke.edu [152.3.233.69]) by hub.freebsd.org (Postfix) with ESMTP id E038637B4CF for ; Wed, 22 Nov 2000 21:26:32 -0800 (PST) Received: from bobzilla.adsl.duke.edu (bobzilla.adsl.duke.edu [152.16.67.15]) by wilson.acpub.duke.edu (8.9.3/8.9.3/Duke-5.0.0) with ESMTP id AAA17212; Thu, 23 Nov 2000 00:26:31 -0500 (EST) Received: (from sto@localhost) by bobzilla.adsl.duke.edu (8.11.1/8.11.1) id eAN5QU311650 for freebsd-stable@FreeBSD.ORG; Thu, 23 Nov 2000 00:26:30 -0500 (EST) (envelope-from sto) Date: Thu, 23 Nov 2000 00:26:30 -0500 From: "Sean O'Connell" To: FreeBSD stable Subject: Re: 4.2-RELEASE + SCSI device unable to mount file system Message-ID: <20001123002630.B11598@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , FreeBSD stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Organization: House of Schmutzli X-Kitties: Bitty Maya CJ Keisha Jacob Hopey X-Hound: Bob X-OS-of-Choice: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frederic Nguyen stated: : What should I do then? How to remove that badsector table so that system : may boot properly? : : > da0: bad sector table not supported : > > da0s1: bad sector table not supported : > : >Why do you have a badsector table on a SCSI disk?? bad144 was canned quite : >some time ago, I think that might be causing this. Badsect tables are for : >old ESDI etc drives. Never been for SCSI I think it is a simply a disklabel flag. There was a thread about this a while back. I vaguely remember that simply doing disklabel -e da0s1 and removing the badsect (or whatever) from the line flags: might fix it. This is not first hand, so no promises! S -- 1--------01---------01--------01--------01--------01--------01--------0 Sean O'Connell sean@stat.Duke.EDU To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message