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

[JH <jupiter.hce@xxxxxxxxx>]

On 10/5/19, Richard Weinberger <richard.weinberger@xxxxxxxxx> wrote:
>> [    6.057136] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0),
>> UUID E9F1667C-8AC1-4030-BB1A-9C5341482A61, small LPT model
>> [    6.074491] VFS: Mounted root (ubifs filesystem) on device 0:13.
>
> So, UBIFS is happy and mounts cleanly.

Oh good, relieved.

>> [    8.732692] systemd[126]: sys-kernel-debug.mount: Failed to execute
>> command: No such file or directory
>> [    8.742715] systemd[128]: sys-fs-fuse-connections.mount: Failed to
>> execute command: No such file or directory
>
> Some files are missing but it does not look like a UBIFS corruption.
> In case of corruption (such as dead directory entry) UBIFS would cry out
> loud.
>
> I don't see a problem which points to the storage stack.

So if the UBIFS was not corrupted, NAND was not damaged, is my
assertion rational that software / kernel was not the cause to break
the system and device down?

Thank you very much Richard.

Kind regards,

- jh

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