Date: Wed, 11 Sep 2019 08:59:58 -0700 From: John Kennedy <warlock@phouka.net> To: "Jack L." <xxjack12xx@gmail.com> Cc: Terry Kennedy <TERRY@glaver.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Anyone else seeing hangs at "Trying to mount root" after recent commits? Message-ID: <20190911155958.GA22817@phouka1.phouka.net> In-Reply-To: <CALeGphwTP6rWbXqoxcD1PkcA8f3Z8BUKi=aGK3jSA22S0_OU1A@mail.gmail.com> References: <01RBAL5781V8000QXF@glaver.org> <CALeGphwTP6rWbXqoxcD1PkcA8f3Z8BUKi=aGK3jSA22S0_OU1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 11, 2019 at 01:38:14AM -0700, Jack L. wrote: > Yes, I upgraded 2 systems and both experience the same behavior > Dell R610 and Dell 7010 here. Afraid to upgrade any others For what it's worth, I have a Dell Optiplex 9020 booting r352118: FreeBSD FreeBSD 12.1-PRERELEASE #105 r352118+b6945c1f5542(stable/12) That's at least after r352025, which may help your bisect. Currently crunching r352202. I boot off of ZFS (vs UFS), but that might be another data point for someone. > On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy <TERRY@glaver.org> wrote: > > I have a system I updated from r352025 (which worked fine) to r352200. > > Any attempt to boot r352200 results in the system just sitting there after > > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > > message. Nothing further, not even after a half hour. The console is non- > > responsive (not that I'd really expect anything, but...). > > > > This persists across multiple resets, power cycles, etc. Booting the > > previous r352025 works fine, as expected. > > > > Before I start trying to bisect this, is anyone else seeing this? amd64 > > on a standard Dell PowerEdge R730 if that matters.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190911155958.GA22817>