Date: Tue, 5 Apr 2016 14:50:38 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Boris Samorodov <bsam@passap.ru> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: A gpart(8) mystery on 10.3-RELEASE Message-ID: <alpine.BSF.2.20.1604051440020.14591@mail.fig.ol.no> In-Reply-To: <5703B0D5.5060701@passap.ru> References: <alpine.BSF.2.20.1604051125030.14591@mail.fig.ol.no> <5703B0D5.5060701@passap.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Apr 2016 15:34+0300, Boris Samorodov wrote: > 05.04.16 12:30, Trond Endrestøl пишет: > > > What am I doing wrong? Can't gpart(8) write both the pmbr and the efi > > image as a single command? Is it an off-by-one error in gpart(8)? > > Should it? Yes, then it would complement the BIOS style invocation: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > > uname -a > > FreeBSD 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > > gpart create -s gpt ada0 > > ada0 created > > > > gpart add -a 4K -s 800K -t efi ada0 > > ada0p1 added > > > > gpart add -a 4K -s 4G -t freebsd-swap ada0 > > ada0p2 added > > > > gpart add -a 4K -t freebsd-zfs ada0 > > ada0p3 added > > > > gpart show -p ada0 > > => 34 41942973 ada0 GPT (20G) > > 34 6 - free - (3.0K) > > 40 1600 ada0p1 efi (800K) > > 1640 8388608 ada0p2 freebsd-swap (4.0G) > > 8390248 33552752 ada0p3 freebsd-zfs (16G) > > 41943000 7 - free - (3.5K) > > > > gpart bootcode -b /boot/pmbr -p /boot/boot1.efifat -i 1 ada0 > > gpart: /boot/boot1.efifat: file too big (524288 limit) > > Do you try to get only UEFI boot? Then do not use "-b" option. It is > needed for BIOS boot. UEFI and GPT specify the PMBR as a way of telling legacy software not to meddle with the (P)MBR. I wouldn't expect a new disk to contain anything in disk block 0, thus the (misguided on my part?) need for initializing block 0 as a proper PMBR. > Do you need to get a system with both UEFI and BIOS boot? Then use two > different partitions for UEFI and BIOS booting schemes. I have no need for dual-booting. > > gpart bootcode -b /boot/pmbr ada0 > > bootcode written to ada0 > > This is needed only for BIOS boot and together with "-p /boot/gptboot" > option. > > > gpart bootcode -p /boot/boot1.efifat -i 1 ada0 > > <no output> > > Hm, I'm not sure if this is supposed (like: supported) to be done like > this. One may use dd to copy this partition image (boot1.efifat) if > target partition is not less then the file length. > > Otherwise one may format the target efi partition as an msdos-fat one, > create /EFI/BOOT mountpoint and copy boot64x.efi file there. > > Here is a link from another similar thead: > http://www.wonkity.com/~wblock/docs/html/disksetup.html#_booting_with_uefi > > > System is bootable. I guess I upset you all. Case closed. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@freebsd.org Tue Apr 5 17:33:12 2016 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF74DB03F05 for <freebsd-stable@mailman.ysv.freebsd.org>; Tue, 5 Apr 2016 17:33:12 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id D23A51D3C; Tue, 5 Apr 2016 17:33:12 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 676A41B72; Tue, 5 Apr 2016 17:33:12 +0000 (UTC) Date: Tue, 5 Apr 2016 17:33:11 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org Message-ID: <1234163876.194.1459877591119.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <754028565.193.1459855783763.JavaMail.jenkins@jenkins-9.freebsd.org> References: <754028565.193.1459855783763.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is still unstable: FreeBSD_stable_10 #189 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkKKb2VAfYQKfu1t7qk4nR5qzUBEI+UqT4BPec4qHVhqUy0FFdq50sMH+3y9bCDNOufctov6VqTNffZ3YXArnZK95YF0OX97fh+E9txYOUX1adc+TikcKjuYpHmL5dE62eaZTI+4A5jnRonskQ1PaoIFz0Kbu4mWzkFsmdiXTraGzomXq4cHUCATA2+K4eDYgjXEQI30z3GOMmmZ4t/+6QGk1cMb/BqMWHbn80AsRCb4tU7Hpd72XLDpsuO7YRP1Q0CjmNAuBOTj+sFiiOe6U9HpqOlQN+iFUvBdZo/ybuy5Kh71cAaYQNL68cYdZJ6binH/DkG3KY/fS7DFYAeuwjwIDAQAB X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 05 Apr 2016 17:33:13 -0000 See <https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/189/>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1604051440020.14591>