From owner-freebsd-questions@FreeBSD.ORG Mon Mar 23 12:25:15 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB1D9952 for ; Mon, 23 Mar 2015 12:25:15 +0000 (UTC) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "neonpark.inter-sonic.com", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D38F12D for ; Mon, 23 Mar 2015 12:25:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <55100628.7090106@intersonic.se> Date: Mon, 23 Mar 2015 13:25:12 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: gptzfsboot problem - anyone awake References: <550F5709.2010902@intersonic.se> <018062e6.13dd2c75@fabiankeil.de> In-Reply-To: <018062e6.13dd2c75@fabiankeil.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 12:25:15 -0000 On 2015-03-23 10:48, Fabian Keil wrote: > Per olof Ljungmark wrote: > >> FBSD 10-STABLE and a Proliant P410 controller >> Rebuilt world and kernel last night, rebooted tonight: >> >> gptzfsboot: error 1 lba 32 >> gptzfsboot: error 1 lba 1 >> gptzfsboot: No ZFS pools located, can't boot >> >> As the boot problem with this controller was known when we installed it >> we have two logical drives and boots from the second to get around it. >> >> The box has been upgraded several times during the last four months with >> out a problem. > > Has the gptzfsboot been updated as well or could it have gotten corrupted? > >> I tried to boot from a memstick with latest 10-STABLE (r280048) >> >>> load /boot/kernel/kernel >>> load /boot/kernel/opensolaris.ko >>> load /boot/kernel/zfs.ko >>> set vfs.root.mountfrom="pool-name" >>> boot >> >> But that produced a panic >> >> panic:mountroot: unable to (re-)mount root >> >> Ideas anyone? I'm out of them just now... > > To boot from a ZFS root, the vfs.root.mountfrom value should > start with "zfs:". Yes, that was it, boot from livecd ok now. What remains to be solved though is why we can not boot the box any longer from the array, nothing was changed except the update on the 21st, before that the OS was updated on the 1st of March without a hinch. //per