From owner-freebsd-current@FreeBSD.ORG Tue Jan 21 10:47:08 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 746747C0 for ; Tue, 21 Jan 2014 10:47:08 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BDEA01EB7 for ; Tue, 21 Jan 2014 10:47:07 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA28375; Tue, 21 Jan 2014 12:46:58 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1W5YrC-000HcB-3z; Tue, 21 Jan 2014 12:46:58 +0200 Message-ID: <52DE4FD0.5030409@FreeBSD.org> Date: Tue, 21 Jan 2014 12:45:36 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "Andrey V. Elsukov" , Thomas Hoffmann , freebsd-current Subject: Re: Problem updating bootcode on ZFS on root system with MBR References: <52DE3F6B.6050209@yandex.ru> In-Reply-To: <52DE3F6B.6050209@yandex.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 10:47:08 -0000 on 21/01/2014 11:35 Andrey V. Elsukov said the following: > On 20.01.2014 23:32, Thomas Hoffmann wrote: >> I am running 11.0-CURRENT (r260850) with zfs on root with MBR. >> >> After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) >> my zpools reported that they needed to be upgraded. So, I upgraded my >> zpools and I am attempting to update the bootcode (as required). I managed >> to get the boot1 stage code updated, but cannot get the boot2 stage code >> updated. Here is what I have done: >> >> # sysctl kern.geom.debugflags=0x10 >> kern.geom.debugflags: 0 -> 16 >> >> # dd if=/boot/zfsboot of=/tmp/zfsboot1 count=1 >> 1+0 records in >> 1+0 records out >> 512 bytes transferred in 0.014996 secs (34142 bytes/sec) >> >> # gpart bootcode -b /tmp/zfsboot1 /dev/ada0s1 >> bootcode written to ada0s1 >> >> # dd if=/boot/zfsboot of=/dev/ada0s1a skip=1 seek=1024 >> dd: /dev/ada0s1a: Operation not permitted >> >> The final dd statement fails with "operation not permitted". In all my >> research, understood the initial sysctl command I ran would prevent this >> particular error from happening. >> >> What do I need to do to get the boot2 code written to /dev/ada0s1a? > > This will work only if ada0s1a isn't in use. The debugflags trick works > only for whole disk, i.e. for geoms with rank=1. Another way is > calculate needed offset and write bootcode directly to ada0. And ultimately we should extend our ZFS interface with an ioctl to write a blob to a boot code area of a specified ZFS leaf vdev. This would the right way to install zfsboot. -- Andriy Gapon