linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: Richard Weinberger <richard.weinberger@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: Thu, 3 Oct 2019 21:14:20 +1000	[thread overview]
Message-ID: <CAA=hcWTzAMU5GvGzcG2Ha5RH_=QUTEAa3gZkMoe=cgtZGG+h+Q@mail.gmail.com> (raw)
In-Reply-To: <CAFLxGvxg3dYoiiTy7=vNwC75s529akqx0DO3ozLrP_TbhATr_g@mail.gmail.com>

Thanks Richard and Steve.

On 10/3/19, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> 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.

I should mention it is the rootfs using ubifs, the kernel is 5.1.

>> 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?

I was told by hardware engineer, it was broken by bad block problem.

>> (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.

So that was not the cause to break the boot.

>> ................
>> [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?

After those lines, the boot stopped in an emergent mode in a prompt to
suggest to log in by Ctl-D, but that could not work, I was not able to
log into the file system, nor can I get kernel log. From your
experience, what could be likely the causes, hardware or software?

Thanks Steve and Richard.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-10-03 11:14 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
2019-10-03 11:14   ` JH [this message]
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='CAA=hcWTzAMU5GvGzcG2Ha5RH_=QUTEAa3gZkMoe=cgtZGG+h+Q@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    /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).