From owner-freebsd-questions@FreeBSD.ORG Sat Jul 10 00:07:22 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CBEF16A4CE for ; Sat, 10 Jul 2004 00:07:22 +0000 (GMT) Received: from mail.cableone.net (scanmail1.cableone.net [24.116.0.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47DE843D1F for ; Sat, 10 Jul 2004 00:07:22 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.191]) by smail1.cableone.net (SurgeMail 1.9b) with ESMTP id 8170097 for multiple; Fri, 09 Jul 2004 16:57:41 -0700 Date: Fri, 9 Jul 2004 19:07:15 -0500 From: Vulpes Velox To: "dave" Message-Id: <20040709190715.199fa2c3@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <000501c465e8$98fa6020$0200a8c0@satellite> References: <000501c465e8$98fa6020$0200a8c0@satellite> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: freebsd-questions@freebsd.org Subject: Re: clearing a drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 00:07:22 -0000 On Fri, 9 Jul 2004 15:11:54 -0400 "dave" wrote: > Hi, > I've got a corrupted drive which i am unable now to clear. > Whenever i > try to fdisk it then relabel it i get an error that partition c does > not cover the entire disk and that this might interfere with system > utilities. I've tried: > dd if=/dev/zero of=/dev/ad1 bs=512 count=1 > and various combinations thereof, without success. Normally running > sysinstall will work, but in this case it is saying an error > occurred writing partition information to drive ad1, and not > allowing me to proceed. > This is on a 5.2.1 box. No clue, but try the current mailing list and archive. Sounds like a hardware problem to me. Bad drive or the like. Still possible a bug in 5.2.1.