From owner-freebsd-questions@FreeBSD.ORG Mon Feb 16 02:05:54 2009 Return-Path: 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 EC753106566B for ; Mon, 16 Feb 2009 02:05:54 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by mx1.freebsd.org (Postfix) with ESMTP id BC7B28FC0C for ; Mon, 16 Feb 2009 02:05:54 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from localhost.localdomain (unknown [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 99A239AA45 for ; Sun, 15 Feb 2009 21:05:53 -0500 (EST) Received: from lukas.is-a-geek.org (unknown [71.113.98.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 001979AA44 for ; Sun, 15 Feb 2009 21:05:52 -0500 (EST) Date: Sun, 15 Feb 2009 18:05:45 -0800 (PST) From: Luke Dean X-X-Sender: lukas@border.lukas.is-a-geek.org To: freebsd-questions@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Pobox-Relay-ID: 57375428-FBCE-11DD-8291-0433C92D7133-96347044!a-sasl-fastnet.pobox.com Subject: "boot0cfg: read /dev/ad1: Input/output error" using nanobsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 02:05:55 -0000 I'm running FreeBSD 7.0 on a soekris 4801 with an image built by nanobsd. It's a small piece of headless hardware that boots from a compact flash drive - no moving parts. I wanted to update the operating system to 7.1 and install some more packages on it, so I built a new image with nanobsd and uploaded it to the second partition using nanobsd's updatep2 tool. The new image mounts fine, but the last line of updatep2, "boot0cfg -s 2 -v ${NANO_DRIVE}" fails with the message I've quoted in the subject line. The machine boots fine, but I can't provoke any kind of response from boot0cfg except for input/output errors. I'd like to make the machine start booting from the second slice. Any ideas?