From owner-freebsd-current@freebsd.org Wed Feb 8 12:53:48 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 004EDCD6D52 for ; Wed, 8 Feb 2017 12:53:48 +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 BED431D7C for ; Wed, 8 Feb 2017 12:53:47 +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 1cbRkn-0005hH-Dk; Wed, 08 Feb 2017 13:53:45 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Thomas Sparrevohn" , "FreeBSD Current" Subject: Re: gptzfsboot trouble References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002001d28207$d0d493a0$727dbae0$@btinternet.com> Date: Wed, 08 Feb 2017 13:53:44 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <002001d28207$d0d493a0$727dbae0$@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: 67ca9281b58cf5c8a5b2b1d981559170 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:53:48 -0000 On Wed, 08 Feb 2017 13:35:22 +0100, Thomas Sparrevohn wrote: > > What would help? Takes a little while as I have to rebuild to 11-RELEASE > each time? 12-CURRENT cashed either before the boot menu or immediately > after which could be unrelated - I have photos but they are quite big > e.g. > 4 MB You can't mail them as attachment, but you might put them on Dropbox or something else and link to them. > I suggest - > > 1) Single disk ZFS pool on the 320GB disks should allow for faster > dd wipes if needed > 2) Run 11-RELEASE initially in case the 12-CURRENT issues are > unrelated > > I send > Dmesg output > Gpart show > Gpart list > Zpool status > Camcontrol devlist > Anything else? That is a really good start for people to look further on. Did you update your boot blocks while updating? Regards, Ronald. > > > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Ronald Klop > Sent: 08 February 2017 12:27 > To: FreeBSD-current@freebsd.org; Thomas Sparrevohn > > Subject: Re: gptzfsboot trouble > > 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. > _______________________________________________ > 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"