From owner-freebsd-questions@FreeBSD.ORG  Fri Feb  5 20:22:51 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E07A2106568F
	for <freebsd-questions@freebsd.org>;
	Fri,  5 Feb 2010 20:22:51 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.103.93])
	by mx1.freebsd.org (Postfix) with ESMTP id B66D18FC1C
	for <freebsd-questions@freebsd.org>;
	Fri,  5 Feb 2010 20:22:51 +0000 (UTC)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.14.2/8.13.8) with ESMTP id o15KMRg3037195
	for <freebsd-questions@freebsd.org>;
	Fri, 5 Feb 2010 14:22:38 -0600 (CST)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <201002052022.o15KMRg3037195@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37191.1265401347.1@dc.cis.okstate.edu>
Date: Fri, 05 Feb 2010 14:22:27 -0600
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: sysinstall and mfs I'm out of Ideas.
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2010 20:22:52 -0000

	After about a week of trying, I don't think sysinstall
will  install FreeBSD when used with mfsbsd. I launched mfsbsd
from a CDROM and it works fine. I also used dd to feed the
mfsboot.img file to the boot sector on the system's hard drive
and that also worked fine. mfsbsd doesn't appear to be the
problem.  Everything but sysinstall works as one would expect.

	Sysinstall may either be confused because the host is in
multi-user mode or it may be trying to protect what it thinks is
the system's boot drive from damage. It absolutely will not
write one byte to /dev/ad0 partitions even though it sees the
drive. the rest of sysinstall appears to be normal except for
its fear about writing to /dev/ad0sx.

	I will be very happy to be proven wrong, but I don't
know what else to do to sysinstall to get it to use that drive.

	It does work from the local console in single-user mode
from the CDROM. I greatly appreciate all the help and welcome
any new ideas, but it appears to be back to the drawing board
for remotely-done upgrades.

Martin McCormick