Date: Tue, 14 Jun 2022 14:15:32 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <50CE21C4-CBE5-4ECB-A27E-42B7AAF71822@yahoo.com> In-Reply-To: <20220613153325.GA12588@www.zefox.net> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <20220601214401.GA42494@www.zefox.net> <20220602045202.GA44686@www.zefox.net> <1B845A0C-EDDC-407C-96A8-AAF4E92C2A4D@yahoo.com> <20220613153325.GA12588@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Jun-13, at 08:33, bob prohaska <fbsd@www.zefox.net> wrote: > On Sat, Jun 11, 2022 at 06:52:42PM -0700, Mark Millard wrote: >> There was another UFS/FFS superblock integrity-check fix today. >> Time to try again? >>=20 >> The fix was . . . >>=20 >> The branch main has been updated by mckusick: >>=20 >> URL: = https://cgit.FreeBSD.org/src/commit/?id=3D800a53b445e7eb113ba193b1ac986312= 99178529 >>=20 >=20 > There still seems to be something wrong. It looked like git picked up = the > change, but after a build/install cycle I'm still seeing: >=20 >> . . . >>=20 >>=20 >=20 May be an appropriate problem-isolation test (not fix) would be to make a microsd card with an system somewhat older than all the recent superblock validation test additions. Depending on media types, you might need to use a USB media reader to look at the problem media with when booted from this older system. If that older system has no problems with looking at your problematical media, it would suggest that their are still more compatibility issues for the more modern superblock validation code. But, if that older system still has problems handling the problematical media, then the issue is something else with your media. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50CE21C4-CBE5-4ECB-A27E-42B7AAF71822>