From owner-freebsd-fs@FreeBSD.ORG Fri Aug 2 14:49:26 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0DB5B18B; Fri, 2 Aug 2013 14:49:26 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 579CA2A88; Fri, 2 Aug 2013 14:49:25 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id ec20so511192lab.28 for ; Fri, 02 Aug 2013 07:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nvTLD1eQb2Xc2MWScbYWZtcKq17Q8s9UYWN0WKDD/Do=; b=TrS70D0qOj+gxc4OFFCwNhLwFnoa8j4HiSRHkHbakr+Qp6furHq5rHlTzZo0onm8JV YOrWKftjhzqdggZZtuhbjqkllViXOBQknshZGZLgcE/ZHZ38JxNEWaEIARwl4jr4UMZI zsplU2qbUie+wbGE7VTV0PyMfhcZjXTi3fpIPbEDZ66q+7b/J1H6Vt7MH7Y9Q3LwHu3l jSrAAjKeBDw1PMWsJ9baBpJ50JRZ2jV4JymYifESUMsSumYPwdZgjv/BOBCjshBgOWvh XNWfuv+tJXBPLJgIL2UnWG3OKSQher3RnFATnXiupG+ZtGOhoN2nlJgy1N0ouZ86w+AR VqbQ== X-Received: by 10.152.29.161 with SMTP id l1mr3222059lah.17.1375454963185; Fri, 02 Aug 2013 07:49:23 -0700 (PDT) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id j1sm3466250lag.4.2013.08.02.07.49.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 07:49:22 -0700 (PDT) Message-ID: <51FBC6F1.9030408@gmail.com> Date: Fri, 02 Aug 2013 17:49:21 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130802 Thunderbird/17.0.7 MIME-Version: 1.0 To: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= Subject: Re: ZFS: can't read MOS of pool References: <51ED5B69.8050200@wasikowski.net> <51FBC24B.5030609@gmail.com> <51FBC4DC.4090506@wasikowski.net> In-Reply-To: <51FBC4DC.4090506@wasikowski.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-stable@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: Fri, 02 Aug 2013 14:49:26 -0000 02.08.2013 17:40, Łukasz Wąsikowski wrote: >>> Any hints how to go from here? >> >> First, how did you update bootcode? `ls -la /boot` also wood help. >> >> Second, what is your /etc/make.conf and /etc/src.conf? > > I'm updating bootcode with: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > > /etc/src.conf doesn't exist (I'm using GENERIC kernel on this VM) > /etc/make.conf - http://pastebin.com/QapEWzfJ > Looks good. Can you also try what Trond suggests about boot order? You can also list your boot fs in /boot/loader.conf like vfs.root.mountfrom=zfs:klawisz/ROOTFS. Or you can just add this at loader prompt. There's also a ${SRC}/tools/tools/zfsboottest script that can tell you something about booting from your pool. -- Sphinx of black quartz, judge my vow.