Date: Mon, 8 Mar 2010 09:32:11 -0500 (EST) From: Brian Conway <bconway@alum.wpi.edu> To: Maciej Milewski <milu@dat.pl> Cc: freebsd-stable@freebsd.org Subject: Re: 8.0-RELEASE-p2: boot0cfg yields "vnode_pager_getpages: I/O read error" Message-ID: <alpine.DEB.2.00.1003080928440.30892@ladyluck.zxvf.local> In-Reply-To: <201003081225.31058.milu@dat.pl> References: <20100307220002.f4b51436.bconway@alum.wpi.edu> <201003081225.31058.milu@dat.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-160343530-1268058731=:30892
Content-Type: TEXT/PLAIN; charset=iso-8859-2; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
On Mon, 8 Mar 2010, Maciej Milewski wrote:
> 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.
>>
>> 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 us=
ing
> boot0cfg.
>
> Maciej Milewski
>
Maciej,
Thanks, that resolved it and I've updated the scripts on my end. It looks=
=20
like nanobsd.sh is using boot0cfg successfully when it builds the images,=
=20
so I'll submit a PR.
Brian Conway
--8323329-160343530-1268058731=:30892--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.DEB.2.00.1003080928440.30892>