On Wednesday, 25 November 2020 06:30:05 GMT the...@sys-concept.com wrote: > On 11/24/2020 10:08 PM, the...@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=".
signature.asc
Description: This is a digitally signed message part.