From nobody Thu Jan 27 14:12:44 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 BF2DA19868C6 for ; Thu, 27 Jan 2022 14:12:47 +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 4Jl2bz573Lz3Prq for ; Thu, 27 Jan 2022 14:12:47 +0000 (UTC) (envelope-from avg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643292767; 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=x+KpdHlLqomkH8zxeo3on3uX/651IJDAeZavNYy94EE=; b=c4oSXS0F51kiJooPj6WPS45Ljp/nHj3rVNOHDhGdBA6l39Tf2/9JrwE6NWkzFI1ZL33OYI kocAmoTyBOJxSuDmTgd3xeMDF/+jKBRznpbCx4cguvT+ttQQOomk7vyjlGbDw4w/SFkIWZ FELkHoTMEPMf02OfmHeEz1yspZH5OE/9ue0ase6ZdoUYMfmcSFC80EkH6yFpjcxM+MyS19 g4Ef8Tl6cI4MGtJjBZJLX9Rnl1SIeOuR7YLklfmokWvScn22055sbGMt7H2J4LfTHL+hw5 4YNK3UzB0G3Mk5nqjPFYNUjjRWAKasTOsGWJyGUxtUgs1/jsKSiVsXuXaAlkfw== 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 548FE2818 for ; Thu, 27 Jan 2022 14:12:47 +0000 (UTC) (envelope-from avg@FreeBSD.org) Message-ID: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> Date: Thu, 27 Jan 2022 16:12:44 +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 Subject: Re: gptzfsboot can't boot from 4TB SSD Content-Language: en-US To: freebsd-stable@freebsd.org References: From: Andriy Gapon 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=1643292767; 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=x+KpdHlLqomkH8zxeo3on3uX/651IJDAeZavNYy94EE=; b=Go+UfX3Tz7Irp6/JCZpQqM5bxm7z1K9Vfr0Qnz9RfovmNEw6PK+3DXgQML2szhjIlCce27 rfymsLgHXiYpYTpB3YpUn1TagJOvWWSjBVh/8nKDKVrCBCY6cQV7a9vwW1EKEklv4YZXcs HS3xZ8lFzvrGJ3WdrJiD/6GSXsvFzgX4h4dkAJlXqhlplbjbd+tURFIabyzBq6JpXfwoAJ 9riiyqKpwOJDA8wfkkFt22ozm4jOuy6sDD2cSZC1F+CcNp4rJU026a3hJd4E1EF5no3Tg6 ANwHr1LKxbRAtWM3l5lPedlgVt8avK0Tlt7JaNqfrqnW8Fp0/KNZWtv2ru3yww== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643292767; a=rsa-sha256; cv=none; b=Ij7obnE/8Lc8lAmf6jEIXYl1igaBV/Abesj0EJiONVotJOHhBIBtQq0xD5Q58uxKEwuXW+ WUTMTfbUm1WmHfEfX2XaugpgQkveA0b7xCY8FO9QmfvGwAIZyzR/G8NK+lFeEpc3QX8GTk L1t8b3AHVBdOlMJlV5FW2jeBytNAjGtICu07SY7Hg56satDATCv8Iht9YPhuA5S97qjsFu oa/aF/f8dysKX7R+IjpVfLA4oxi9Z2QYG+aAzOIWRGvdKWEeLPI1FzvwBKyEkRcJ0ST8di psXCFi3PBQ6KJfocOipiTA+rYUCeJMVI8m6fkRU0f7+VE+siIehOdnjNsHeSJA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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. -- Andriy Gapon