Date: Thu, 04 May 2017 19:18:13 +0300 From: Toomas Soome <tsoome@me.com> To: current@freebsd.org Cc: Ngie Cooper <yaneurabeya@gmail.com>, "Michael W. Lucas" <mwlucas@michaelwlucas.com> Subject: Re: old snapshot install images? Message-ID: <46A1AE01-8534-4093-8C95-0ED88209B8FC@me.com> In-Reply-To: <2C0A4513-FDC4-440E-A5DD-E6F15F9F7EF2@me.com> References: <20170502191531.GA10288@mail.michaelwlucas.com> <E3394CDC-4260-41E3-8C89-628F5132B08B@gmail.com> <20170503163424.GA18325@mail.michaelwlucas.com> <80F20120-06DF-4BC9-B317-F77B54512A8F@gmail.com> <20170503164150.GB18325@mail.michaelwlucas.com> <FECE86AF-F1D0-4C64-AC2C-C8882A8D32EE@gmail.com> <D1E7B1C7-0590-4A21-AC8F-B711E2ADD6EC@me.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <tsoome@me.com> wrote: >=20 >>=20 >> On 3. mai 2017, at 21:23, Michael W. Lucas <mwlucas@michaelwlucas.com = <mailto:mwlucas@michaelwlucas.com>> 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 = <mwlucas@michaelwlucas.com> 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 = <http://www-old.michaelwlucas.com/zm.sh>; = <http://www-old.michaelwlucas.com/zm.sh = <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 <mailto:freebsd-current@freebsd.org> = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current = <https://lists.freebsd.org/mailman/listinfo/freebsd-current>; > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org = <mailto:freebsd-current-unsubscribe@freebsd.org>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46A1AE01-8534-4093-8C95-0ED88209B8FC>