Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Nov 2018 19:10:03 +0300
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Harry Schmalzbauer <freebsd@omnilan.de>, FreeBSD Filesystems <freebsd-fs@freebsd.org>
Subject:   Re: boot2 / loader can not check superblock checksum and refuse to boot, but fsck_ffs doesn't see problems
Message-ID:  <d85bb7c2-3bb0-1791-c49b-6e093d8cb7e5@FreeBSD.org>
In-Reply-To: <a2354384-2a3a-58ee-9075-117ee23d7bc5@omnilan.de>
References:  <ed7fc03e-4601-1cff-5293-d3852ba25bd0@FreeBSD.org> <a2354384-2a3a-58ee-9075-117ee23d7bc5@omnilan.de>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--w7ENF4mcIfAdQseAw3S3ZeM93d4X15YBP
Content-Type: multipart/mixed; boundary="m5Izw3w6yiHx3v7ciQHs1ZI2hR7Va4tgY";
 protected-headers="v1"
From: Lev Serebryakov <lev@FreeBSD.org>
Reply-To: lev@FreeBSD.org
To: Harry Schmalzbauer <freebsd@omnilan.de>,
 FreeBSD Filesystems <freebsd-fs@freebsd.org>
Message-ID: <d85bb7c2-3bb0-1791-c49b-6e093d8cb7e5@FreeBSD.org>
Subject: Re: boot2 / loader can not check superblock checksum and refuse to
 boot, but fsck_ffs doesn't see problems
References: <ed7fc03e-4601-1cff-5293-d3852ba25bd0@FreeBSD.org>
 <a2354384-2a3a-58ee-9075-117ee23d7bc5@omnilan.de>
In-Reply-To: <a2354384-2a3a-58ee-9075-117ee23d7bc5@omnilan.de>

--m5Izw3w6yiHx3v7ciQHs1ZI2hR7Va4tgY
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 01.11.2018 18:54, Harry Schmalzbauer wrote:

> I think I've had the same / a similar problem some dozend moons ago,
> which I could track down to a 'newfs' induced problem.=C2=A0 'newfs'ing=
 the
> same partition [/md(4) deivce=C2=A0 without partitions in my case] mult=
iple
> 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 =E2=80=93 unfortunately I can't remember if it really was=
 boot2
> where my =E2=80=93 at least very similar =E2=80=93 error came from. Oth=
er symptoms match
> =E2=80=93 no problem by fsck_ffs(8) found.

 I'm using same md(4)-bakcing file for many-many times, yes (much more
than 4), but it is first time I got this problem. Ok, I'll re-create
backing file on image builder and try to create image again.

 But it looks like very strange bug.

--=20
// Lev Serebryakov


--m5Izw3w6yiHx3v7ciQHs1ZI2hR7Va4tgY--

--w7ENF4mcIfAdQseAw3S3ZeM93d4X15YBP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKSBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvbJVtfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5
NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c
R49yhA/43idsfFnANnn3Zi1Tsu5CWIKsCFOXWQulJdHVdw6LS9wfgiVZMAmRmuIA
dHGkRwR2AjhfRLbOgWn7ukZo6w3WFDOyZZi9rdjy+fuzZQ39gwFSH+vKw0qK9RZx
Gf+r9R58sB9ZOxQb6MB+QIdh+28moZm7lPMptJ+RgwPbiAVtiq1HsyIY0Z8qK+Y6
95lDLj++szJJidIHya6vCZcXXmtEIpcGc3bxWulu8TuQSe4w/9tJwtKy+d/d9BU2
n5Y/O5pxYX4PfKii1lG3zD0PMfI8KnC3jCBBi62NeXnZBixV4dWO/meK4kVXzax9
dJ8mOPt4xlBZ1EWgiclxYSYLcqAUa3pvNE/LHIiDcK86UcFbxXQXFmBMxujb2Ezn
ns1JaqWiyfwDI1rbbt9fRhZNO/Cerx5sPAV1pIhaWk4qCLh0fdTSXyNVU1KuBRO3
NfKSa2WjvL2KkNX/xMSO6jOMwC9g0VI2Z2PhfPFsDcDEmhCExrIKzszsXeY27fat
M1m7eQZLCRDbf1Cl76I+Ja711KTrwT39K55+s86ehC/XRC91WGCyVsWC89EHXF2L
EYMbEmWoZMXzZ2QauqiVSWIgC/hGXpBzVrM7JzDEPrOvU30lXjVjzm3GNr0lPiKJ
eCmcRwyxjiayNj2Kv9cQJG4GpqBu9JPhEWZ/ZfqvTQDu3p8oTw==
=H4SG
-----END PGP SIGNATURE-----

--w7ENF4mcIfAdQseAw3S3ZeM93d4X15YBP--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d85bb7c2-3bb0-1791-c49b-6e093d8cb7e5>