From owner-freebsd-hackers  Thu Aug 21 07:58:56 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA24809
          for hackers-outgoing; Thu, 21 Aug 1997 07:58:56 -0700 (PDT)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA24804
          for <hackers@freebsd.org>; Thu, 21 Aug 1997 07:58:52 -0700 (PDT)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Thu, 21 Aug 1997 10:58:21 -0400 (EDT)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA13575; Thu, 21 Aug 97 10:58:20 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id KAA22414; Thu, 21 Aug 1997 10:55:27 -0400
Message-Id: <19970821105527.53931@ct.picker.com>
Date: Thu, 21 Aug 1997 10:55:27 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: hackers@freebsd.org
Subject: ? "sysinstall" errors labeling a new disk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

     I'm trying to do something I think should be very simple -- run
sysinstall on an installed system to allocate a sizable free slice of disk
to FreeBSD.  This will be "wd1s2", with the intent of having:

      wd1s2b: 128Meg   - SWAP 
      wd1s2e: the rest - UFS @ /share3

FDISKING in sysinstall worked flawlessly:

      Custom-Partition-wd1-Create-<CR>-<CR>-Write-Yes

Then, I got the new slice layed out in the disklabel editor:

      Label-Create-128M-SWAP-Create-<CR>-FS-/share3

So far, looks good.  

                                 ---

BUT I try to "Write" and I get:

   >> "Unable to add /dev/wd1s2b as a swap device: Device not configured" <<

ktracing sysinstall, I see it's trying to:

      swapon( "/dev/wd1s2b" )

I'm wonderering why its trying to do that--I can do it later.  Anway, going
on it then immediately forks off:

      newfs -b 8192 -f 1024 /dev/rwd1s2e

It appears it attempted no "disklabel" before this, so newfs fails.  I
guess sysinstall doesn't check the newfs command for failure since it then
goes on and tries to mount the partition:

      mount( ..., "/share3", ..., "/dev/wd1s2e" )

which returns Invalid argument yielding the:

   >> "Error mounting /dev/wd1s2e on /share3 : Invalid argument" << 

dialog.  

If I try the "newfs -b 8192 -f 1024 /dev/rwd1s2e" by hand in the shell, I 
get:

      "newfs: /dev/rwd1s2e: `e' partition is unavailable"

The /dev/rwd1s2e device file does exist, and "disklabel wd1s2" in the shell
confirms the slice was never disklabeled (all blocks are in "c").


Shouldn't sysinstall be doing a disklabel?  Any idea what I'm doing wrong
or if this is a sysinstall bug?  

I'd welcome any tips, suggestions, and even enlightening flames.  Before I
resort to disklabeling via cmd-line, I'd like to make sure that sysinstall
isn't an option -- it's definitely the easier and safer way to go if it can
work for folks that don't

Thanks,

Randall