From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: jim.cromie@gmail.com
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2
Date: Sat, 14 Aug 2021 20:21:00 -0400 [thread overview]
Message-ID: <69789.1628986860@turing-police> (raw)
In-Reply-To: <CAJfuBxxnk+UhxLXVv+gWZ9+hDN2crt0H+=j3_ur=Yd_9-fPmJA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]
On Fri, 13 Aug 2021 18:08:38 -0600, jim.cromie@gmail.com said:
> then I added BTRFS_FS, since thats the host fs.
> of course it didnt work.
> VFS: Cannot open root device "(null)" or unknown-block(0,0): error -2
> Please append a correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> CPU: 0 PID: 1 Comm: swapper Tainted: G W 5.14.0-rc4+ #5
And it didn't find any usable btrfs (or other fs it knew about)
> Heres a working kernel (if overlarge config)
> VFS: Mounted root (9p filesystem) readonly on device 0:20.
> Anybody see any clues ?
That '9p filesystem' should be a really big clue. If that's the root fs that you
actually want to use, you need to do two things:
a) point at it with root=
b) have 9p filesystem support in the kernel
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-08-15 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 0:08 VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2 jim.cromie
2021-08-15 0:21 ` Valdis Klētnieks [this message]
2021-08-15 23:22 ` jim.cromie
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=69789.1628986860@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.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