From: Richard Weinberger <richard.weinberger@gmail.com>
To: JH <jupiter.hce@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: How the bad blocks occured in despite MTD manages the bad blocks
Date: Wed, 2 Oct 2019 18:13:10 +0200 [thread overview]
Message-ID: <CAFLxGvxg3dYoiiTy7=vNwC75s529akqx0DO3ozLrP_TbhATr_g@mail.gmail.com> (raw)
In-Reply-To: <CAA=hcWSR52BJB4+k2k4CwLTQUVmvJvR=bjRx6kqe2aar-PH21w@mail.gmail.com>
On Wed, Oct 2, 2019 at 12:35 PM JH <jupiter.hce@gmail.com> wrote:
>
> Hi,
>
> My understinding is that MTD manages the NAND bad blocks, but can the
> MTD prevent bad blocks happening?
It does not. UBI does by applying wear-leveling.
> My iMX6 NAND device was only up and running about a month, it now
> failed to boot from NAND due to the bad blocks:
Why do you think so?
> Questions:
>
> (a) what could be common cause to trigger bad blacks?
Mostly due to block aging.
> (b) if I reflush the NAND will the bad blacks recovered or just mapped
> it to bad block list?
A bad block will be bad forever.
> .......
> Bad block table found at page 131008, version 0x01
> Bad block table found at page 130944, version 0x01
Having a bad block table is nothing bad.
> ................
> [FAILED] Failed to mount Kernel Debug File System.
> [FAILED] Failed to mount Temporary Directory (/tmp).
> [FAILED] Failed to start Remount Root and Kernel File Systems.
> [FAILED] Failed to mount /var/volatile.
> [FAILED] Failed to mount FUSE Control File System.
This lines are useless. Why exactly is it failing? And *what* fails?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-10-02 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 10:35 How the bad blocks occured in despite MTD manages the bad blocks JH
2019-10-02 16:09 ` Steve deRosier
2019-10-02 16:13 ` Richard Weinberger [this message]
2019-10-03 11:14 ` JH
2019-10-03 13:28 ` Richard Weinberger
2019-10-03 21:26 ` JH
2019-10-03 23:44 ` Steve deRosier
2019-10-04 6:36 ` JH
2019-10-05 8:38 ` Richard Weinberger
2019-10-05 21:56 ` JH
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='CAFLxGvxg3dYoiiTy7=vNwC75s529akqx0DO3ozLrP_TbhATr_g@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=jupiter.hce@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).