Date: Wed, 1 Jun 2022 14:45:51 -0700 From: Robert Montano <irontree043111@gmail.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Free BSD <freebsd-arm@freebsd.org> Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <CABzjivdzsyfRe-eS84nzn39784=5nTAH7dPVVEeUHv2ANNMHaA@mail.gmail.com> In-Reply-To: <20220601214401.GA42494@www.zefox.net> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <20220601214401.GA42494@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000bfbda105e069d016 Content-Type: text/plain; charset="UTF-8" I'm a newbie to all of this. Sorry I don't really understand the nomenclature! On Wed, Jun 1, 2022, 2:44 PM bob prohaska <fbsd@www.zefox.net> wrote: > On Wed, Jun 01, 2022 at 09:17:10AM -0700, Mark Millard wrote: > > On 2022-Jun-1, at 08:41, bob prohaska <fbsd@www.zefox.net> wrote: > > > > > Since about 05/29 mountroot has been failing on a Pi3 self-hosting > -current, > > > using a usb mechanical hard disk. > > > > > > Anybody else seen this sort of behavior? > > > > You do not report much context. FreeBSD version? UFS? ZFS? > > -current, UFS. > > > > > However, there has been today (for main): > > > > git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity > checks when reading a superblock > > > > that is for fixing boot problems in UFS contexts. See: > > > > > https://lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html > > > > This is for fixes related to the 2022-May-27 change: > > > > ??? git: 076002f24d35 - main - Do comprehensive UFS/FFS superblock > integrity checks when reading a superblock. Kirk McKusick > > > > It sounds like there's some hope the trouble isn't purely local to my > machines. I'll just continue to update and hope for the best. A Pi3 > running -current as well as a Pi3 running stable/13 seem to be affected. > A Pi4 running -current works perfectly. All use UFS on mechanical > hard disks. > > FWIW, one boot attempt followed the mountroot failure > with a kernel panic and backtrace, but I inadvertently wiped > out the console transcript before I could post it. If that > happens again I'll take more care. > > Thanks to everyone who replied, especially Mark! > > bob > > > > it. > > --000000000000bfbda105e069d016 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">I'm a newbie to all of this. Sorry I don't really= understand the nomenclature!<div dir=3D"auto"><br></div><div dir=3D"auto">= <br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm= ail_attr">On Wed, Jun 1, 2022, 2:44 PM bob prohaska <<a href=3D"mailto:f= bsd@www.zefox.net">fbsd@www.zefox.net</a>> wrote:<br></div><blockquote c= lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;= padding-left:1ex">On Wed, Jun 01, 2022 at 09:17:10AM -0700, Mark Millard wr= ote:<br> > On 2022-Jun-1, at 08:41, bob prohaska <<a href=3D"mailto:fbsd@www.z= efox.net" target=3D"_blank" rel=3D"noreferrer">fbsd@www.zefox.net</a>> w= rote:<br> > <br> > > Since about 05/29 mountroot has been failing on a Pi3 self-hostin= g -current,<br> > > using a usb mechanical hard disk.=C2=A0 <br> > > <br> > > Anybody else seen this sort of behavior? <br> > <br> > You do not report much context. FreeBSD version? UFS? ZFS?<br> <br> -current, UFS. <br> <br> > <br> > However, there has been today (for main):<br> > <br> > git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integri= ty checks when reading a superblock<br> > <br> > that is for fixing boot problems in UFS contexts. See:<br> > <br> > <a href=3D"https://lists.freebsd.org/archives/dev-commits-src-main/202= 2-June/006977.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https:/= /lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html</a><= br> > <br> > This is for fixes related to the 2022-May-27 change:<br> > <br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0??? git: 076002f24d35 - main - Do comprehens= ive UFS/FFS superblock integrity checks when reading a superblock. Kirk McK= usick <br> > <br> <br> It sounds like there's some hope the trouble isn't purely local to = my<br> machines. I'll just continue to update and hope for the best. A Pi3<br> running -current as well as a Pi3 running stable/13 seem to be affected.<br= > A Pi4 running -current works perfectly. All use UFS on mechanical <br> hard disks. <br> <br> FWIW, one boot attempt followed the mountroot failure<br> with a kernel panic and backtrace, but I inadvertently wiped <br> out the console transcript before I could post it. If that<br> happens again I'll take more care.<br> <br> Thanks to everyone who replied, especially Mark!<br> <br> bob<br> <br> <br> <br> it. <br> <br> </blockquote></div> --000000000000bfbda105e069d016--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABzjivdzsyfRe-eS84nzn39784=5nTAH7dPVVEeUHv2ANNMHaA>