On Wed, Dec 9, 2020 at 9:32 AM Michael D. Setzer II <msetzerii@xxxxxxxxx> wrote: > > > > Sometimes have the rescue kernel around is handy. Had people > sometime move a hard disk to a different system with a diskcontroller > that wasn't included by the standard kernel. The rescue kernel generally > has the support for more hardware. > > Once upgraded a machine to SATA disk. Copied image and it started > boot but then failed since the SATA support wasn't in the files. Went > thru process of manually building a kernel to support it. So, found the > process. > > I've used the little script mknewrescue that runs this. > /etc/kernel/postinst.d/51-dracut-rescue-postinst.sh $(uname -r) > /boot/vmlinuz-$(uname -r) > > Note: you have to manually remove or move the rescue kernels > elsewhere or it will not build new ones? > When I know I am doing a migration to new hardware I rebuild the booting kernel with "hostonly=no" in dracut.conf or on explicitly on the dracut rebuild command. rhel6 defaulted to hostonly=no, it was changed at rhel7 to hostonly=yes, not sure when change was made in fedora. The disadvantages to =no is that the initramfs are around 60M vs 25M or so so you can have fewer of these on /boot, and it takes grub and the kernel a few seconds longer or so to read and decompress on boot up, but with that they should boot any hardware that kernel can support. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
