From nobody Thu Jan 27 15:13:10 2022 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4C4661984EBD for ; Thu, 27 Jan 2022 15:13:14 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jl3xk1mg8z4bbc; Thu, 27 Jan 2022 15:13:14 +0000 (UTC) (envelope-from avg@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643296394; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n8JLrvNPeNQ8YorlFJby2CZ7f+hLgEKCuN+MIFDzH1Q=; b=D3Wdtp1M3h/wCc+s7vtYfRhhWYuTpj3O8KBoU2wkw/Puy/sicym0lUuFAxNWyognB8fqg0 nhMy+tcQuPBlnVk4Eda5reu5MLxsMJ98zzmVXR6BRsUPhaTchGHpZdqwu9r9F4Juqh6AA5 T6AyxWU7T5ETXAVaFChS3qxCK+OJCsqvBScO0kueQ2sCGx2kUm8tfFJJKi9qaBDiKRR0Ag heNUJ1GytXRFRAaupvTPGgbLXGrv5LcBQwNS6uMitVUY3ATY/ivTQ59cDTU7ggWa4WypFP VfwMDW1Ag3TDFw7G6WtvjDIGc+D/v9jaop08JjRG31NRh27v12FXgLrKb8heYw== Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 9287720F2; Thu, 27 Jan 2022 15:13:13 +0000 (UTC) (envelope-from avg@freebsd.org) Message-ID: <9c9bba54-e6ee-157c-87f0-c85a5eafc676@FreeBSD.org> Date: Thu, 27 Jan 2022 17:13:10 +0200 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.5.0 From: Andriy Gapon Subject: Re: gptzfsboot can't boot from 4TB SSD Content-Language: en-US To: =?UTF-8?Q?Ulrich_Sp=c3=b6rlein?= , freebsd-stable@freebsd.org References: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643296394; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n8JLrvNPeNQ8YorlFJby2CZ7f+hLgEKCuN+MIFDzH1Q=; b=MNLY6NNCsVQ0PvTvtbmZYLG4XxMA9qmiQ1sGFr/zcTvjyWlC3ylvFhYxJXFjHJpymU/dEr 23umeSxnKvow28LNTdjwKSrcLj26eKdULHfmLa901pvaKGrvALMyx1909Lq95P+59NiOj4 AYWzV+Jk9YP940/mSaJWF1TjRQcqrcVndkclBZjF7mg+lRWLth3g9EjakjUJmUW1cySZW4 VpFuRqhlMNgcG1JnhmkWbBz4tTnvxw55NbwRVcjn3fFcSIm7U3zv9NwHNFMALsW5HjFkjt 3MVSd/iIwbGkmhdfd/QikuZOjgza03ceMehJ6LudvgsMk6SO7RnuZyXLk/j5EA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643296394; a=rsa-sha256; cv=none; b=b0Wwo9lOK5Sbj1udQLCz3JXoAJvBTL8VpX/d7FkeGacay14m1vFnJTz+sJN0w/pC80XENZ 180a03XSrDAD26/xdM056OWQo2qQKpNfkCFGCVaiyZ/MpxIHbDkIt1h2gmoZSyl6WINpbE NteQQqlsS8PY+HHh90/+ogSaU023M4FbqXeW+gj+v8BdvQx4mDQJPZlBO6COBJQUFmivfg SAfIL/ua/elu/GyZtyV3ZTDqLJ/M1QU8TQIrpOTENQ4aptzpw8plN68bvuRtNslnnibyH5 gVCYreovkmpAw5SnCKfwkQ3N2fc0qWxIU3pspC+JTMmWxcCfmuXdYJUifSz7wQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 27/01/2022 17:09, Ulrich Spörlein wrote: > On Thu, Jan 27, 2022 at 3:13 PM Andriy Gapon wrote: >> On 27/01/2022 15:57, Ulrich Spörlein wrote: >>> So can this be a shortcoming in the BIOS with large drives? >> >> Yes, it can. >> many people encountered this kind of a problem in the past. >> 2TB (2^31 bytes) is the common boundary. >> >>> I had thought that only applies to boot0, not the loader itself. >> >> loader also uses BIOS calls for disk access. > > Would that issue go away with UEFI and its ~100MB partition being in > front of the disk? It would still > need to be able to read the loader and kernel from anywhere in those > 4TB though... I don't know. There is a greater chance that UEFI would be more correct, but there is no guarantee. > Or should I bring back a / UFS partition in the front instead, with > /usr and /var on ZFS? It's up to you, of course. You can also have a separate ZFS boot pool (a pool containing a dataset for /boot or for /) in the lower half of the disk. -- Andriy Gapon