From owner-freebsd-fs@FreeBSD.ORG Sat Feb 8 07:16:45 2014 Return-Path: Delivered-To: freebsd-fs@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 62CF8F4; Sat, 8 Feb 2014 07:16:45 +0000 (UTC) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 360F61174; Sat, 8 Feb 2014 07:16:44 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.jrv.org (Postfix) with ESMTP id 27B8C24A001; Sat, 8 Feb 2014 01:08:32 -0600 (CST) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from mail.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsrpXWJZofZE; Sat, 8 Feb 2014 01:08:22 -0600 (CST) Received: from [192.168.23.128] (BMX.housenet.jrv [192.168.3.140]) by mail.jrv.org (Postfix) with ESMTPSA id 13C9D1EA1B0; Sat, 8 Feb 2014 01:08:22 -0600 (CST) Message-ID: <52F5D7E7.70006@jrv.org> Date: Sat, 08 Feb 2014 01:08:23 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows NT 5.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Andrey V. Elsukov" Subject: Re: amd64/186515: Doesn't boot with GPT when # of entries over than 128. References: <201402061930.s16JU2Pi052495@freefall.freebsd.org> <52F4D4C9.3060902@yandex.ru> In-Reply-To: <52F4D4C9.3060902@yandex.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Feb 2014 07:16:45 -0000 On 2/7/2014 6:42 AM, Andrey V. Elsukov wrote: > On 06.02.2014 23:30, John Baldwin wrote: >> Using more entries to pad out the table isn't the normal way to handle 4k >> alignment. You can just leave a gap before the start of freebsd-boot. Having >> the sectors "free" vs having them contain zero'd GPT entries doesn't really >> make a difference. One question is when does the boot break? Does it make it >> into the loader and break trying to boot the kernel? Does it make it into >> gptboot and break trying to load the loader? > Hi John, > > this is gptboot's restriction. Look at the sys/boot/common/gpt.c. > For the last couple of years every FreeBSD system I've installed has been partitioned by this command: bigtex:/root# grep -- -s.gpt mkdisk.sh gpart create -s gpt -n 152 "$DISK" || exit yielding something like bigback:/root# gpart show => 40 3907029089 ada0 GPT (1.8T) 40 128 1 freebsd-boot (64K) 168 29828864 2 freebsd-swap (14G) 29829032 3877200097 3 freebsd-zfs (1.8T) I guess the bug is unique to GPT UFS booting?