From owner-freebsd-stable Sat Sep 2 6: 2:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by hub.freebsd.org (Postfix) with ESMTP id BE4C837B424 for ; Sat, 2 Sep 2000 06:02:12 -0700 (PDT) Received: from JDBitters@cs.com by imo-d07.mx.aol.com (mail_out_v28.15.) id n.e3.95ba093 (1882); Sat, 2 Sep 2000 09:02:04 -0400 (EDT) From: JDBitters@cs.com Message-ID: Date: Sat, 2 Sep 2000 09:02:04 EDT Subject: 4.1-STABLE BOOT SLICE PROBLEM To: freebsd-stable@freebsd.org Cc: JDBitters@cs.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Unknown sub 30 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently, I copied a 4.1-20000813-STABLE installation to a larger disk. I used /stand/sysinstall to create a "dangerously dedicated" disk and to custom label it. Thereafter, I mounted the new slices on temporary mount points on the old disk and copied the folders and files using Midnight Commander. It all works like a charm with one exception. My problem is that the root "/" partition installed on the "s1e" rather than the "s1a" slice The s1a slice does not exist on this disk. This results in an "invalid partition" message upon boot up, followed by unsuccessful attempts to boot into the nonexistent s1a slice. However, I am able to manually enter the correct slice and boot loader info. I understand that booting into the s1a slice is default behavior. I am tempted to use boot0cfg but am apprehensive because of the "dangerously dedicated" type of installation. Reviewing the boot and boot0cfg manuals has not given me a solution. Any ideas? Thank you! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message