From: JH <jupiter.hce@gmail.com>
To: Jef Driesen <jef.driesen@niko.eu>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Corruped NAND booting for all devices
Date: Thu, 6 Feb 2020 11:49:36 +1100 [thread overview]
Message-ID: <CAA=hcWQb-ok9u3Fa8ukBENE4peJaw=MEegT0-sMeXVWJrTinyA@mail.gmail.com> (raw)
In-Reply-To: <09505ab3-a51f-e0aa-1610-1ea1f106eec7@niko.eu>
Hi Jef,
On 2/5/20, Jef Driesen <jef.driesen@niko.eu> wrote:
>> [ 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?
I did notice the R/O mode, it was never in previous hardware revision,
the MTD partition for UBI is always RW, I did not know where is that
from, since the MTD partitions and installation was performed by our
hardware contractor, I don't believe it could be my Yocto image to
change it, but correct me, I could be wrong.
> 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
Interesting, good to know there is an issue here,
I guess the question here, firstly why we had the RO ubifs filesystem
backed by an overlay RW ubifs filesystem in the first place, secondly
is it an MTD bug or is it our fault to set up wrong RO and overlay RW
ubifs?
I'll keep an eye on it.
Thank you so much for sharing your information.
Kind regards,
- jh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-02-06 0:50 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
2020-02-06 0:49 ` JH [this message]
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='CAA=hcWQb-ok9u3Fa8ukBENE4peJaw=MEegT0-sMeXVWJrTinyA@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=jef.driesen@niko.eu \
--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).