Gentoo Archives: gentoo-user

From: Rich Freeman <rich0@g.o>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
Date: Wed, 25 Nov 2020 17:40:14
Message-Id: CAGfcS_mS8xVT-Pp4aravaHuGpwjQjhA3tQyhEn869nHNhJm2rQ@mail.gmail.com
In Reply to: Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0) by thelma@sys-concept.com
1 On Wed, Nov 25, 2020 at 12:15 PM <thelma@×××××××××××.com> wrote:
2 >
3 > On 11/25/2020 02:50 AM, Michael wrote:
4 > > On Wednesday, 25 November 2020 06:30:05 GMT thelma@×××××××××××.com wrote:
5 > >
6 > >> On 11/24/2020 10:08 PM, thelma@×××××××××××.com wrote:
7 > >>> I'm getting a kernel panic when booting a new system.
8 > >>>
9 > >>> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block
10 > >>> (0,0)
11 > >>>
12 > >>> fstab:
13 > >>> LABEL=boot /boot vfat
14 > > noauto,noatime 1 2
15 > >>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b /
16 > > ext4 noatime 0 1
17 > >>> LABEL=swap none swap
18 > > sw 0 0
19 > >>>
20 > >>> I even use: emerge --ask sys-kernel/genkernel
21 > >>> genkernel all
22 > >>>
23 > >>> So all the driver are compile-in (nothing should be missing)
24 > >>>
25 > >>> ls -al /boot/vmlinu* /boot/initramfs*
26 > >>> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30
27 > >>> /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672
28 > >>> Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920
29 > >>> Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64
30 > >> This problem is solved, it seems to me I was booting old kernel.
31 > >> Removing old kernel and re-running:
32 > >> grub-mkconfig -o /boot/grub/grub.cfg
33 > >>
34 > >> Solved the problem.
35 > >
36 > > Glad you got your new disk booting.
37 > >
38 > > Worth mentioning your fstab syntax is not entirely correct. According to 'man
39 > > fstab' you can specify a device with LABEL=<label>, as long as you have set
40 > > up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is
41 > > correct.
42 > >
43 > > UUID on the other hand is meant to be specified like so:
44 > >
45 > > UUID=<uuid>
46 > >
47 > > In your case it would be:
48 > >
49 > > UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b
50 > >
51 > > instead of it being preceded by "root=".
52 >
53 > The "genkernel all" is working but I need to find out which option is it
54 > that allow booting the drive. The genkernel.conf is different from
55 > standard kernel .config
56 >
57 > Removing options from genkernel is not easy.
58
59 With most initramfs you just pass root=UUID=foo on the kernel command
60 line. In the past genkernel has been quirky - I use dracut and you'd
61 definitely just use root=UUID=foo there.
62
63 --
64 Rich