Date: Wed, 15 Aug 2018 06:49:50 -0500 From: Kyle Evans <kevans@freebsd.org> To: tech-lists <tech-lists@zyxst.net> Cc: Toomas Soome <tsoome@me.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: boot errors since upgrading to 12-current Message-ID: <CACNAnaHogeyCytPAEwYZPE%2BU1=0rwXUx8JNu=UbPHkLUc=rZzQ@mail.gmail.com> In-Reply-To: <d93df45c-99f5-0549-1154-9fd3c62193bd@zyxst.net> References: <f3cb9196-0e89-6c4e-5e8f-d3c4e48e16dc@zyxst.net> <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> <C3AC526B-56DD-4273-A3FB-7BBB472563E5@me.com> <d93df45c-99f5-0549-1154-9fd3c62193bd@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 15, 2018 at 6:22 AM, tech-lists <tech-lists@zyxst.net> wrote: > Hello Toomas, > > On 15/08/2018 07:31, Toomas Soome wrote: >> >> Well that does explain the problem, if you look on the sizes reported=E2= =80=A6 so >> your BIOS is reporting wrong sizes, is unable to access whole 4TB space = and >> the zfs reader is not getting the correct data from the disks > > > Do you know why this was not happening on 11-stable but is happening on > 12-current? > > The BIOS has not been modified since the machine was bought back in 2014. > Perhaps r335245, which fixed a logical error and completely changed the calculations for this stuff and possibly sent you on dramatically different path. There's not too many commits to this area that haven't yet landed back in stable/11, fortunately. Thanks, Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHogeyCytPAEwYZPE%2BU1=0rwXUx8JNu=UbPHkLUc=rZzQ>