From owner-freebsd-current@freebsd.org Thu May 4 16:18:23 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 691CAD5D6F7 for ; Thu, 4 May 2017 16:18:23 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 44F21F3F for ; Thu, 4 May 2017 16:18:23 +0000 (UTC) (envelope-from tsoome@me.com) Received: by mailman.ysv.freebsd.org (Postfix) id 415CFD5D6F4; Thu, 4 May 2017 16:18:23 +0000 (UTC) Delivered-To: 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 40EBED5D6F3 for ; Thu, 4 May 2017 16:18:23 +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 128E9F3E for ; Thu, 4 May 2017 16:18:23 +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 <0OPF00I00RPISQ00@st13p35im-asmtp002.me.com> for current@freebsd.org; Thu, 04 May 2017 16:18:18 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1493914698; bh=/hxAjKCL4RVB9QNzWCpqGh/OE1Z72DdPnSDzu5k/bqw=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=HGXchBVEIbe1DeXnOW8v7PB7mbP4bPcimI18xnEWrB4BxVuwLAJkmmxpoWQd/sP/2 KY0X8rbCJFAJ0zoZKfkmQhnTwCi3q2XkdcT2GpD8nzNPRDfQJS2JLER4AvTuc47MyH 1PCq/qA1PoJnBIAnG5iBUT7K1iBiOf2E8DN+8fTCjg4ikGu7U6viynpdhJqw/zEld0 rBe7XEF1q2kasbOU0kfFf9ajiZMfM0tiW6TQjM8rWBNB24vNSJNOCL4CbvQtb6Fz48 OI+efXVZvzWGv9IaU1laMiQdogPEBAtzfIappawDIdJwED3RMVqzQ+rzSAObH+zh6H dD//z9BFM0lAw== 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 <0OPF00JMURYF8N40@st13p35im-asmtp002.me.com>; Thu, 04 May 2017 16:18:17 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-04_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=17 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1705040249 From: Toomas Soome Message-id: <46A1AE01-8534-4093-8C95-0ED88209B8FC@me.com> MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: old snapshot install images? Date: Thu, 04 May 2017 19:18:13 +0300 In-reply-to: <2C0A4513-FDC4-440E-A5DD-E6F15F9F7EF2@me.com> Cc: Ngie Cooper , "Michael W. Lucas" To: current@freebsd.org References: <20170502191531.GA10288@mail.michaelwlucas.com> <20170503163424.GA18325@mail.michaelwlucas.com> <80F20120-06DF-4BC9-B317-F77B54512A8F@gmail.com> <20170503164150.GB18325@mail.michaelwlucas.com> <20170503180602.GA18700@mail.michaelwlucas.com> <828E5321-056C-4ABC-BBBB-B28CCD1079C9@me.com> <20170503182301.GA18781@mail.michaelwlucas.com> <2C0A4513-FDC4-440E-A5DD-E6F15F9F7EF2@me.com> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Thu, 04 May 2017 16:18:23 -0000 just for an update: apparently this was buggy BIOS and the BIOS update = did fix it. The curious fact was that the gptzfsboot INT13 calls were = failing, while pmbr INT13 calls were doing OK also the usb stick boot = had no apparent problems. rgds, toomas > On 3. mai 2017, at 21:53, Toomas Soome wrote: >=20 >>=20 >> On 3. mai 2017, at 21:23, Michael W. Lucas > wrote: >>=20 >> On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote: >>>=20 >>>> On 3. mai 2017, at 21:06, Michael W. Lucas = wrote: >>>>=20 >>>> On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote: >>>>> There was many issues fixed step by step and some fixes for = particular problem did reveal next one (at least in some systems), and = indeed, it can cause some problems if you are caught in middle of = updates. =46rom my point of view, the most important question is if the = current =E2=80=9Ccurrent=E2=80=9D is ok:) >>>>=20 >>>>=20 >>>> Agreed 500%. >>>>=20 >>>> The latest snapshot is NOT ok. >>>>=20 >>>=20 >>> What is the error there? >>=20 >>=20 >> error 1 >> error 1 >> gptzfsboot: error 1 lba 4294967288 >> gptzfsboot: error 1 lba 1 >> gptzfsboot: no ZFS pools located, can't boot >>=20 >> My first thought was that the BIOS was looking at a different drive, >> not the SATADOMs, so I disabled booting from all the spinning drives >> in the BIOS. >>=20 >> On a related note: my script at = http://www-old.michaelwlucas.com/zm.sh = = > >> also gives the same error at boot. >>=20 >=20 > well, yea, i know what it is. sigh. Welcome to the x86 hell. >=20 > error 1 is: Invalid command. And it is resulting firstly from = drvsize() (the lone =E2=80=9Cerror 1=E2=80=9D messages) and then from = drvread(). Now the question is, did you do the install from usb stick or = cd, and has this system booted fbsd from the disk before? >=20 > The question is up because, the boot2 is only using INT13 extended = read (INT13 EAX=3D0x4200) and INT13 EAX=3D0x4800 to get disk size; if = the read is now getting error but was working before, it is pointing = towards the error from 0x4800 (drvsize) is triggering the error with = read - meaning we should probably attempt the disk reset on error. >=20 > As an first take on possible fix, I think we need to address the = drvsize() to get size from INT13 0x800 as biosdisk.c bd_int13probe() = does, and reset the disk on error. And if this is not enough, then check = further. >=20 > However, since you have the system to test with, the testing is all on = you;) So if you are up to the task, poke me in private (mail or irc) and = we can work it out - no need to kill the list with all that noise;) >=20 > rgds, > toomas=20 >=20 > _______________________________________________ > 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 = "