From nobody Sun Feb 12 04:35:24 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PDvlT5s79z3pM7k for ; Sun, 12 Feb 2023 04:35:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PDvlS5DJdz4JNn for ; Sun, 12 Feb 2023 04:35:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 31C4ZPv7019455 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 11 Feb 2023 20:35:25 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 31C4ZPbg019454; Sat, 11 Feb 2023 20:35:25 -0800 (PST) (envelope-from fbsd) Date: Sat, 11 Feb 2023 20:35:24 -0800 From: bob prohaska To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: fsck segfaults on rpi3 running 13-stable Message-ID: <20230212043524.GA19401@www.zefox.net> References: <20230211224057.GA17805@www.zefox.net> <9DC74DD9-9AA1-4822-B425-217AAC7DB3F5@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9DC74DD9-9AA1-4822-B425-217AAC7DB3F5@yahoo.com> X-Spamd-Result: default: False [-1.10 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[zefox.net]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PDvlS5DJdz4JNn X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Sat, Feb 11, 2023 at 06:57:41PM -0800, Mark Millard wrote: > On Feb 11, 2023, at 14:40, bob prohaska 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 prohaska