Date: Thu, 2 May 2019 11:42:49 -0500 From: Kyle Evans <kevans@freebsd.org> To: Larry Rosenman <ler@lerctr.org> Cc: Warner Losh <imp@bsdimp.com>, FreeBSD Current <freebsd-current@freebsd.org>, owner-freebsd-current@freebsd.org Subject: Re: Mount Root fails: r347007 Message-ID: <CACNAnaFfscVdsqNSK1%2Bx%2BdPWP2qzcrgk=S%2BUcojm_C7hHU5JOw@mail.gmail.com> In-Reply-To: <5084541f31224d3fb91796f0b4096bb7@lerctr.org> References: <20190502040229.ysm45il3n2mdsfg6@ler-imac.local> <CANCZdfrUuYDAVEg3M9GbjBFv=Qb0JQc=h2HKQ_Aj%2BLP3CKoLwQ@mail.gmail.com> <e43fe27edd1761a39169c9e9f71185c0@lerctr.org> <CANCZdfq_OyFxkfL9zYDa7pdMeNQuQ%2B9ox2eVFyJvUH5aW6DjeQ@mail.gmail.com> <33e20e5367966cb4f5c2856f3eda192f@lerctr.org> <b9ecd1747f06dd0b5f90a5fa49988922@lerctr.org> <CANCZdfpe-fMWrEK-fkY1XdLpg%2Ba36nYO=FSJM71noXZ1uM0Y4w@mail.gmail.com> <4419741bbbc2fafe9efde97fb5bf6d8b@lerctr.org> <6fd7b2d4dcbbbe07a2e9639e3657906d@lerctr.org> <5084541f31224d3fb91796f0b4096bb7@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 2, 2019 at 11:40 AM Larry Rosenman <ler@lerctr.org> wrote: > > On 05/02/2019 11:34 am, Larry Rosenman wrote: > > On 05/02/2019 11:10 am, Larry Rosenman wrote: > >> On 05/02/2019 10:58 am, Warner Losh wrote: > >>> On Thu, May 2, 2019 at 9:54 AM Larry Rosenman <ler@lerctr.org> wrote: > >>> > >>>> On 05/02/2019 9:41 am, Larry Rosenman wrote: > >>>> > On 05/02/2019 9:24 am, Warner Losh wrote: > >>>> >> On Thu, May 2, 2019 at 7:40 AM Larry Rosenman <ler@lerctr.org> wrote: > >>>> >> > >>>> >>> On 05/02/2019 8:29 am, Warner Losh wrote: > >>>> >>> > On Wed, May 1, 2019 at 10:04 PM Larry Rosenman <ler@lerctr.org> > >>>> wrote: > >>>> >>> > > >>>> >>> >> Upgraded from r346487 to r347007, and when I reboot, I get a > >>>> mountroot > >>>> >>> >> prompt. If I answer it with the same BootFS I booted from > >>>> >>> >> (zfs:zroot/ROOT/r347007) it continues to boot, and run. > >>>> >>> >> > >>>> >>> >> Dmesg: https://www.lerctr.org/~ler/Boot-NoRoot.txt > >>>> >>> >> > >>>> >>> >> What else do we need? > >>>> >>> >> > >>>> >>> >> I did upgrade the EFI partitions, and the freebsd-boot partitions > >>>> >>> >> and that did *NOT* change anything. > >>>> >>> >> > >>>> >>> >> Ideas? > >>>> >>> >> > >>>> >>> > > >>>> >>> > BIOS or UEFI booting? > >>>> >>> > >>>> >>> UEFI boot. > >>>> >>> > >>>> >> > >>>> >> So no change to \efi\boot\bootx64.efi (or whatever you are booting? > >>>> >> > >>>> >> Can you get the output of 'show' in the boot loader? > >>>> >> > >>>> >> Also, is there a way you can try one or two of the versions in between > >>>> >> 346487 and 347007 to try to narrow the changes down a bit? > >>>> >> > >>>> >> Warner > >>>> > > >>>> > show output in 4 screenshots: > >>>> > https://www.lerctr.org/~ler/FreeBSD/NO-BOOT/ > >>>> > > >>>> > What's the easiest way to try some of the other revisions? And which > >>>> > would > >>>> > you suggest? (I'm set up for meta-mode). > >>>> working with Kyle Evans on IRC, and backing /boot/loader.efi to > >>>> r346487 > >>>> lets the system boot > >>>> normally. > >>>> > >>> > >>> OK. I noticed vfs.root.mountfrom wasn't set. Can you see if it's set > >>> in > >>> your successfully booted system with kenv? > >>> > >> > >> 2 things: r346675 still works, and vfs.root.mountfrom *IS* set. > > r346879 does *NOT* work. Stepping back to r346759 > r346759 *WORKS*. So it's r346879 that breaks it. > Hi, Head back to -head and try applying [0] -- this block was accidentally reintroduced, and I wouldn't be surprised if the double-initialization has some weird side effect. [0] https://people.freebsd.org/~kevans/loader.diff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaFfscVdsqNSK1%2Bx%2BdPWP2qzcrgk=S%2BUcojm_C7hHU5JOw>