Date: Wed, 15 Aug 2018 18:18:16 +0300 From: Toomas Soome <tsoome@me.com> To: tech-lists <tech-lists@zyxst.net> Cc: Kyle Evans <kevans@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: boot errors since upgrading to 12-current Message-ID: <F4DFDE06-8F93-4628-A200-99878D6666DD@me.com> In-Reply-To: <dbc7db12-70a5-b56b-bdc8-f2e6389fd5e4@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> <CACNAnaHogeyCytPAEwYZPE%2BU1=0rwXUx8JNu=UbPHkLUc=rZzQ@mail.gmail.com> <cc47ceab-22c2-3b87-8e88-92a314889da2@zyxst.net> <dbc7db12-70a5-b56b-bdc8-f2e6389fd5e4@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 15 Aug 2018, at 16:52, tech-lists <tech-lists@zyxst.net> wrote: >=20 > On 15/08/2018 13:20, tech-lists wrote: >> On 15/08/2018 12:49, Kyle Evans wrote: >>> On Wed, Aug 15, 2018 at 6:22 AM, tech-lists <tech-lists@zyxst.net> = wrote: >>>> Hello Toomas, >>>>=20 >>>> On 15/08/2018 07:31, Toomas Soome wrote: >>>>>=20 >>>>> 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 >>>>=20 >>>>=20 >>>> Do you know why this was not happening on 11-stable but is = happening on >>>> 12-current? >>>>=20 >>>> The BIOS has not been modified since the machine was bought back in = 2014. >>>>=20 >>>=20 >>> 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. >>>=20 >>> Thanks, >>>=20 >>> Kyle Evans >>>=20 >> Thank you Toomas and Kyle for the clarifications. >=20 > addendum to this - installed new world and kernel r337835 and the zfs = warning at boot seems to have disappeared. Something else odd has = started happening though, will make a new email for it - usb keyboard no = longer functioning at the beastie menu, but functions when boot = completes. >=20 >=20 The size related problem is entirely about luck - to read the pool, we = get pool config from label, and then read MOS (meta object set), and if = we can not read MOS, we are busted. if we can read MOS, the zfs probe in = boot loader is happy (actual file reads is still different story). = However, whenever the pool is changed, the MOS will get updates and its = location can (and will) change. rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4DFDE06-8F93-4628-A200-99878D6666DD>