From owner-freebsd-current@freebsd.org Wed Feb 8 12:35:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E765DCD6919 for ; Wed, 8 Feb 2017 12:35:53 +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 C148B13CF for ; Wed, 8 Feb 2017 12:35:53 +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 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL200K002R26K00@st13p35im-asmtp001.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 12:35:46 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486557346; bh=mTo0Hoqo9Yho0HlG9yiw+t1KA7fBWvvBN+ow4xeELUY=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=GJ6Bzoat2zoRqI4wdh8qnDDTDuTY1be+O64wBkWDGJp5PUddP7aLWR0/Qg/tjTDXY HH6tPtZUrdy/2x/AJVQIFPQWOeGj7VPMjYbnBV/cCzk5PNPhLFxqjLD8fFpi42ygF1 la6r70rRV9NqFMwhHjcfhXCmYP9i2WyjUpHdbKcAxwQIJMmIDO4v8wC3H4dUvuE2Q9 uhKAoMNuhUqI10fa+csy0173ZQvVEr9UOcmdL2MghQtQpSBHNqC0PaUX8LHGLzAFS8 yGI0D+/uWBT0naZVYedfS/fvR9Z7AfMEngUkIwVi+3Zj1RxJV9Jg+zRzF83Yc3+Vzm QNBhKwNFlv1AA== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL200GKF2ZJNY00@st13p35im-asmtp001.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 12:35:46 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-08_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=5 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702080123 From: Toomas Soome Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: gptzfsboot trouble Date: Wed, 08 Feb 2017 14:35:43 +0200 References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> To: FreeBSD-current@freebsd.org In-reply-to: Message-id: X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Feb 2017 12:35:54 -0000 > On 8. veebr 2017, at 14:26, Ronald Klop wrote: >=20 > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn = wrote: >=20 >> Hi all >>=20 >>=20 >> Last week I decided to upgrade my FreeBSD installation - it's been a = while >> (September 16 was last time). Unfortunately CURRENT does not boot and = cash >> in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to = attempt >> to read blocks that exceeds the physical disk. Initially I through it = was a >> hard disk error - but after a "oh" experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical = boundaries >> of the disk (300GB disk). In order to rule out different options - I >> installed a vanilla 11-RELEASE on the 300G with a simple stripe - it = also >> gives the error but does boot - the LBA of the error is slightly = different >> on 11 CURRENT and comes up with LBA 921600 >>=20 >>=20 >> I have scanned all the disks for physical faults and there seems to = be none >> and I have tried doing a single disk installation on each disk - they = give >> the same error - Does anybody have any idea? Included Photos as = sometimes it >> get through to the actual boot menu but then crash in another place >>=20 >>=20 >> I have some images - but they are 2 bit for the mailing list ;-) >=20 >=20 > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 >=20 > Would be nice if you tell more about the system. CPU? dmesg? > The 11-RELEASE did that boot from the same disk? In the mentioned = issue there is the case that gptzfsboot does recognize a secondary disk = (can be configured as mirror), but not the first. >=20 > As you say UFS works, the bug might be in the gptzfsboot code, because = that is not used for UFS. >=20 There is another possible test scenario - to create pool on BSD labeled = disk, so we can see if it is just about the zfs code itself or rather = related to GPT. Or vice versa, try ufs on GPT labeled disk. rgds, toomas