From owner-freebsd-questions  Wed Sep 20 21:12:17 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA18617
          for questions-outgoing; Wed, 20 Sep 1995 21:12:17 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA18598
          for <freebsd-questions@freebsd.org>; Wed, 20 Sep 1995 21:12:07 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id VAA24189; Wed, 20 Sep 1995 21:10:51 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id VAA00164; Wed, 20 Sep 1995 21:13:14 -0700
Message-Id: <199509210413.VAA00164@corbin.Root.COM>
To: Brian Litzinger <brian@mediacity.com>
cc: freebsd-questions@freebsd.org
Subject: Re: disklabel -B and me not getting along 
In-reply-to: Your message of "Wed, 20 Sep 95 20:39:12 PDT."
             <199509210339.UAA22061@MediaCity.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 20 Sep 1995 21:13:14 -0700
Sender: owner-questions@freebsd.org
Precedence: bulk

>I'm issuing the command
>
>    disklabel -B -b ./boot1 -s ./boot2 sd0
>
>with the FORCE_COMCONSOLE compiled version of the boot code.
>
>And getting the result:
>
>Warning, revolutions/minute 0
>super block size 0 
>
>and it seems the data isn't being written to the drive, as the system
>continues to boot with the factory boot programs.

   Right - this was a "known" problem awhile back. Basically, you'll need to
use the '-e' switch and then edit this to correct the 'rpm' and 'interleave'.
After this has been done and the label updated, you should be able to write
out the new bootblocks as you tried to do above.
   This was fixed a few months ago.

-DG