From owner-freebsd-questions Sat Jun 14 23:19:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28663 for questions-outgoing; Sat, 14 Jun 1997 23:19:10 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28658 for ; Sat, 14 Jun 1997 23:19:05 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA00971; Sun, 15 Jun 1997 09:15:15 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma000961; Sun Jun 15 09:14:59 1997 Message-ID: <33A3880A.7722@barcode.co.il> Date: Sun, 15 Jun 1997 09:13:30 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: Gerard Giamberdine CC: freebsd-questions@FreeBSD.ORG Subject: Re: Can't find kernel after partition changes References: <199706141658.KAA27659@flatland.dimensional.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gerard Giamberdine wrote: > > Hello.... > > When I installed freebsd I created a 70M dos partition from which to > install. I've just tried to change it over to freebsd, hoping that I > could mount it as /usr2 or something (is it possible to 'tack' it on to my > existing /usr?). I used sysinstall/configure to delete the dos partition, > create a freebsd partition, and label it (the dos/now freebsd partition > is wd0s1 and the old freebsd is wd0s2). Now at the boot prompt it says > it can't find the kernel. I can access all the original freebsd file > systems using the fixit disk so I know I didn't wipe them out. Does anyone > know what I need to do to get the booter to see the kernel (reconfigure > /dev, rebuild kernel, ...?). > > Thanks for your help, > Gerard Giamberdine. You must remove your newly created FreeBSD slice :-(. What happens is that the boot code always searches the *first* FreeBSD partition on the disk for the kernel. Since you've created a fresh new FreeBSD partition in front of your old one, that's where the boot code is looking for the kenel now. In any case, having two FreeBSD slices on a single disk is possible but difficult. The only other thing you could do is switch the roles of the root partition (i.e. have a root partition on the new slice and use what used to be your root partition for some other purpose). Nadav