Date: Wed, 15 Aug 2018 14:41:17 +0300 From: Toomas Soome <tsoome@me.com> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-current@freebsd.org Subject: Re: boot errors since upgrading to 12-current Message-ID: <A8C7905C-980F-4A91-A3C7-879E4BE5807F@me.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 15 Aug 2018, at 14:22, tech-lists <tech-lists@zyxst.net> wrote: >=20 > Hello Toomas, >=20 > 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 >=20 > Do you know why this was not happening on 11-stable but is happening = on 12-current? The current has few bits updated about diagnostics (that concerns the = 0x31 error messages), the storage pool issue depends on how the pool is = filled with data - once the BIOS limits are exceeded, we will be unable = to read those data blocks and the errors will appear... >=20 > Once booted, the whole drives in the pool are accessible: >=20 > Filesystem Size Used Avail Capacity Mounted on > storage 5.8T 1.1T 4.8T 18% /storage >=20 > The pool is raidz1-0 so this is the available size I'd expect with 3 x = 4Tb drives. Am I incorrect here? >=20 >> - and is resulting with errors. Thats why you get the errors from = =E2=80=98storage=E2=80=99 pool and yes, this is harmless for boot = because you have separate (small) disk for the boot. >=20 > Is it also harmless for the 'storage' pool ? >=20 Yes, well the catch there is that with this machine, you can not use = those 4TB disks fo boot pool, unless you will create separate smaller = partition within BIOS limits. But if you do not plan to make it = bootable, the data pool does not concern boot loader other than we do = probe disk devices to detect [boot] pool configuration and to make it = possible to boot from different pool. rgds, toomas=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8C7905C-980F-4A91-A3C7-879E4BE5807F>