From owner-freebsd-current  Fri Apr  4 15:49:35 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA11696
          for current-outgoing; Fri, 4 Apr 1997 15:49:35 -0800 (PST)
Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11687
          for <current@freebsd.org>; Fri, 4 Apr 1997 15:49:29 -0800 (PST)
Received: (from helbig@localhost)
	by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id BAA27949;
	Sat, 5 Apr 1997 01:49:17 +0200 (MET DST)
From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
Message-Id: <199704042349.BAA27949@helbig.informatik.ba-stuttgart.de>
Subject: Re: ufs filesystem not available at mount time ...
In-Reply-To: <Pine.BSI.3.94.970404170738.344A-100000@militzer.me.tuns.ca> from Antonio Bemfica at "Apr 4, 97 05:19:14 pm"
To: bemfica@militzer.me.tuns.ca (Antonio Bemfica)
Date: Sat, 5 Apr 1997 01:49:16 +0200 (MET DST)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> A week or so back someone posted a message refering to a problem with
> mount at boot time. The same problem is happening to my -current box after
> a 'make world' (I didn't have a chance of building a new kernel...):
> 
> mount: ufs filesystem is not available
[...]
> is mounted at /mnt2.  Should I mount /dev/rsd0a (my "/" ) onto / or onto
> /mnt, or some such thing? I tried some combinations, but never got access
> to the fixed drive (mount complains it needs a "block device" or something
> like that). 

Well, so give it  a block device, i. e. /dev/sd0a (w/o the "r" for raw device)

You have to specify the raw-device to all programs that want a disk device.
(like newfs, disklabel ...)
With one exception: mount. 

Wolfgang