From owner-freebsd-current@freebsd.org Wed Aug 15 12:42:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E99541082EF3 for ; Wed, 15 Aug 2018 12:42:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 961928A1E8 for ; Wed, 15 Aug 2018 12:42:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDI00100320FR00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 15 Aug 2018 11:41:21 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDI00HR234U2W00@st13p35im-asmtp001.me.com>; Wed, 15 Aug 2018 11:41:21 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808150128 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-15_04:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: boot errors since upgrading to 12-current From: Toomas Soome In-reply-to: Date: Wed, 15 Aug 2018 14:41:17 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> To: tech-lists X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 12:42:19 -0000 > On 15 Aug 2018, at 14:22, tech-lists 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=