All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pintu Agarwal <pintu.ping@gmail.com>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Phillip Lougher <phillip@squashfs.org.uk>,
	open list <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RESEND]: Kernel 4.14: UBIFS+SQUASHFS: Device fails to boot after flashing rootfs volume
Date: Mon, 31 May 2021 08:24:49 +0530	[thread overview]
Message-ID: <CAOuPNLigHdbu_OTpsFr7gq+nFK2Pv+4MUSrC6A6PfKfF1H1X3Q@mail.gmail.com> (raw)
In-Reply-To: <4304c082-6fc5-7389-f883-d0adfc95ee86@geanix.com>

On Tue, 25 May 2021 at 11:07, Sean Nyekjaer <sean@geanix.com> wrote:
> We are writing our rootfs with this command:
> ubiupdatevol /dev/ubi0_4 rootfs.squashfs
>
> Please understand the differences between the UBI and UBIFS. UBI(unsorted block image) and UBIFS(UBI File System).
> I think you want to write the squashfs to the UBI(unsorted block image).
>
> Can you try to boot with a initramfs, and then use ubiupdatevol to write the rootfs.squshfs.
>
Dear Sean, thank you so much for this suggestion.
Just a final help I need here.

For future experiment purposes, I am trying to setup my qemu-arm
environment using ubifs/squashfs and "nandsim" module.
I already have a working setup for qemu-arm with busybox/initramfs.
Now I wanted to prepare ubifs/squashfs based busybox rootfs which I
can use for booting the mainline kernel.
Is it possible ?
Are there already some pre-built ubifs images available which I can
use for my qemu-arm ?
Or, please guide me how to do it ?

I think it is more convenient to do all experiments with "nandsim"
instead of corrupting the actual NAND hardware.
If you have any other suggestions please let me know.


Thanks,
Pintu

WARNING: multiple messages have this Message-ID (diff)
From: Pintu Agarwal <pintu.ping@gmail.com>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Phillip Lougher <phillip@squashfs.org.uk>,
	open list <linux-kernel@vger.kernel.org>,
	 linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RESEND]: Kernel 4.14: UBIFS+SQUASHFS: Device fails to boot after flashing rootfs volume
Date: Mon, 31 May 2021 08:24:49 +0530	[thread overview]
Message-ID: <CAOuPNLigHdbu_OTpsFr7gq+nFK2Pv+4MUSrC6A6PfKfF1H1X3Q@mail.gmail.com> (raw)
In-Reply-To: <4304c082-6fc5-7389-f883-d0adfc95ee86@geanix.com>

On Tue, 25 May 2021 at 11:07, Sean Nyekjaer <sean@geanix.com> wrote:
> We are writing our rootfs with this command:
> ubiupdatevol /dev/ubi0_4 rootfs.squashfs
>
> Please understand the differences between the UBI and UBIFS. UBI(unsorted block image) and UBIFS(UBI File System).
> I think you want to write the squashfs to the UBI(unsorted block image).
>
> Can you try to boot with a initramfs, and then use ubiupdatevol to write the rootfs.squshfs.
>
Dear Sean, thank you so much for this suggestion.
Just a final help I need here.

For future experiment purposes, I am trying to setup my qemu-arm
environment using ubifs/squashfs and "nandsim" module.
I already have a working setup for qemu-arm with busybox/initramfs.
Now I wanted to prepare ubifs/squashfs based busybox rootfs which I
can use for booting the mainline kernel.
Is it possible ?
Are there already some pre-built ubifs images available which I can
use for my qemu-arm ?
Or, please guide me how to do it ?

I think it is more convenient to do all experiments with "nandsim"
instead of corrupting the actual NAND hardware.
If you have any other suggestions please let me know.


Thanks,
Pintu

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

  reply	other threads:[~2021-05-31  2:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOuPNLjgpkBh9dnfNTdDcfk5HiL=HjjiB9o_=fjrm+0vP7Re2Q@mail.gmail.com>
2021-05-14 11:41 ` Kernel 4.14: SQUASHFS error: unable to read xattr id index table Pintu Agarwal
2021-05-14 11:41   ` Pintu Agarwal
2021-05-14 12:37   ` [RESEND]: " Pintu Agarwal
2021-05-14 21:50     ` Phillip Lougher
2021-05-14 21:50       ` Phillip Lougher
2021-05-17 11:34       ` Pintu Agarwal
2021-05-17 11:34         ` Pintu Agarwal
2021-05-20  4:30         ` Phillip Lougher
2021-05-20  4:30           ` Phillip Lougher
2021-05-23 16:44           ` [RESEND]: Kernel 4.14: UBIFS+SQUASHFS: Device fails to boot after flashing rootfs volume Pintu Agarwal
2021-05-23 16:44             ` Pintu Agarwal
2021-05-23 17:31             ` Sean Nyekjaer
2021-05-23 17:31               ` Sean Nyekjaer
2021-05-24  6:12               ` Pintu Agarwal
2021-05-24  6:12                 ` Pintu Agarwal
2021-05-24  7:07                 ` Phillip Lougher
2021-05-24  7:07                   ` Phillip Lougher
2021-05-25  9:22                   ` Pintu Agarwal
2021-05-25  9:22                     ` Pintu Agarwal
2021-05-25  5:37                 ` Sean Nyekjaer
2021-05-25  5:37                   ` Sean Nyekjaer
2021-05-31  2:54                   ` Pintu Agarwal [this message]
2021-05-31  2:54                     ` Pintu Agarwal
2021-06-01  6:52                     ` Sean Nyekjaer
2021-06-01  6:52                       ` Sean Nyekjaer

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=CAOuPNLigHdbu_OTpsFr7gq+nFK2Pv+4MUSrC6A6PfKfF1H1X3Q@mail.gmail.com \
    --to=pintu.ping@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=phillip@squashfs.org.uk \
    --cc=sean@geanix.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.