From owner-freebsd-questions@FreeBSD.ORG Mon Mar 23 00:04:45 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37FA44C1 for ; Mon, 23 Mar 2015 00:04:45 +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 EE2B3BA4 for ; Mon, 23 Mar 2015 00:04:44 +0000 (UTC) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <550F5709.2010902@intersonic.se> Date: Mon, 23 Mar 2015 00:58:01 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: gptzfsboot problem - anyone awake Content-Type: text/plain; charset=iso-8859-15 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 00:04:45 -0000 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. 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... Thanks!