Date: Mon, 9 Aug 2004 03:47:32 -0400 From: Allan Fields <bsd@afields.ca> To: Stijn Hoop <stijn@win.tue.nl> Cc: freebsd-current@freebsd.org Subject: Re: slice weirdness Message-ID: <20040809074732.GA3155@afields.ca> In-Reply-To: <20040808211337.GB91609@pcwin002.win.tue.nl> References: <20040808211337.GB91609@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Aug 08, 2004 at 11:13:37PM +0200, Stijn Hoop wrote:
> Hi,
>=20
> while trying to migrate my FreeBSD -CURRENT partition to another disk, I =
keep
> running into a slice weirdness issue which makes the kernel unable to find
> it's root fs. It seems that something about the partition table is fishy =
such
> that GEOM doesn't find both slices:
Which kernel: the one from your existing install, the install kernel
(booting off CD), a new kernel?
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.
> 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.
Out of curiosity, did you disklabel the second slice anew or just
copy/dd existing slice over to new drive?
> I first created ad1s2 by hand using fdisk, but got the exact same result.=
The
But, does a newly created slice/disklabel/root filesystem have the same pro=
blem?
i.e. if you were to go the sysinstall route and do a fresh install
on ad1, exhibit same behaviour?
> 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 insta=
lled
> slice. That boot ends with the kernel unable to find the root file system
> ad1s2a (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. Set=
ting
> them to CHS produced an unbootable Windows so I reverted that. In any case
> I thought that those values were of historical interest only...
>=20
> Any clues?
>=20
> --Stijn
>=20
> PS: I thought that there was a sysctl that showed the GEOM topology in XM=
L;
> however I was unable to find it in sysctl -a. Is it still around?
I believe so, phk recently (few months back) mentioned it's staying in.
> --=20
> The rain it raineth on the just
> And also on the unjust fella,
> But chiefly on the just, because
> The unjust steals the just's umbrella.
--=20
Allan Fields, AFRSL - http://afields.ca
2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541
--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQFBFywT90UNcjm0VUERArQFAJ98ddFS6x5BPBFU+FOcwkPEiol18ACgjYii
LOI8665mDR1xAK9UCi4YdEY=
=pWDF
-----END PGP SIGNATURE-----
--BXVAT5kNtrzKuDFl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040809074732.GA3155>