From nobody Thu Jan 27 15:09:07 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 0BAA3198372E for ; Thu, 27 Jan 2022 15:09:27 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jl3sL10R6z4ZMM; Thu, 27 Jan 2022 15:09:26 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mail-wr1-f54.google.com with SMTP id h21so5325565wrb.8; Thu, 27 Jan 2022 07:09:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RJqnjQzE1NB+IdyVbS88P+H/NEhkW8hnxPpm+VhZU/c=; b=ZdEZHoyjrKsN7FVD0ZnIXSItL1druJZbhaTUCCA2wEY6af/Kb2qm63u5K4j0e6ySVX J8Bjflz9MT57T7hjbbzx1ZGn7RlWIIvE9yxugfjaLiElbNM393MQOCl4yYwLyTR3NTD+ xOM8ULByQGzFuyYmCRdEXLCOp13dVrSaODUcr1Vg1hHwb+wbBdjK3CXtFzRCGfWn4HaH oHVQ54hOiq/ncY3UGTSjBdFZWGsFXrfPgzcuqTPY8hKkBJyG5iHXwUZFyk+AHfQVJqMh a7FJ1LiTqIE9daHyxoknDU0dEZDjoRPIazH5PMoY+V6kBrBIA6lmN9WVR+ynZye2SuII +Qjg== X-Gm-Message-State: AOAM530MLsvopTgIv+O4zc9C77CyiDQWa9o76CbaLUly6H7Ps0oQHt4M 0pbuKpAVzMMdAr8bFlDRhOClPxFyl5q4YxtbzDx/BpvK X-Google-Smtp-Source: ABdhPJxQr9B9ZiDhLWyNPe0evWWA2MC0443e3J6AFtxiW4clhz8ymOLuEa4f1hxeRzCwHwBEFyh98Zbvm6vhMvctkiA= X-Received: by 2002:a05:6000:1b8a:: with SMTP id r10mr3416243wru.665.1643296158533; Thu, 27 Jan 2022 07:09:18 -0800 (PST) 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 References: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> In-Reply-To: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Thu, 27 Jan 2022 16:09:07 +0100 Message-ID: Subject: Re: gptzfsboot can't boot from 4TB SSD To: freebsd-stable@freebsd.org Cc: Andriy Gapon Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Jl3sL10R6z4ZMM X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of uspoerlein@gmail.com designates 209.85.221.54 as permitted sender) smtp.mailfrom=uspoerlein@gmail.com X-Spamd-Result: default: False [-0.31 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-0.86)[-0.862]; NEURAL_SPAM_MEDIUM(0.99)[0.994]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.54:from]; MLMMJ_DEST(0.00)[freebsd-stable]; FORGED_SENDER(0.30)[uqs@freebsd.org,uspoerlein@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.54:from]; R_DKIM_NA(0.00)[]; R_MIXED_CHARSET(0.56)[subject]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[uqs@freebsd.org,uspoerlein@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Thu, Jan 27, 2022 at 3:13 PM Andriy Gapon wrote: > On 27/01/2022 15:57, Ulrich Sp=C3=B6rlein 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... Or should I bring back a / UFS partition in the front instead, with /usr and /var on ZFS?