misc/144553: NanoBSD's updatep* scripts fail with boot0cfg:
vnode_pager_getpages: I/O read error
Brian Conway
bugs at zxvf.us
Mon Mar 8 14:40:02 UTC 2010
>Number: 144553
>Category: misc
>Synopsis: NanoBSD's updatep* scripts fail with boot0cfg: vnode_pager_getpages: I/O read error
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 08 14:40:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Brian Conway
>Release: 8.0-RELEASE-p2
>Organization:
>Environment:
FreeBSD fbsd8.zxvf.local 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 16:02:27 UTC 2010 root at i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
>Description:
The final step in the NanoBSD's updatep[1,2] scripts, boot0cfg appears to succeed, but leaves disk access unusable with errors of "vnode_pager_getpages: I/O read error". Full information and thread here:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055653.html
>How-To-Repeat:
'boot0cfg -s 1 -v ad0' from a booted NanoBSD image.
>Fix:
In updatep1, replace:
#boot0cfg -s 1 -v ${NANO_DRIVE}
gpart set -a active -i 1 ${NANO_DRIVE}
However, it looks like the nanobsd.sh script is using boot0cfg successfully when building the disk image, so this may not be the correct approach (or may require updating in both places). Thanks.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list