On Friday, 11 December 2020 18:56:19 GMT the...@sys-concept.com wrote: > On 12/11/2020 11:39 AM, Michael wrote: > > On Friday, 11 December 2020 18:24:27 GMT the...@sys-concept.com wrote: > >> On 12/11/2020 10:45 AM, Michael wrote: > >>> On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote: > >>>> On Fri, Dec 11, 2020 at 9:27 AM <the...@sys-concept.com> wrote: > >>>>> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote: > >>>>>> Now, when I boot I get a message: > >>>>>> > >>>>>> Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid > >>>>>> root device. > >>>>> > >>>>> This puzzles me. I cannot find the string "is not a valid root device" > >>>>> (or > >>>> > >>>> sub-strings) in the source code for the Linux kernel, GRUB2, and > >>>> refind. > >>>> It > >>>> seems to me it should be in one of them. > >>>> > >>>> - Matthew > >>> > >>> The error is indicative of the kernel driver for the / block device > >>> missing. If it is not built in-the-kernel, but as a module, then it > >>> should be in initramfs. > >>> > >>> Copy the kernel image, System.map, .config and corresponding initramfs > >>> to > >>> the /boot partition, then point your boot manager to the kernel to boot > >>> it. > >> > >> How do you copy/generate initramfs in /boot directory? > > > > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel > > https://wiki.gentoo.org/wiki/Genkernel > > > > If you're using genkernel it will copy it to /boot. Besides the Handbook > > you may find the following reference material on boot managers/loaders > > useful: > > > > For rEFInd see here: > > > > https://wiki.gentoo.org/wiki/Refind > > > > For GRUB see here: > > > > https://wiki.gentoo.org/wiki/GRUB2 > > > > For efibootmgr see here: > > > > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/ > > Bootloader#Alternative_2:_efibootmgr > > After I compile kernel I usually get this message (WHY?): > > * You will find the initramfs in '/boot/initramfs-5.4.72-gentoo.img'. > > * WARNING... WARNING... WARNING... > * Additional kernel parameters that *may* be required to boot properly: > * > * With support for several ext* filesystems available, it may be needed to > * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
I would have thought all modern boot loaders can read ext* filesystems, without needing to specify the filesystem type by passing the kernel parameters yourself to the boot loader. However, I don't use genkernel to know how to configure/modify it so it boots with different boot managers. If the details are not explained in the links I provided above, someone experienced in using genkernel should give some pointers.
signature.asc
Description: This is a digitally signed message part.