From owner-freebsd-current  Sun Mar 26 21:38:35 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA04629 for current-outgoing; Sun, 26 Mar 1995 21:38:35 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA04623 for <freebsd-current@freefall.cdrom.com>; Sun, 26 Mar 1995 21:38:20 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA08650; Mon, 27 Mar 1995 15:36:47 +1000
Date: Mon, 27 Mar 1995 15:36:47 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503270536.PAA08650@godzilla.zeta.org.au>
To: jc@irbs.com, rgrimes@gndrsh.aac.dev.com
Subject: Re: Slice errors
Cc: freebsd-current@freefall.cdrom.com
Sender: current-owner@FreeBSD.org
Precedence: bulk

>> The data for partition 0 is:
>> <UNUSED>
>> The data for partition 1 is:
>> <UNUSED>
>> The data for partition 2 is:
>> <UNUSED>
>> The data for partition 3 is:
>> sysid 165,(FreeBSD/NetBSD/386BSD)
>>     start 0, size 50000 (24 Meg), flag 80
>> 	beg: cyl 0/ sector 1/ head 0;
>> 	end: cyl 1023/ sector 63/ head 255

>Use fdisk -u to correct the partition table so that size==size of
>your BSD c or d partition and things should be fine.  What you see
>above is the bogus partition table that gets installed if you install
>new boot blocks.

This advice no longer applies.  The bogus partition table is specially
handled to make it work.  Changing it risks introducing bugs and
changes will be blown away by new boot blocks.

Bruce