From owner-freebsd-bugs Sat Dec 12 17:07:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21126 for freebsd-bugs-outgoing; Sat, 12 Dec 1998 17:07:24 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21116; Sat, 12 Dec 1998 17:07:22 -0800 (PST) (envelope-from dillon@FreeBSD.org) From: Matt Dillon Received: (from dillon@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id RAA01278; Sat, 12 Dec 1998 17:07:22 -0800 (PST) Date: Sat, 12 Dec 1998 17:07:22 -0800 (PST) Message-Id: <199812130107.RAA01278@freefall.freebsd.org> To: jin@iss-p5.lbl.gov, dillon@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/7614 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: disklabel fails to write labal on scsi disk State-Changed-From-To: open-closed State-Changed-By: dillon State-Changed-When: Sat Dec 12 17:03:12 PST 1998 State-Changed-Why: I'm pretty sure this PR can be closed, though I will add another note: sometimes there will be data on the disk that causes disklabel to barf, even when you are trying to install a new label. When this happens to me I clear out the first 64K or so worth of the partition with dd and then install a complete new label and boot program. If you do this, however, remember that using dd to clear the label will also clear the boot blocks so always install new boot blocks :-) e.g. dd if=/dev/zero of=THEPARTITION bs=64k count=1 (this will 'destroy' the disk, after which you can install a new label & new boot blocks with disklabel) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message