linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: JH <jupiter.hce@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Unable to mount root fs (UBIFS volume)
Date: Sat, 15 Feb 2020 08:17:33 +0100	[thread overview]
Message-ID: <CAFLxGvwKX5y7ZUR+Kv9=fBM-1cC--HtTYPq8Te=pK4MqW7LKHw@mail.gmail.com> (raw)
In-Reply-To: <CAA=hcWQY82OCzv9Pscb2E+8gV0rQ-YRoEaALZ9VV2=0mCoQK_Q@mail.gmail.com>

On Sat, Feb 15, 2020 at 4:09 AM JH <jupiter.hce@gmail.com> wrote:
>
> Hi,
>
> I am running MTD on customized imx6ull evk board, the root is a UBIFS
> volume, installed from s ubinize image.
>
> If I boot from a ramdisk to Linux, I could run ubiattach -p /dev/mtd2
> and mount -t ubifs -r -v ubi0:rootfs-volume /mnt in ramdisk Linux, but
> it failed in NAND kernel boot, looks like that the kernel was not able
> to attach the mtd device or not able to mount to the rootfs-volume, do
> I need to pass more parameters to kernel? Or what could I be missing
> in the u-boot bootargs setup?
>
> => setenv bootargs "console=ttymxc0,115200 earlycon
> mtdparts=gpmi-nand:1m(boot),1m(ubootenv),-(storage)
> root=storage:rootfs-volume ro ubi.mtd=2,2048 noinitrd rootfstype=ubifs
> mem=256M rootwait=1"
>

[...]

> [    3.206295] UBI error: cannot open mtd 2, error -19

There is no mtd2.

-- 
Thanks,
//richard

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

  reply	other threads:[~2020-02-15  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15  3:09 Unable to mount root fs (UBIFS volume) JH
2020-02-15  7:17 ` Richard Weinberger [this message]
2020-02-15  7:36   ` JH
2020-02-15 10:12   ` JH
2020-02-15 12:40     ` JH
2020-02-16 10:19       ` 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='CAFLxGvwKX5y7ZUR+Kv9=fBM-1cC--HtTYPq8Te=pK4MqW7LKHw@mail.gmail.com' \
    --to=richard.weinberger@gmail.com \
    --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).