From owner-freebsd-stable@FreeBSD.ORG Mon Mar 8 11:41:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 583C2106564A for ; Mon, 8 Mar 2010 11:41:01 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id BCBEA8FC15 for ; Mon, 8 Mar 2010 11:41:00 +0000 (UTC) Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id E45BA5C58; Mon, 8 Mar 2010 12:24:04 +0100 (CET) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9j2Qj13CjLVk; Mon, 8 Mar 2010 12:24:02 +0100 (CET) Received: from snifi.localnet (87-204-241-35.ip.netia.com.pl [87.204.241.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id 180094054; Mon, 8 Mar 2010 12:24:02 +0100 (CET) From: Maciej Milewski To: freebsd-stable@freebsd.org Date: Mon, 8 Mar 2010 12:25:30 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.32-trunk-686; KDE/4.3.4; i686; ; ) References: <20100307220002.f4b51436.bconway@alum.wpi.edu> In-Reply-To: <20100307220002.f4b51436.bconway@alum.wpi.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Message-Id: <201003081225.31058.milu@dat.pl> Cc: Brian Conway Subject: Re: 8.0-RELEASE-p2: boot0cfg yields "vnode_pager_getpages: I/O read error" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 11:41:01 -0000 Dnia poniedzia=B3ek, 8 marca 2010 o 04:00:02 Brian Conway napisa=B3(a): > Greetings. I'm testing NanoBSD images for eventual use in an Alix board > and have run into an issue with the boot0cfg lines in the update scripts, > in multiple environments. Specifically, any use of boot0cfg yields a > successful output[1], followed by: > ... > Any ideas? Bug or > user error? Thanks. >=20 > Brian Conway Brian, try changing in updatep1 and updatep2 to use gpart not boot0cfg: #boot0cfg -s 1 -v ${NANO_DRIVE} gpart set -a active -i 1 ${NANO_DRIVE} I think is the problem. I was having similar errors as you while I was usin= g=20 boot0cfg. Maciej Milewski