* [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
@ 2020-11-25 5:08 thelma
2020-11-25 6:30 ` thelma
0 siblings, 1 reply; 6+ messages in thread
From: thelma @ 2020-11-25 5:08 UTC (permalink / raw
To: Gentoo mailing list
I'm getting a kernel panic when booting a new system.
kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
fstab:
LABEL=boot /boot vfat noauto,noatime 1 2
root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / ext4 noatime 0 1
LABEL=swap none swap sw 0 0
I even use: emerge --ask sys-kernel/genkernel
genkernel all
So all the driver are compile-in (nothing should be missing)
ls -al /boot/vmlinu* /boot/initramfs*
-rwxr-xr-x 1 root root 11221820 Nov 24 21:30 /boot/initramfs-5.4.72-gentoo-x86_64.img
-rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo
-rwxr-xr-x 1 root root 8513920 Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
But at the end of the compilation I get:
* Kernel compiled successfully!
*
* --no-bootloader set; Skipping bootloader update ...
*
* Required kernel parameter:
*
* root=/dev/$ROOT
*
* Where $ROOT is the device node for your root partition as the
* one specified in /etc/fstab
* If you require Genkernel's hardware detection features, you MUST
* tell your bootloader to use the provided initramfs file '/boot/initramfs-5.4.72-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
--
Thelma
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
2020-11-25 5:08 [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0) thelma
@ 2020-11-25 6:30 ` thelma
2020-11-25 9:50 ` [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0) Michael
0 siblings, 1 reply; 6+ messages in thread
From: thelma @ 2020-11-25 6:30 UTC (permalink / raw
To: Gentoo mailing list
Thelma
On 11/24/2020 10:08 PM, thelma@sys-concept.com wrote:
> I'm getting a kernel panic when booting a new system.
>
> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
>
> fstab:
> LABEL=boot /boot vfat noauto,noatime 1 2
> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / ext4 noatime 0 1
> LABEL=swap none swap sw 0 0
>
> I even use: emerge --ask sys-kernel/genkernel
> genkernel all
>
> So all the driver are compile-in (nothing should be missing)
>
> ls -al /boot/vmlinu* /boot/initramfs*
> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 /boot/initramfs-5.4.72-gentoo-x86_64.img
> -rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo
> -rwxr-xr-x 1 root root 8513920 Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
This problem is solved, it seems to me I was booting old kernel.
Removing old kernel and re-running:
grub-mkconfig -o /boot/grub/grub.cfg
Solved the problem.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
2020-11-25 6:30 ` thelma
@ 2020-11-25 9:50 ` Michael
2020-11-25 15:19 ` thelma
2020-11-25 17:15 ` thelma
0 siblings, 2 replies; 6+ messages in thread
From: Michael @ 2020-11-25 9:50 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Wednesday, 25 November 2020 06:30:05 GMT thelma@sys-concept.com wrote:
> On 11/24/2020 10:08 PM, thelma@sys-concept.com wrote:
> > I'm getting a kernel panic when booting a new system.
> >
> > kernel panic - not syncing: VFS: unable to mount root fs on unknown-block
> > (0,0)
> >
> > fstab:
> > LABEL=boot /boot vfat
noauto,noatime 1 2
> > root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b /
ext4 noatime 0 1
> > LABEL=swap none swap
sw 0 0
> >
> > I even use: emerge --ask sys-kernel/genkernel
> > genkernel all
> >
> > So all the driver are compile-in (nothing should be missing)
> >
> > ls -al /boot/vmlinu* /boot/initramfs*
> > -rwxr-xr-x 1 root root 11221820 Nov 24 21:30
> > /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672
> > Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920
> > Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
> This problem is solved, it seems to me I was booting old kernel.
> Removing old kernel and re-running:
> grub-mkconfig -o /boot/grub/grub.cfg
>
> Solved the problem.
Glad you got your new disk booting.
Worth mentioning your fstab syntax is not entirely correct. According to 'man
fstab' you can specify a device with LABEL=<label>, as long as you have set
up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is
correct.
UUID on the other hand is meant to be specified like so:
UUID=<uuid>
In your case it would be:
UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b
instead of it being preceded by "root=".
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
2020-11-25 9:50 ` [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0) Michael
@ 2020-11-25 15:19 ` thelma
2020-11-25 17:15 ` thelma
1 sibling, 0 replies; 6+ messages in thread
From: thelma @ 2020-11-25 15:19 UTC (permalink / raw
To: gentoo-user
On 11/25/2020 02:50 AM, Michael wrote:
> On Wednesday, 25 November 2020 06:30:05 GMT thelma@sys-concept.com wrote:
[snip]
>>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b /
[snip]
>>
>> Solved the problem.
>
> Glad you got your new disk booting.
>
> Worth mentioning your fstab syntax is not entirely correct. According to 'man
> fstab' you can specify a device with LABEL=<label>, as long as you have set
> up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is
> correct.
>
> UUID on the other hand is meant to be specified like so:
>
> UUID=<uuid>
>
> In your case it would be:
>
> UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b
>
> instead of it being preceded by "root=".
I've notice it too during booting and corrected it, thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
2020-11-25 9:50 ` [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0) Michael
2020-11-25 15:19 ` thelma
@ 2020-11-25 17:15 ` thelma
2020-11-25 17:39 ` Rich Freeman
1 sibling, 1 reply; 6+ messages in thread
From: thelma @ 2020-11-25 17:15 UTC (permalink / raw
To: gentoo mailing list
On 11/25/2020 02:50 AM, Michael wrote:
> On Wednesday, 25 November 2020 06:30:05 GMT thelma@sys-concept.com wrote:
>
>> On 11/24/2020 10:08 PM, thelma@sys-concept.com wrote:
>>> I'm getting a kernel panic when booting a new system.
>>>
>>> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block
>>> (0,0)
>>>
>>> fstab:
>>> LABEL=boot /boot vfat
> noauto,noatime 1 2
>>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b /
> ext4 noatime 0 1
>>> LABEL=swap none swap
> sw 0 0
>>>
>>> I even use: emerge --ask sys-kernel/genkernel
>>> genkernel all
>>>
>>> So all the driver are compile-in (nothing should be missing)
>>>
>>> ls -al /boot/vmlinu* /boot/initramfs*
>>> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30
>>> /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672
>>> Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920
>>> Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
>> This problem is solved, it seems to me I was booting old kernel.
>> Removing old kernel and re-running:
>> grub-mkconfig -o /boot/grub/grub.cfg
>>
>> Solved the problem.
>
> Glad you got your new disk booting.
>
> Worth mentioning your fstab syntax is not entirely correct. According to 'man
> fstab' you can specify a device with LABEL=<label>, as long as you have set
> up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is
> correct.
>
> UUID on the other hand is meant to be specified like so:
>
> UUID=<uuid>
>
> In your case it would be:
>
> UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b
>
> instead of it being preceded by "root=".
The "genkernel all" is working but I need to find out which option is it
that allow booting the drive. The genkernel.conf is different from
standard kernel .config
Removing options from genkernel is not easy.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
2020-11-25 17:15 ` thelma
@ 2020-11-25 17:39 ` Rich Freeman
0 siblings, 0 replies; 6+ messages in thread
From: Rich Freeman @ 2020-11-25 17:39 UTC (permalink / raw
To: gentoo-user
On Wed, Nov 25, 2020 at 12:15 PM <thelma@sys-concept.com> wrote:
>
> On 11/25/2020 02:50 AM, Michael wrote:
> > On Wednesday, 25 November 2020 06:30:05 GMT thelma@sys-concept.com wrote:
> >
> >> On 11/24/2020 10:08 PM, thelma@sys-concept.com wrote:
> >>> I'm getting a kernel panic when booting a new system.
> >>>
> >>> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block
> >>> (0,0)
> >>>
> >>> fstab:
> >>> LABEL=boot /boot vfat
> > noauto,noatime 1 2
> >>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b /
> > ext4 noatime 0 1
> >>> LABEL=swap none swap
> > sw 0 0
> >>>
> >>> I even use: emerge --ask sys-kernel/genkernel
> >>> genkernel all
> >>>
> >>> So all the driver are compile-in (nothing should be missing)
> >>>
> >>> ls -al /boot/vmlinu* /boot/initramfs*
> >>> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30
> >>> /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672
> >>> Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920
> >>> Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
> >> This problem is solved, it seems to me I was booting old kernel.
> >> Removing old kernel and re-running:
> >> grub-mkconfig -o /boot/grub/grub.cfg
> >>
> >> Solved the problem.
> >
> > Glad you got your new disk booting.
> >
> > Worth mentioning your fstab syntax is not entirely correct. According to 'man
> > fstab' you can specify a device with LABEL=<label>, as long as you have set
> > up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is
> > correct.
> >
> > UUID on the other hand is meant to be specified like so:
> >
> > UUID=<uuid>
> >
> > In your case it would be:
> >
> > UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b
> >
> > instead of it being preceded by "root=".
>
> The "genkernel all" is working but I need to find out which option is it
> that allow booting the drive. The genkernel.conf is different from
> standard kernel .config
>
> Removing options from genkernel is not easy.
With most initramfs you just pass root=UUID=foo on the kernel command
line. In the past genkernel has been quirky - I use dracut and you'd
definitely just use root=UUID=foo there.
--
Rich
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-11-25 17:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-25 5:08 [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0) thelma
2020-11-25 6:30 ` thelma
2020-11-25 9:50 ` [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0) Michael
2020-11-25 15:19 ` thelma
2020-11-25 17:15 ` thelma
2020-11-25 17:39 ` Rich Freeman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox