From owner-freebsd-fs@freebsd.org Thu Nov 1 15:54:33 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98F1D10F6E86 for ; Thu, 1 Nov 2018 15:54:33 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A6347CF2C; Thu, 1 Nov 2018 15:54:32 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id wA1FsU7R018656; Thu, 1 Nov 2018 16:54:30 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 6C888F4B; Thu, 1 Nov 2018 16:54:30 +0100 (CET) Subject: Re: boot2 / loader can not check superblock checksum and refuse to boot, but fsck_ffs doesn't see problems To: lev@freebsd.org, FreeBSD Filesystems References: From: Harry Schmalzbauer Organization: OmniLAN Message-ID: Date: Thu, 1 Nov 2018 16:54:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Thu, 01 Nov 2018 16:54:30 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 15:54:33 -0000 Am 01.11.2018 um 13:17 schrieb Lev Serebryakov: > I have NanoBSD image built from head/r339933, which passes all checks > on other system: "fsck_ffs" passes, it could be mounted without > problems, everything could be read. > > But when I try to boot from it, boot2 (or loader?) complains about > failed superblock checksum several times (for each copy?), like this: > > Superblock check-hash failed: recorded check-hash 0xcfa0ae67 != computed > check-hash 0x21993fb > > ALL these messages contains SAME "recorded" and "compuded" hashes, so > it doesn't look like corrupted flash. > > Looks like boot2/loader wrongly calculate hash... I think I've had the same / a similar problem some dozend moons ago, which I could track down to a 'newfs' induced problem.  'newfs'ing the same partition [/md(4) deivce  without partitions in my case] multiple times (4 times) triggered that problem, as far as I remember. Can't find any notices :-( And haven't investigated further :-( Maybe it's worth checking if your problem is also related to the number of newfs runs – unfortunately I can't remember if it really was boot2 where my – at least very similar – error came from. Other symptoms match – no problem by fsck_ffs(8) found. -harry