Re: Last kernel update leads to emergency mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 24 Aug 2023 17:44:52 +0100
Paul Smith <phhs80@xxxxxxxxx> wrote:
 
> I have been able to take a screen-shot:
> 
> https://i.imgur.com/nAsE6i6.jpg

This means that dracut was unable to start systemd in order to continue
the boot once the initramfs was finished creating the bootstrap.  I
have had this happen, but not with stock kernels.  I build custom
kernels, and dracut was not building a complete initramfs when
they were installed.  I had to write a script that created a custom file
that told dracut to include all missing libraries, and run dracut again
after install to fix the problem.  The missing libraries included some
vital systemd libraries.  Because library versions change, I run the
script to be sure that the custom file includes the latest libraries.
If this *is* the cause, it will be obvious in /boot. The failing
initramfs size will be about half the size of an initramfs file that
works.  I could not find any reason that dracut wasn't working properly
when it first installed the kernel; all the settings said it should
have put those libraries in, but I just could not get it to do so.

If it is your issue, post back and I'll attach the file of libraries and
the directory to put it in, as well as the dracut command to run.  They
might not work for you, since the version has to be included.  There is
also a way to actually examine what is in the initramfs, so you could
see if the systemd libraries were there. From the dracut man page,

Inspecting the Contents
       To see the contents of the image created by dracut, you can use
the lsinitrd tool.
 
           # lsinitrd | less
 
       To display the contents of a file in the initramfs also use the
lsinitrd tool:
 
           # lsinitrd -f /etc/ld.so.conf
           include ld.so.conf.d/*.conf
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux