Kernel Panic on Boot After Installation (No initrd in grub.cfg)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cubic |
Fix Released
|
High
|
Cubic PPA |
Bug Description
Yesterday I ran my usual scripts with the latest version of Cubic (2020.10-34) to create an updated Linux Mint installer.
The custom ISO booted properly into Live Boot as well as straight to Ubiquity installer.
But, when I install the Linux Mint (from either Live Boot or our customized straight-
Upon investigation, I've found that the grub.cfg file does not have any initrd listed in the generated boot option.
I've recreated the custom ISO today to make sure it wasn't a fluke and got the same result.
This did not happen with last months updated build which used the same exact scripts during created. The last working ISO that I created was made on 2020-09-23 using Cubic 2020.09-31.
Is there something in the latest Cubic changes that could have possibly caused this?
I'm doubtful that it is a Linux Mint or Kernel issue because our custom installation process installs all updates via chroot into the installed drive after installation. So, even using my 2020-09-23 ISO, after the installation process, the latest Linux Mint with the latest Kernel is being successfully booted.
Changed in cubic: | |
status: | Incomplete → Confirmed |
importance: | Undecided → High |
As always, any thoughts or advice is greatly appreciated. I am not 100% certain this is a Cubic issue, but it seems to be the only variable that has changed between the last working ISO and now (unless I've somehow spaced me doing sometime silly in the meantime).
I believe I've seen in the past that the boot settings applied after the installation are somewhat inherited from the USB installer boot, but I'm not certain how all of that really works.