From owner-freebsd-current@freebsd.org Tue Aug 14 21:17:12 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 5C3E31064A00 for ; Tue, 14 Aug 2018 21:17:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 8094489667 for ; Tue, 14 Aug 2018 21:17:11 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDG00A00VZBTZ00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Tue, 14 Aug 2018 20:16:11 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDG00IPEWAVIN50@st13p35im-asmtp002.me.com>; Tue, 14 Aug 2018 20:16:09 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-14_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808140204 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: Tue, 14 Aug 2018 23:16:06 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> References: 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: Tue, 14 Aug 2018 21:17:12 -0000 > On 14 Aug 2018, at 22:37, tech-lists wrote: >=20 > Hello, >=20 > 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. >=20 > 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 >=20 > This machine was running 11.2 up until about a month ago. >=20 > Recently I've seen this flash up on the screen before getting to the = beastie screen: >=20 > 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 >=20 > [the above is normal and has always has been seen on every boot] >=20 > 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 >=20 > the above has been happening since upgrading to -current a month ago >=20 > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool storage >=20 > the above is alarming and has been happening for the past couple of = days, since upgrading to r337682 on the 12th August. >=20 > The beastie screen then loads and it boots normally. >=20 > Should I be concerned? Is the output indicative of a problem? >=20 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. Since you are getting errors from data pool =E2=80=98storage=E2=80=99, = 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=E2=80=A6.=20 rgds, toomas