From owner-freebsd-current@freebsd.org Thu May 2 16:43:26 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DD6D159AB0D; Thu, 2 May 2019 16:43:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 052E4966CC; Thu, 2 May 2019 16:43:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id A1125D6DE; Thu, 2 May 2019 16:43:25 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f172.google.com with SMTP id r72so2779016ljb.9; Thu, 02 May 2019 09:43:25 -0700 (PDT) X-Gm-Message-State: APjAAAVJcEZAMRGoF3ofLRLamEeFIlwNAnTvFm583HzN+E7HcGnA+ERJ IiAk2oPKxvHqlUNjj+H2wCJEiKGF1BHgX1swZIs= X-Google-Smtp-Source: APXvYqzDetXimxuy/YVmPalo3VTJ7soqMrUtOoXX3fIsmnd4+Hp/Sa4YWDA7gicUT2gCiAJnaFUtW8r4kI6Uo8s48MI= X-Received: by 2002:a2e:456:: with SMTP id 83mr2429998lje.77.1556815404146; Thu, 02 May 2019 09:43:24 -0700 (PDT) MIME-Version: 1.0 References: <20190502040229.ysm45il3n2mdsfg6@ler-imac.local> <33e20e5367966cb4f5c2856f3eda192f@lerctr.org> <4419741bbbc2fafe9efde97fb5bf6d8b@lerctr.org> <6fd7b2d4dcbbbe07a2e9639e3657906d@lerctr.org> <5084541f31224d3fb91796f0b4096bb7@lerctr.org> In-Reply-To: <5084541f31224d3fb91796f0b4096bb7@lerctr.org> From: Kyle Evans Date: Thu, 2 May 2019 11:42:49 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Mount Root fails: r347007 To: Larry Rosenman Cc: Warner Losh , FreeBSD Current , owner-freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 052E4966CC X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.994,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 02 May 2019 16:43:26 -0000 On Thu, May 2, 2019 at 11:40 AM Larry Rosenman 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 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 wrote: > >>>> >> > >>>> >>> On 05/02/2019 8:29 am, Warner Losh wrote: > >>>> >>> > On Wed, May 1, 2019 at 10:04 PM Larry Rosenman > >>>> 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