Date: Wed, 15 Aug 2018 12:22:22 +0100 From: tech-lists <tech-lists@zyxst.net> To: Toomas Soome <tsoome@me.com> Cc: freebsd-current@freebsd.org Subject: Re: boot errors since upgrading to 12-current Message-ID: <d93df45c-99f5-0549-1154-9fd3c62193bd@zyxst.net> In-Reply-To: <C3AC526B-56DD-4273-A3FB-7BBB472563E5@me.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 BIOS has not been modified since the machine was bought back in 2014. 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 ? thanks, -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d93df45c-99f5-0549-1154-9fd3c62193bd>