From owner-freebsd-fs@FreeBSD.ORG Wed Nov 21 16:49:49 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1452EE5A for ; Wed, 21 Nov 2012 16:49:49 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5B8E88FC16 for ; Wed, 21 Nov 2012 16:49:48 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA13304; Wed, 21 Nov 2012 18:49:46 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AD0629.1080708@FreeBSD.org> Date: Wed, 21 Nov 2012 18:49:45 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Peter Wullinger Subject: Re: ???BOGOSPAM??? Re: kern/153520: [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable. References: <201211182220.qAIMK1oY061509@freefall.freebsd.org> <50AA4437.1070509@FreeBSD.org> <20121121072546.GA2992@kaliope.home> In-Reply-To: <20121121072546.GA2992@kaliope.home> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 16:49:49 -0000 on 21/11/2012 09:25 Peter Wullinger said the following: > % uname -v > FreeBSD 9.1-PRERELEASE #5 r243290: Mon Nov 19 22:33:42 CET 2012 src@...:/usr/obj/usr/src/sys/ML350 > # gpart bootcode -b /boot/pmbr -i 1 -p /boot/gptzfsboot da0 > da0 has bootcode > # reboot > > Problem seems to be fixed by r243217. > > System has now come up without hassle across three reboots, which is > more stable than usual. The second machine has just completed its > reboot without any problems, too. > > I'll recheck if the issue persists, probably from a cold boot, > once I get the opportunity (probably the next update to -STABLE). Thank you for testing! -- Andriy Gapon