My ten year old Fedora Server 33 runs on AMD Phenom 1090T Six Core Processor on GigaByte GA-880GM-UD2H motherboard, recently started having bootup trouble as detailed below:
Out of following three Fedora Kernels I am not able to boot with kernel versions higher and including > 5.10.16.200.fc33.x86_64 :
Fedora (5.10.19.200.fc33.x86_64) 33 (Server Edition) - Does not boot
Fedora (5.10.16.200.fc33.x86_64) 33 (Server Edition) - Does not boot
Fedora (5.8.15.801.fc33.x86_64) 33 (Server Edition) - Boots good
The problem with 5.10 kernels is:
dracut-initqueue[329] : Warning: dracut-initqueue timeout - starting timeout script
and waits and waits …
and then it falls back to grub emergency mode prompt.
Please help, I am scared that upcoming version Fedora Server 34 might end up having the same boot problems.
You would need to test the upcoming release before you commit to the system upgrade.
Also, if you are doing anything more than venting steam about the issue it would be nice if you clearly told us what was happening, what the hardware is, what messages you see, etc.
Logs, dmesg output, journal entries, etc. are all helpful.
Even when it fails to boot there are usually some things that give us a clue, and “Does not boot” is not at all helpful in getting advice.
I could be like the doctor and say If that kernel does not boot then use the other kernel.
As for the Boot Log Journals, sorry for posting such long texts but there is no way to attach text file, either:
Done for a new installation. This is a Windows 7 certified motherboard provisioned for Fedora Server 33, hence might find a lot of inconsistencies, pardon me for that though.
Two Journals being posted :
1- Boot Before kernel upgrade hence with v5.8
2- Boot Just after Kernel upgrade to V 5.10
Here goes -
Sorry no way to paste/attach such a long log story
and post the browser address link after hitting the “Paste”-button here.
to your problem:
on an command line do
rpm -qa | grep kernel-core
to get an list off installed kernels
remove the newest problematic kernel via
sudo dnf remove kernel-core -<fill in the correct number and ending here>
hint:
your could also type “sudo dnf remove kernel-core-” and hit the TAB-key (one or more times)
now re-install the same kernel via: arrow key up (to get the last command back) and exchange “remove” with “install”
do the install scripts run without errors ?
Background:
moons ago the did not
===
you could test your fear regarding F34 by booting an F34 DVD/USB-stick and checking with dmesg.
usually if that goes okay, the installed kernel will also do [1] , cause the kernels (DVD, installed) are the same.
but with one restriction: that the box has no internet connection during installation.
- assuming the install (still) fetches the newest packages from the internet and install them contrary to what’s on the dvd -
[1]
- I slightly remember a case where it seemed it didn’t, somehow -
Same experience as mine. RH in all its versions from 1992 until fedora was branched then fedora from the beginning. IIRC at the beginning it was Fedora Core 1, and at some point they dropped the “Core” and became just Fedora (although the packages are still labeled fc32, fc33, etc.)
You left out the 5, 10, & 20MB HDs (which I used on a 286 machine) as well as the 128KB, 256KB, & 512KB RAM, and the 80286 and 80386 processors from the late 80s and early 90s. Those CPUs were barely into the Mhz range before the pentiums came along.
