Date: Sat, 11 Feb 2023 20:35:24 -0800 From: bob prohaska <fbsd@www.zefox.net> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: fsck segfaults on rpi3 running 13-stable Message-ID: <20230212043524.GA19401@www.zefox.net> In-Reply-To: <9DC74DD9-9AA1-4822-B425-217AAC7DB3F5@yahoo.com> References: <20230211224057.GA17805@www.zefox.net> <9DC74DD9-9AA1-4822-B425-217AAC7DB3F5@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On Sat, Feb 11, 2023 at 06:57:41PM -0800, Mark Millard wrote: > On Feb 11, 2023, at 14:40, bob prohaska <fbsd@www.zefox.net> wrote: > > > While running buildworld on a Pi3 running 13-stable the machine > > panic'd. On restart using the previous kernel fsck failed with a > > segfault, which repeated when the disk was moved to a -current Pi3. > > > > In single user mode on -current the segfault message is > > > > .... > > 7912408300994173476 BAD I=74682090 > > 4313599915630302063 BAD I=74682090 > > -4473632163892877928 BAD I=74682090 > > 8068741989830080453 BAD I=74682090 > > 3857159125896022134 BAD I=74682090 > > -4354179704011695453 BAD I=74682090 > > 7611175298055105740 BAD I=74682090 > > 3985638883347136889 BAD I=74682090 > > -2495754894521232470 BAD I=74682090 > > 7739654885841380823 BAD I=74682090 > > INODE CHECK-HASH FAILED I=74999808 OWNER=1842251117 MODE=15044 > > fsck: /dev/da1s2d: Segmentation fault > > > > I gather this like unlikely to be recoverable, but it would be > > nice to understand what went wrong if possible. > > Did it produce a *.core file? > The 13-current host, looking at the 13-stable disk, reports root@www:~ # savecore -C -v /dev/da1s2b checking for kernel dump on device /dev/da1s2b mediasize = 2147483648 bytes sectorsize = 512 bytes magic mismatch on last dump header on /dev/da1s2b No dump exists Seemingly no file was made, or it got erased amid my fumbling. The corruption of the ailing disk is almost certainly in some part of /usr/obj or /usr/src. Is there any subterfuge that might allow me to simply delete, say, /usr/obj and then let the buildworld process re-populate it? Something along the lines of mount -o force /dev/da1s2d /mnt and then run rm -rf /mnt/obj then unmount and try fsck again. At this stage there's not much to be lost.... Thanks for replying! bob prohaskahelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230212043524.GA19401>