From owner-freebsd-current@freebsd.org Tue Aug 14 19:37:27 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 106F41055CAA for ; Tue, 14 Aug 2018 19:37:27 +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 97AA98411F for ; Tue, 14 Aug 2018 19:37:26 +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 064EC21957 for ; Tue, 14 Aug 2018 15:37:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 14 Aug 2018 15:37:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=iZQBO65w7daa03C5a+oWQ3532LKnjYa9uZpmfUk+OCs=; b=h499Tafi RBh4A7EaezgU/MfJxhaWD8hKHckXB9hzohbi8b8D59y1EySIf7jcokWvd3VnNOg5 +ja7wAyhLl30yH1Uy+42de9Dad5F9Gq5E4WoI2x08BTByYZdcBJ/nfjMP5g/FYHI odGSfIeMARm9iw7DeQKtqXPyZ4HHRCblbj6KOM6q3EdV2bouG/ZNeYPdE511YiKT dT8cy4BXw+GIciJB7i74NcGx2yJGZTM+e3mySagLT8xzbdn7ZlzdaPMFlNdQNRaA PNoVYfm1OFz0Mta3dNubsf0C6rLH4RMr0tlh2gBt0P4ONMiPzk3AFOWAUcADGAiJ AH/pri2iQsP6Sg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=iZQBO65w7daa03C5a+oWQ3532LKnj Ya9uZpmfUk+OCs=; b=W34UZnHZuzx2tWExc+7dnSCQ3/EFOouQ1QrtOr9RCyxgV vFyxvDZGKqmQyCVqc6cP+TE6m0tnKJ6mkL+8OByS1gnHaxpu6VUYcIaB/yfJx5TZ QQT2rTeTJJah/DupSAYeoswExPHvG2TUbm10KfkKSx2IA2fVMqe4YYz8X1ue0Z/1 oTwpSKqV4eCSfqssBpsJ0sMp1oSmcb7kE83WIN3eXTY28uIYTnnVIZMPhM3Ey9a4 9zAKZQDsT6XBSapIB3Jtmvas4yjfFD5jNjMcZcAsZ0sLfwRymhez6ew8S3utt+OM kG0h7Pj+pQZghmlCqTE7d5WYB7moHtn3mdWqg///g== 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 746BE10261 for ; Tue, 14 Aug 2018 15:37:25 -0400 (EDT) To: freebsd-current@freebsd.org From: tech-lists Subject: boot errors since upgrading to 12-current Organization: none Message-ID: Date: Tue, 14 Aug 2018 20:37:24 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Tue, 14 Aug 2018 19:37:27 -0000 Hello, context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is *not* root-on-zfs. It boots to an SSD. The three disks indicated below are spinning rust. NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 This machine was running 11.2 up until about a month ago. Recently I've seen this flash up on the screen before getting to the beastie screen: BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 [the above is normal and has always has been seen on every boot] read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 the above has been happening since upgrading to -current a month ago ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool storage the above is alarming and has been happening for the past couple of days, since upgrading to r337682 on the 12th August. The beastie screen then loads and it boots normally. Should I be concerned? Is the output indicative of a problem? thanks, -- J.