From: Richard Weinberger <richard@nod.at>
To: t kevin <kevint324@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: Get error -74 (ECC error) during ubiattach
Date: Sat, 20 Dec 2014 10:27:13 +0100 [thread overview]
Message-ID: <549540F1.4040107@nod.at> (raw)
In-Reply-To: <CAOx4H9Ds5_ZSwwKRGcEzJc_k+CTeGyeeWRWAyo5mHV5rVEnSCA@mail.gmail.com>
Hi!
Am 20.12.2014 um 04:43 schrieb t kevin:
> So for uncorrectable ECC error ( e.g., bad block) the only way out is
> to do a fresh ubiformat?
> For device like harddisk you get bad blocks all the time, if it is not
> in the critical sector things can be fixed as much as possible by fsck
> so I was looking for something like fsck.ubifs.
An uncorrectable ECC error means that more bits flipped than your ECC
algorithm can fix.
All you can do is trying to erase the block and hoping that it will
work again.
>>> Is it because the background thread "ubi_bgt2d" has not started yet so
>>> no one could do the data scrubbing during ubiattach stage?
>>
>> UBI does scrubbing if it faces bit-flips (correctable ECC errors).
>>
>>> Is it possible to do something like a fsck.ubifs to fix this issue?
>>
>> No. PEB 404 is bad.
>> Is it always the same block?
>
> Yes, it is always the same block. What got me confused is below
> message telling bad PEBs is still 0.
> UBI: number of good PEBs: 1920
> UBI: number of bad PEBs: 0
> UBI: number of corrupted PEBs: 0
I agree that this is a bit strange.
UBI treats a block as bad if it has a bad block marker or it detects
so while scrubbing.
But it can also happen that you get a block with bad ECC if a powercut happened
while erasing it.
This is why UBI does not automatically mark it as bad while scanning.
Such a block will be erased.
Thanks,
//richard
next prev parent reply other threads:[~2014-12-20 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 12:24 Get error -74 (ECC error) during ubiattach t kevin
2014-12-19 13:49 ` Richard Weinberger
2014-12-20 3:43 ` t kevin
2014-12-20 9:27 ` Richard Weinberger [this message]
2014-12-20 10:00 ` Oleksij Rempel
2014-12-20 10:02 ` Richard Weinberger
2014-12-20 10:05 ` Oleksij Rempel
2014-12-20 10:12 ` Richard Weinberger
2014-12-20 10:16 ` Oleksij Rempel
2014-12-20 14:05 ` Oleksij Rempel
2014-12-19 15:31 ` Tanya Brokhman
2014-12-20 3:48 ` t kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=549540F1.4040107@nod.at \
--to=richard@nod.at \
--cc=kevint324@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).