Re: How the bad blocks occured in despite MTD manages the bad blocks

[Richard Weinberger <richard.weinberger@xxxxxxxxx>]

On Wed, Oct 2, 2019 at 12:35 PM JH <jupiter.hce@xxxxxxxxx> 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/