From owner-freebsd-current@freebsd.org Wed Aug 15 03:06:23 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 B9231106FBCA for ; Wed, 15 Aug 2018 03:06:23 +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 6500A74CC2 for ; Wed, 15 Aug 2018 03:06:23 +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 C0CAF20B78; Tue, 14 Aug 2018 23:06:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 14 Aug 2018 23:06:17 -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=n+e04OTKf7HcO3eQ71mxiYaln5bzg o/zJUGKmFFhsPs=; b=L44iaeiMLUyHrWxZvZvVs6EbRd+EP5QkjXeMjScek8jbc N3QuJtJIAauzX1vYDY2abhUuI9iQaXEozzb5Rcp/bhJC6LtQlP4O7A9SalxwaJH6 xOcv/dkybr8K6J2KxZ2SxG2uTz8q77oVB7V74GGTJDXCkwRX4wkLz43KpDCJA9o4 qH8W8itDkQikWVeCFvPTaLx99ilO0zF+JxPDcJTMNdJH/yXbR8vhKptUWm2TojXG Sb3S87uW4SDNJIZfVuF5KUDYcHQ0R/EJP+4+qIWgEMdN6dZbwnsg8F3qFLEGa3Gf 7IlD3g1b4hy/ogVRRxyyz5daZdO6VE8GUy6uXkI/g== 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=n+e04O TKf7HcO3eQ71mxiYaln5bzgo/zJUGKmFFhsPs=; b=nN80SDZkrUy7aOAXRUK9/T UYKy8cFwgJ6ySqlR/JF/TDMs/EPuL4tkIL06swg95M4xGmhsDAAko1dxnW7mDAA2 wQhR1cnFk8cLIkuMZql246OBZS3e5qgDSVUK5TU1n7ZJjt3QFxp6F3d1zHqggSVA zshpzkVd70oNu+DoGPeZgQspobAwUIBmI8rO4eCd1o7i/pNDOoczxrqcH8CHLrqA 9NYi8g3I0Gkn521fsytHX5p+Mdi+iz7BRidHIbirZkFukybFPysoGw7+GuN3cfdG kjkDZ4XPYXpAK8PJNjM1RQ5TPuS5ox0S5eEtFhNl58d4DXVzcIhavn8F1Q22h5Cg == 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 1C84D10273; Tue, 14 Aug 2018 23:06:17 -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> From: tech-lists Organization: none Message-ID: <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> Date: Wed, 15 Aug 2018 04:06:15 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> 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 03:06:24 -0000 On 14/08/2018 21:16, Toomas Soome wrote: > > >> On 14 Aug 2018, at 22:37, tech-lists wrote: >> >> 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? >> > > Not immediately and yes. In BIOS loader, we do all disk IO with INT13 > and the error 0x31 is often hinting about missing media or some other > controller related error. Could you paste the output from loader > lsdev -v output? > > The drive list appears as an result of probing the disks in > biosdisk.c. The read errors are from attempt to read 1 sector from > sector 0 (that is, to read the partition table from the disk). Why > this does end with error, would be interesting to know, unfortunately > that error does not tell us which disk was probed. Hi Toomas, thanks for looking at this. lsdev -v looks like this: OK lsdev -v disk devices: disk0: BIOS drive C (16514064 X 512): disk0s1: FreeBSD 111GB disk0s1a: FreeBSD UFS 108GB disk0s1b: FreeBSD swap 3881MB disk1: BIOS drive D (16514064 X 512): disk2: BIOS drive E (16514064 X 512): disk3: BIOS drive F (16514064 X 512): disk4: BIOS drive G (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk5: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk6: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk7: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 OK disk4 to disk7 corresponds with da0 to da3 which are sd/mmc devices without any media in. What made me notice it is it never showed the read 1 from 0 to $random_value on 11-stable. The system runs 12-current now. disk1 to disk3 are the hard drives making up ZFS. These are 4TB Western Digital SATA-3 WDC WD4001FAEX. >> Since you are getting errors from data pool ‘storage’, it does not >> affect the boot. Why the pool storage is unreadable - it likely has >> to do about the errors above, but can not tell for sure based on the >> data presented here…. Thing is, the data pool works fine when boot completes. i.e it loads read/write and behaves normally. thanks, -- J.