From owner-freebsd-current@freebsd.org Wed Feb 8 12:26:46 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 E9FC3CD66F0 for ; Wed, 8 Feb 2017 12:26:46 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (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 B3946F30 for ; Wed, 8 Feb 2017 12:26:42 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cbRKZ-00006q-Ha; Wed, 08 Feb 2017 13:26:39 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: FreeBSD-current@freebsd.org, "Thomas Sparrevohn" Subject: Re: gptzfsboot trouble References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> Date: Wed, 08 Feb 2017 13:26:38 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: c09395f469c52153b963e4ff2d10f427 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:26:47 -0000 On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn wrote: > Hi all > > > 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 > > > 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 > > > I have some images - but they are 2 bit for the mailing list ;-) Can it be related to this issue? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 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. As you say UFS works, the bug might be in the gptzfsboot code, because that is not used for UFS. Regards, Ronald.