Missing initrd in lowlatency

[Tarheel86j]

In clean-installed 20.04 (amd64) using "linux" and "initrd.gz" found in "netboot.tar.gz", kernel panic is caused by the missing "initrd.img-*-lowlatency" on the first boot.

Procedure to reproduce the bug is as follows:
1.)Extract "netboot.tar.gz" and move the resulting directory "ubuntu-installer" under "/boot" in 18.04LTS (or on any systems with valid installation of grub2).
2.)Boot into the installer via grub, by manually typing in
"linux /ubuntu-installer/amd64/linux"
"initrd /ubuntu-installer/amd64/initrd.gz"
"boot"
3.)Proceed with setup as usual, selecting "Ubuntu Studio Desktop" and "OpenSSH Server" in the package selection section (and activate realtime processing for Jackd2 as prompted).
4.)Installation completes as usual and the machine is rebooted. Then the user experiences long silence.
5.)Force-shutdown PC, power-up again, enter GRUB by hitting Esc while in POST.
6.)Edit the lowlatency menu by typing "e", remove "quiet" from the kernel option.
7.)At this point the missing line containing "initrd" is becomes possible cause of the issue. Manually type it in, and boot.
8.)A Message saying that GRUB2 failed to load "initrd.img-*-lowlatency" shows up.
9.)Reboot the machine to see what happens when booted with "linux-*-generic" -> Boots fine.
10.)Missing "initrd.img-*-lowlatency" being the cause of this issue becomes clear.
11.)Run:
sudo apt-get update; sudo apt-get install linux-*-lowlatency --reinstall; sudo update-grub2
12.)Problem solves.

This bug was present in 20.04(RC), and is also present in 20.04(release).
Hardware/Platform on which I have confirmed this are Lenovo ThinkPad X200, Sun Fire X2100, Dell Studio 540D.

Unfortunately I cannot point out which package causes the issue. Troubleshooting the issue is easy for the experienced, yet could be cumbersome for those who are not familiar with Linux in general, Ubuntu or any Debian-variant distros. Hope this gets fixed quickly.

Regards and many thanks in advance.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1875574/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

By the way, there are many packages with 'low-latency' in their name. Sometimes reporting a bug against a package which 'might' be correct will mean it reaches the right team within Ubuntu. It can always be moved on to the correct package if necessary.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]