Date: Thu, 27 Jan 2022 16:09:07 +0100 From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= <uqs@freebsd.org> To: freebsd-stable@freebsd.org Cc: Andriy Gapon <avg@freebsd.org> Subject: Re: gptzfsboot can't boot from 4TB SSD Message-ID: <CAJ9axoRneWhE61k-o0xTH04wyLQnoeNwD6Y2myR0vnvD1Q01Vg@mail.gmail.com> In-Reply-To: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> References: <YfKkr%2BmC6rMrRlF9@acme.spoerlein.net> <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 27, 2022 at 3:13 PM Andriy Gapon <avg@freebsd.org> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ9axoRneWhE61k-o0xTH04wyLQnoeNwD6Y2myR0vnvD1Q01Vg>