> On 15 Aug 2018, at 14:22, tech-lists <tech-li...@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… 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 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... > > Once booted, the whole drives in the pool are accessible: > > Filesystem Size Used Avail Capacity Mounted on > storage 5.8T 1.1T 4.8T 18% /storage > > The pool is raidz1-0 so this is the available size I'd expect with 3 x 4Tb > drives. Am I incorrect here? > >> - and is resulting with errors. Thats why you get the errors from ‘storage’ >> pool and yes, this is harmless for boot because you have separate (small) >> disk for the boot. > > Is it also harmless for the 'storage' pool ? > 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 _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
