Date: Sun, 24 Sep 2017 15:44:36 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Dying SD memory? handle_workitem_freefile: got error 5 while accessing filesystem Message-ID: <20170924124436.GU2271@kib.kiev.ua> In-Reply-To: <20170924141926.4c6876dd@thor.intern.walstatt.dynvpn.de> References: <20170924093151.2edfeeff@thor.intern.walstatt.dynvpn.de> <20170924075238.GS2271@kib.kiev.ua> <20170924141926.4c6876dd@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 24, 2017 at 02:19:26PM +0200, O. Hartmann wrote: > Am Sun, 24 Sep 2017 10:52:38 +0300 > Konstantin Belousov <kostikbel@gmail.com> schrieb: > > > On Sun, Sep 24, 2017 at 09:31:51AM +0200, O. Hartmann wrote: > > > Running a NanoBSD application on a small PCEngine device, feeding the box with a > > > CURRENT (FreeBSD 12.0-CURRENT #33 r323958: Sat Sep 23 22:19:57 CEST 2017 amd64), > > > booting from a SD memory card. > > > > > > Recently, when saving configuration changes on the SD memory card, I receive these > > > strange errors: > > > > > > [...] > > > checksum failed: cg 0, cgp: 0xb478d1d5 != bp: 0x874608df > > > checksum failed: cg 12, cgp: 0xe626d67c != bp: 0x7360c12a > > > checksum failed: cg 0, cgp: 0xb478d1d5 != bp: 0x874608df > > > handle_workitem_freefile: got error 5 while accessing filesystem > > > checksum failed: cg 12, cgp: 0xe626d67c != bp: 0x7360c12a > > > handle_workitem_freefile: got error 5 while accessing filesystem > > > [...] > > > > > > I do not use MMCCAM in the kernel, but as far as I know, the problem occured in the > > > same time frame. > > > > > > The question is: is the SD memory about to die and is to be replaced or is this a bug > > > introduced with the new MMCCAM stuff recently? > > > > The messages you see about 'checksum_failed' are due to recently added > > UFS feature where cylinder group blocks are checksummed, and the checksum > > is verified against the known one stored on the volume. > > > > Were there kernel messages about disk I/O errors before that (as opposed > > to UFS errors about checksums and SU complains) ? > > Hello, > > no, there were no errors before. The small box is updated on a frequent basis, so I'm > sure there were no errors like those before or any other kind regarding I/O. > > I recall having read the commit description about the UFS2 enhancement. > > The NanoBSD image is created using UFS2/GPT partitioning scheme, if this is important to > know. Try to read the SD card on pre-checksum kernel. If you can read it, verify that the files are not damaged. This is a way to check whether your SD card or controller provides the wrong data to host.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170924124436.GU2271>