From owner-freebsd-current@freebsd.org Wed Aug 15 11:22:25 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 2DB76107FE56 for ; Wed, 15 Aug 2018 11:22:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB16D868FC for ; Wed, 15 Aug 2018 11:22:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 49C7521C08; Wed, 15 Aug 2018 07:22:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 15 Aug 2018 07:22:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=gkhbcZz8LmAAFn2pYCkBJmK4tkhKv TH/uhPgilOl7uM=; b=KgDKIFjIFtKyvE1mMWWAlstJrYKx0Au94rDYQ/Nzw7gZ6 gyPVUwln83K/qXTSRGCrFfoT9o5Hf7DcdK2I+KgW/sbXtsX7t6knp+YQGKk2Q+FB 98d3jFc8KdtZz+jIiBorZC3+p/3sAwD7jaI2U5BgnVu7IGDaxFkIFXXNn8umBwxQ a/zC9u1dhE85qU12SoNd7e68wSN32om+mqN/V8H8dIE0eDl0lR7bkq2TZvtX6I7L 7rdh1NbWvLajfW45DXtc9K6K0WeYFIPe6v9Fio+A6Bd2G5oOAA/vK2r2a9EarxP+ Sx+gXDIKXfce22SMAC5F59WnxicnFYmE1WUulKXhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=gkhbcZ z8LmAAFn2pYCkBJmK4tkhKvTH/uhPgilOl7uM=; b=OZ8uYnoOJ04V7cwe4owPaJ Qy2Gi/s2srGAxOFEDViqNW1gevuBSWqTpsxtFL2b3e/i8pJFVsKt36suPFrPlyij 4ouAZShAgb4WOBZGHWkUKWTM41KpiCRNQNm7V8DsDUGhfEQjLVKXgKznamZ3TcCy BCbWcmKpuocZgxTmVyp3TacwA+oPeGlCoFWO6pnuzHrYDzcLcQ86g3v1o/4+7WDX DA4O5D2GD2dGQY3pic07/hqd0onJil3VKw2Pz4zuZvefGynAF+bb7jeKzXPfgmAV G4dsolaV9mxoMLobAAh59WbvsOSJOJgBBbQ4iypApDzQUfnXQIw0u8harW8/vnhw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A130B1028B; Wed, 15 Aug 2018 07:22:23 -0400 (EDT) Subject: Re: boot errors since upgrading to 12-current To: Toomas Soome Cc: freebsd-current@freebsd.org References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> From: tech-lists Organization: none Message-ID: Date: Wed, 15 Aug 2018 12:22:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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 11:22:25 -0000 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.