From owner-freebsd-bugs Thu Jul 20 9:20:13 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7A1CD37B702 for ; Thu, 20 Jul 2000 09:20:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA66438; Thu, 20 Jul 2000 09:20:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 20 Jul 2000 09:20:07 -0700 (PDT) Message-Id: <200007201620.JAA66438@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Michael R. Wayne" Subject: Re: conf/16948: Sysinstall/disklabel: bad partition table when single->multiple slices Reply-To: "Michael R. Wayne" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/16948; it has been noted by GNATS. From: "Michael R. Wayne" To: freebsd-gnats-submit@FreeBSD.org Cc: jkh@FreeBSD.org, Sheldon Hearn Subject: Re: conf/16948: Sysinstall/disklabel: bad partition table when single->multiple slices Date: Thu, 20 Jul 2000 12:10:32 -0400 This problem is still present in 4.0 RELEASE. Unfortunately, I did not re-examine the open PR database prior to my last FreeBSD conversion so I got bit by it again today. So I have a completely installed and configured system ready to go, that will not boot. Is there any possibility of getting this into 4.1 RC? It should be a fairly simple fix to either zero the prior contents of blocks 1 & 2 on the disk before writing the partition table and boot blocks or to simply zero all contents of the old partition table when writing a non-dangerously-dedicated one. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message