From owner-freebsd-current@freebsd.org Wed Feb 8 13:17:41 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 2BCA1CD657B for ; Wed, 8 Feb 2017 13:17:41 +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 03B6C11E3 for ; Wed, 8 Feb 2017 13:17:41 +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 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL2005004UR8700@st13p35im-asmtp002.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 13:17:40 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486559860; bh=ceJYMEUUqRMUfaHESOav6WWA9sOfriCoGhZ7JdEWTtg=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=A7DHd/qO7f3Rp53OMleBNyAcj/zUX+Pav05krNEMFbgpjpuDnO3VdRJ7z85TXNBdx Eqp7fft3Spr82rrmOZyWDesk+mAtFTef7gtWRZFPJx6Auk5Y6ePoh3lNqG/nGx1FeZ qHjAXy6eutQhBXiOZXMDrr2ShktwE32gVBjiY0TsUhuqZ/Ni7lzwVm9g0/AAxKxu7x iBoJZ15c93+/QD4pfAf2JIUbx618LU+Tt7lgD36YMdDS3ue7xB1bDsHdLyx0JOHRZE B9P5qK2nfPPZiNYVXJ16vzxH75g+Sqd48X6L+Nw8o5mHyrGzyEyuGX9Hq2YuTlM8lJ iiCkW41LFOiyw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL200M9S4XEEE20@st13p35im-asmtp002.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 13:17:39 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-08_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=12 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702080131 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 15:17:37 +0200 References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002201d28208$85492bc0$8fdb8340$@btinternet.com> To: FreeBSD Current In-reply-to: Message-id: <2F2FC064-7508-4BA2-96EE-820A4E1E9F64@me.com> 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 13:17:41 -0000 > On 8. veebr 2017, at 14:51, Ronald Klop wrote: >=20 > On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn = wrote: >=20 >>=20 >> The bug in the bugzilla could be related - what is weird is I have = been running this setup for years without issues - which I guess just = shows how good ye'ol FreeBSD still is ;-) Tried to run through the svn = log but could not immediately see anything that seemed to be related >=20 > I was triggered on that bugzilla issue because of the wrong lba = number. I would start from carte blanche. 1. extract/write down the GPT header content; especially = important/interesting ones are alternate LBA for backup label location = (and therefore the disk end), the sector size used by GPT. 2. verify we do get the same sector size used with BIOS INT13 and if we = can actually read the last sectors. This one is with catch - it implies = some coding with gptzfsboot just to try to extract the information, = fortunately the BIOS interface is simple enough to use and it should not = be too hard:) Based on the results, we can try to figure out what really is happening = there and why things break down. One possible hypothesis is: as you wrote, your disk is 3TB; now it *may* = be the actual BIOS INT13 interface to address higher sectors is just = buggy, and it just can be so that the zfsloader binary is stored towards = the disk end in case of zfs and therefore revealing the issue. Another way to verify this hypothesis is to create separate (smaller) = zroot partition at the beginning of the disk. Having older system sort = of points towards the possibility. Another thing - have you checked for BIOS updates?=20 rgds, toomas >=20 >> Would the photos of the screen help? >=20 > Everything helps. > NB: please keep the mailinglist in the address list. There are more = knowledgeable people there. >=20 > Ronald. >=20 >=20 >> -----Original Message----- >> From: Ronald Klop [mailto:ronald-lists@klop.ws] >> Sent: 08 February 2017 12:27 >> To: FreeBSD-current@freebsd.org; Thomas Sparrevohn = >> Subject: Re: gptzfsboot trouble >>=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 >> Regards, >> Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"