From: Jef Driesen <jef.driesen@niko.eu>
To: JH <jupiter.hce@gmail.com>, linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Corruped NAND booting for all devices
Date: Wed, 5 Feb 2020 09:12:17 +0100 [thread overview]
Message-ID: <09505ab3-a51f-e0aa-1610-1ea1f106eec7@niko.eu> (raw)
In-Reply-To: <CAA=hcWTmUFRnxH7XY_040QG0oiUErJ84-mZQ3Zbfaaj7-TMFtQ@mail.gmail.com>
On 2/5/20 2:43 AM, JH wrote:
> It is a bad day we have 5 devices failed NAND booting all of certain
> today. The 5 devices running kernel 4.19.75 on iMX6ULL customized
> board, the devices had been running for weeks, the device DC power is
> supplied from AC via ADC and regulator, we turned power on and off
> several times when installing those test devices to test boxes in the
> last couple of days without problems, then they all failed together
> mysteriously today. It could not complete the booting to Linux user
> space, so I am not able to log into the user space to check and to
> debug it.
>
> ...
> [ 5.915558] UBIFS (ubi0:0): recovery needed
> [ 6.777033] UBIFS (ubi0:0): recovery deferred
> [ 6.782640] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0,
> name "rootfs_data", R/O mode
>
> ...
>
> [FAILED] Failed to mount /var/volatile.
> See 'systemctl status var-volatile.mount' for details.
> [DEPEND] Dependency failed for Bind mount volatile /var/cache.
> [DEPEND] Dependency failed for Bind mount volatile /srv.
> [DEPEND] Dependency failed for Bind mount volatile /var/spool.
> [DEPEND] Dependency failed for Bind mount volatile /var/lib.
At first sight, it looks you have a read-only ubifs filesystem, with an
overlay filesystem backed by another read-write ubifs filesystem? And
that read-write filesystem fails to mount after a power failure?
In that case, this sounds very similar to the problem I reported last week:
http://lists.infradead.org/pipermail/linux-mtd/2020-January/093542.html
Jef
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-02-05 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 1:43 Corruped NAND booting for all devices JH
2020-02-05 2:32 ` Steve deRosier
2020-02-05 7:58 ` JH
2020-02-05 17:06 ` Steve deRosier
2020-02-05 8:12 ` Jef Driesen [this message]
2020-02-06 0:49 ` JH
2020-02-06 1:40 ` Steve deRosier
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=09505ab3-a51f-e0aa-1610-1ea1f106eec7@niko.eu \
--to=jef.driesen@niko.eu \
--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).