Date: Wed, 16 Dec 2009 09:29:00 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: sthaug@nethelp.no Cc: freebsd-stable@freebsd.org Subject: Re: update to 8.0-RELEASE --> partition gone Message-ID: <55FA4159-2AEE-4E2A-BAE9-E9699C6C7537@mac.com> In-Reply-To: <20091216.113300.74685382.sthaug@nethelp.no> References: <200912151720.37709.freebsd@insightbb.com> <20091216000803.GA39686@osiris.mauzo.dyndns.org> <7BA0C6CC-A1D9-49C2-942D-D46C19E9B3CB@mac.com> <20091216.113300.74685382.sthaug@nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 16, 2009, at 2:33 AM, sthaug@nethelp.no wrote:
>> If you installed "dangerously dedicated" and ended up
>> with ad0s1a (note the "s1"), then you have an invalid
>> partitioning and FreeBSD 8.x will not give you what
>> you've been getting on FreeBSD 7.x. Most of the time
>> you only need to wipe out the second sector on the
>> disk to clean it up and have FreeBSD 8.x also give
>> you ad0s1a.
>
> So what's an easy recipe we can run on 7.x hosts to see whether we
> would have problems with 8.x?
If
1. fdisk ${D} shows FreeBSD slices, and
2. your mount points are within these slices (i.e your device name
has a prefix of ${D}s1, ${D}s2, ${D}s3, etc *OR* they have a
prefix of ${D}cs1 ${D}cs2 ${D}cs3, etc), and
3. bsdlabel ${D} shows that there's a (possibly empty) BSD disklabel
then you have an invalidly created danerously dedicated disk.
You can wipe out the second sector on the disk to clear the bogus
BSD disklabel.
The most important thing to look at is how you currently mount.
If fdisk ${D} and bsdlabel ${D} show valid information and you
mount from ${D}a, ${D}d, etc -- then your disk is not necessarily
invalid in the same sense that having a PMBR with slices in front
of a GPT is not considered invalid.
FYI,
--
Marcel Moolenaar
xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55FA4159-2AEE-4E2A-BAE9-E9699C6C7537>