From owner-freebsd-current@FreeBSD.ORG Mon Aug 9 07:52:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3661416A4CE for ; Mon, 9 Aug 2004 07:52:32 +0000 (GMT) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B042143D1D for ; Mon, 9 Aug 2004 07:52:31 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.11/8.12.11) with ESMTP id i797qSjL002627; Mon, 9 Aug 2004 09:52:29 +0200 (CEST) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.11/8.12.11/Submit) id i797qSRu002626; Mon, 9 Aug 2004 09:52:28 +0200 (CEST) (envelope-from stijn) Date: Mon, 9 Aug 2004 09:52:28 +0200 From: Stijn Hoop To: Allan Fields Message-ID: <20040809075228.GC91609@pcwin002.win.tue.nl> References: <20040808211337.GB91609@pcwin002.win.tue.nl> <20040809074732.GA3155@afields.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9Ek0hoCL9XbhcSqy" Content-Disposition: inline In-Reply-To: <20040809074732.GA3155@afields.ca> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! cc: freebsd-current@freebsd.org Subject: Re: slice weirdness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 07:52:32 -0000 --9Ek0hoCL9XbhcSqy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 09, 2004 at 03:47:32AM -0400, Allan Fields wrote: > On Sun, Aug 08, 2004 at 11:13:37PM +0200, Stijn Hoop wrote: > > while trying to migrate my FreeBSD -CURRENT partition to another disk, > > I keep running into a slice weirdness issue which makes the kernel unab= le > > to find it's root fs. It seems that something about the partition table > > is fishy such that GEOM doesn't find both slices: >=20 > Which kernel: the one from your existing install, the install kernel > (booting off CD), a new kernel? The same kernel that boots my current installation; I just did a new 'make install{world,kernel} DESTDIR=3D/mnt/NEW' where /mnt/NEW is the mount= ed /dev/ad2s1a (ie the new slice after just having it partitioned). > I've had some partition/slice issues in the past w/ install CD and > missing device entries with non-standard slice (anything except s1 > entry), can't recall details, but running sysinstall w/ newfs > flag to N creates appropriate entries. Else I've found suitable > device entries elsewhere or make them temporarily with mknod. > Maybe this was only an issue in -stable. I don't know, but obviously I can't mknod / do something about it when the kernel has just been booted. > > So where's my /dev/ad1s2? > >=20 > > The disk layout is ad1s1 is my Windows partition, ad1s2 my targeted new > > partition for the FreeBSD installation currently residing at ad0s1. >=20 > Out of curiosity, did you disklabel the second slice anew or just > copy/dd existing slice over to new drive? I disklabeled anew. > > I first created ad1s2 by hand using fdisk, but got the exact same resul= t. > > But, does a newly created slice/disklabel/root filesystem have the same > problem? > i.e. if you were to go the sysinstall route and do a fresh install > on ad1, exhibit same behaviour? Yes, it does. I didn't use sysinstall but 'make installworld' but either do= ing fdisk / disklabel by hand or by doing it using sysinstall, both methods stop at the same 'cannot find root' prompt when booting off the slice. A reboot into the old install later and my device entry is gone again. > > script above shows the values that I obtained when /sbin/sysinstall > > partitioned the drive. After partitioning the device nodes reappear, and > > I was able to install{kernel,world} with DESTDIR pointing to the newly > > mounted ad1s2, but the device nodes disappear after having booted the > > newly installed slice. That boot ends with the kernel unable to find the > > root file systemad1s2a (which is not strange given the above). > >=20 > > Am I looking at some sort of geometry bug? I've tried setting the BIOS > > geometry settings to LBA (from Auto), that didn't make a difference. > > Setting them to CHS produced an unbootable Windows so I reverted that. > > In any case I thought that those values were of historical interest onl= y... > >=20 > > Any clues? > >=20 > > --Stijn > >=20 > > PS: I thought that there was a sysctl that showed the GEOM topology in = XML; > > however I was unable to find it in sysctl -a. Is it still around? >=20 > I believe so, phk recently (few months back) mentioned it's staying in. Too bad I couldn't find it... Thanks for your reply, --Stijn --=20 Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children the dragons can be killed. -- G.K. Chesterton --9Ek0hoCL9XbhcSqy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBFy08Y3r/tLQmfWcRAsPYAKCmvDsmbNKYjAWgH7Q4/bE/AyIQvACfYBTc haItERFDyLJSrN7OxBKhBr0= =rXLH -----END PGP SIGNATURE----- --9Ek0hoCL9XbhcSqy--