Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 9 Jun 2021 20:22:20 +0200 (CEST)
From:   Richard Weinberger <richard@nod.at>
To:     Pintu Agarwal <pintu.ping@gmail.com>
Cc:     linux-kernel <linux-kernel@vger.kernel.org>,
        linux-mtd <linux-mtd@lists.infradead.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        Miquel Raynal <miquel.raynal@bootlin.com>
Message-ID: <295072107.94766.1623262940865.JavaMail.zimbra@nod.at>
In-Reply-To: <CAOuPNLiRDZ9M4n3uh=i6FpHXoVEWMHpt0At8YaydrOM=LvSvdg@mail.gmail.com>
References: <CAOuPNLiRDZ9M4n3uh=i6FpHXoVEWMHpt0At8YaydrOM=LvSvdg@mail.gmail.com>
Subject: Re: qemu: arm: mounting ubifs using nandsim on busybox
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Thread-Topic: qemu: arm: mounting ubifs using nandsim on busybox
Thread-Index: RJ64NFz5i2HW9LxJVNrur1Kl9viauw==
Precedence: bulk

Pintu,

----- Ursprüngliche Mail -----
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,0)
> =============================
> 
> If any one has used nandsim on qemu before, please let us know the exact steps.

nandsim works as expected. It creates a new and *erased* NAND for you.
So you have no UBI volumes. Therfore UBIFS cannot be mounted.
I suggest creating a tiny initramfs that creates UBI volumes before mounting UBIFS on
one of the freshly created (and empty) volumes.

Thanks,
//richard