Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1905294 [details] rdsosreport.txt Description of problem: I am trying to boot Fedora-Server-netinst-x86_64-36-1.5.iso on bare metal through a Lantronix (Peppercon) SLS KVM Console which fails. Version-Release number of selected component (if applicable): 5.17.5-300.fc36.x86_64 (ISO timestamp 2022-05-04-18-33-31-00) How reproducible: Always Steps to Reproduce: 1. Mount ISO on Lantronix KVM console and try to boot Actual results: [...] [ 320.579171] fedora dracut-initqueue[1059]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 320.580751] fedora dracut-initqueue[1059]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 320.581946] fedora dracut-initqueue[1059]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 320.583892] fedora dracut-initqueue[1059]: Warning: dracut-initqueue: starting timeout scripts [ 320.583892] fedora dracut-initqueue[1059]: Warning: ############# Anaconda installer errors begin ############# [ 320.583892] fedora dracut-initqueue[1059]: Warning: # # [ 320.583892] fedora dracut-initqueue[1059]: Warning: It seems that the boot has failed. Possible causes include [ 320.583892] fedora dracut-initqueue[1059]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 320.583892] fedora dracut-initqueue[1059]: Warning: kernel cmdline. Please verify that you have specified [ 320.583892] fedora dracut-initqueue[1059]: Warning: inst.stage2 or inst.repo. [ 320.583892] fedora dracut-initqueue[1059]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 320.583892] fedora dracut-initqueue[1059]: Warning: # # [ 320.595984] fedora dracut-initqueue[1059]: Warning: #### Installer errors encountered during boot: #### [ 320.595984] fedora dracut-initqueue[1059]: Warning: # # [ 320.595984] fedora dracut-initqueue[1059]: /lib/dracut/hooks/initqueue/timeout/50-anaconda-error-reporting.sh: line 19: /run/anaconda/initrd_errors.txt: No such file or directory [ 320.595984] fedora dracut-initqueue[1059]: Warning: # # [ 320.595984] fedora dracut-initqueue[1059]: Warning: ############# Anaconda installer errors end ############### [ 321.594711] fedora dracut-initqueue[1059]: Warning: Could not boot. [ 321.609663] fedora systemd[1]: Starting dracut-emergency.service - Dracut Emergency Shell... Expected results: installation pass Additional info: I am experiencing similar boot failures using systemrescuecd with this Lantronix KVM which I reported upstream as https://gitlab.com/systemrescue/systemrescue-sources/-/issues/276 which could be related.
We found the issue and a fix is available: Bug is in udevd, see https://github.com/systemd/systemd/pull/24309
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.