From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Hans-Joachim Lange <lange-achim@posteo.de>,
linux-ide@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: PROBLEM: Kernel 6.8.x: VFS: Unable to mount root fs on unknown-block(0,0) – SATA (Intel AHCI) not detected
Date: Fri, 9 Oct 2026 17:40:28 +0200 [thread overview]
Message-ID: <askK7KVJlMcfyYWp@ryzen> (raw)
In-Reply-To: <1b9f33d6-f887-432a-83ec-292ff43eccdd@kernel.org>
On Fri, Oct 09, 2026 at 09:33:42AM +0200, Damien Le Moal wrote:
> On 2026/10/07 14:40, Hans-Joachim Lange wrote:
> > Hello,
> >
> > I am experiencing a regression: kernel 5.15.x boots fine, but 6.8.x
> > fails with "Kernel panic - not syncing: VFS: Unable to mount root fs
> > on unknown-block(0,0)". The SATA controller (Intel, rev 06) is not
> > detected; /dev/sda never appears. The ahci module is present in the
> > initramfs but does not load.
> >
> > [1.] One line summary:
> > Kernel 6.8.x fails to detect Intel SATA AHCI controller; /dev/sda
> > not created.
>
> Please try again with at least the latest stable kernel, or ideally the latest
> mainline kernel (7.3-rc6 as of this week). And also please try to capture the
> boot messages with the bad kernel. Hard to say what's happening without that.
> You can use network console or simply a video/pictures of the screen where we
> can see the ata messages.
You can also add rdinit=/bin/sh to the kernel command line
to get a shell.
Then you can do:
$ lspci
to see if the AHCI controller is there.
to see which modules are loaded.
You can then try to modprobe ahci to see
if your drives are detected.
In most of these cases, you are simply missing the required
filesystem (or similar) modules in your initramfs.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-10-09 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:40 PROBLEM: Kernel 6.8.x: VFS: Unable to mount root fs on unknown-block(0,0) – SATA (Intel AHCI) not detected Hans-Joachim Lange
2026-10-09 7:33 ` Damien Le Moal
2026-10-09 15:40 ` Niklas Cassel [this message]
[not found] ` <d575b071-50a4-479b-a992-3268f3b37a50@posteo.de>
[not found] ` <08c11d50-a358-4846-badc-7b7cb5c12d35@kernel.org>
[not found] ` <e2e16c3e-df02-47de-9205-c5259875211b@kernel.org>
2026-10-12 7:45 ` Niklas Cassel
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=askK7KVJlMcfyYWp@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=lange-achim@posteo.de \
--cc=linux-ide@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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