Issue Booting after latest Zorin Update

[nooze]

@Aravisian

I'd try the .deb package linked above, then running the command above to disable swap, then update initramfs.

What does "trying the .deb package" entail in this? Installing it? Its the same version to what I am running.

[FrenchPress]

@nooze

I hoenstly forgot how I udpated the kernel in the first place. Would it be the same process to downgrading? Any tips on that would be beneficial.

You can do that in Synaptic.

[Aravisian]

@nooze

What does "trying the .deb package" entail in this? Installing it? Its the same version to what I am running.

Yes, it does. I suggest Reinstalling the package.
I linked an easy self installer to help with that.
I recommend using gdebi, but you can use the terminal if you prefer.

[nooze]

@Aravisian

Yes, it does. I suggest Reinstalling the package.
I linked an easy self installer to help with that.
I recommend using gdebi, but you can use the terminal if you prefer.

Awesome. I'll give this a try. Really appreciate the help. Did not know you could do a "re-install" which I guess is nice to know for when you see a symptom like this.

[nooze]

Log from install (via gdebi)

(Reading database ... 323087 files and directories currently installed.)
Preparing to unpack .../linux-modules-5.14.9-051409-generic_5.14.9-051409.202109300934_amd64.deb ...
Unpacking linux-modules-5.14.9-051409-generic (5.14.9-051409.202109300934) over (5.14.9-051409.202109300934) ...
Setting up linux-modules-5.14.9-051409-generic (5.14.9-051409.202109300934) ...
Processing triggers for linux-image-unsigned-5.14.9-051409-generic (5.14.9-051409.202109300934) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.14.9-051409-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34699: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34699: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34712: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34712: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34727: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34727: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34740: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34740: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found theme: /usr/share/grub/themes/zorin/theme.txt
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34831: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34831: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34849: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34849: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34867: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34867: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34889: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34889: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34979: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 34979: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found linux image: /boot/vmlinuz-5.14.9-051409-generic.signed
Found initrd image: /boot/initrd.img-5.14.9-051409-generic.signed
Found linux image: /boot/vmlinuz-5.14.9-051409-generic
Found initrd image: /boot/initrd.img-5.14.9-051409-generic
Found linux image: /boot/vmlinuz-5.12.0-051200-generic
Found initrd image: /boot/initrd.img-5.12.0-051200-generic
Found linux image: /boot/vmlinuz-5.11.0-41-generic
Found linux image: /boot/vmlinuz-5.11.0-38-generic
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 35797: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on vgs invocation. Parent PID 35797: /usr/sbin/grub-probe
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
File descriptor 69 (pipe:[314005]) leaked on lvs invocation. Parent PID 36069: /bin/sh
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Adding boot menu entry for UEFI Firmware Settings
done

[Aravisian]

You can follow this to get rid of the missing firmware warnings:

Linux-firmware sources (Possible missing firmware)

Some of us will occasionally experience the i915 "Possible Missing Firmware" warning. EDIT: A recent Update may make some of this Obsolete. If you are reading this after the updates released by 16 Dec 2021 and still having Firmware Warnings, perhaps the below will help you. I gathered all the listed files into one directory and this can be handled here: However, this only covers users with the i915 modinfo warning. Others have the AMD warnings and so forth. Other users may be having troubl…

Following the link to the post in "Bad behavior..." Should be all you need for that.

I am sorry, scrolling between this post and the O.P., I cannot tell which is yuor /dev/sda/
Can you clarify which drive that is?
Once you are able to boot, we may need to check your global filter in /etc/lvm/lvm.conf

[nooze]

@Aravisian

I am sorry, scrolling between this post and the O.P., I cannot tell which is yuor /dev/sda/
Can you clarify which drive that is?
Once you are able to boot, we may need to check your global filter in /etc/lvm/lvm.conf

Did the re-install, and rebooted. Same symptom.

Here is output of my drives:

nvme0n1                                                                                      
├─nvme0n1p1          vfat              71F5-BEA3                               505.8M     1% /boot/efi
├─nvme0n1p2          ext4              12ceaf52-1852-42f1-aeb3-8b114acc8ad4    354.9M    42% /boot
└─nvme0n1p3          crypto_LUKS       43a6282d-7a2d-48e0-802c-78371fc519ca                  
  └─nvme0n1p3_crypt  LVM2_member       9zRJUZ-ZIsE-tJCQ-YDFo-dYze-86Nh-hoo0tb                
    ├─vgzorin-root   ext4              0df273cb-51e9-4b37-8431-b44ba0a680e1    398.1G     7% /
    └─vgzorin-swap_1 swap              35347cf8-8ba6-49b1-b45f-f1d276b64c97                  [SWAP]

[FrenchPress]

@nooze

Did the re-install, and rebooted. Same symptom.

Time to grub a LAN cable?

[Aravisian]

@nooze

Here is output of my drives:

Do you have only one nVME drive?

[nooze]

@FrenchPress

Time to grub a LAN cable?

I am on a LAN cable as we speak:)

[nooze]

@Aravisian

Do you have only one nVME drive?

Yeppers.

[Aravisian]

I need to run to the store shortly... If you like, try @FrenchPress 's suggestion, Then we should check the above lvm conf file.

[FrenchPress]

@Aravisian

Then we should check the above lvm conf file.

I think it is safer for OP to wait for you.
I do not have any NVMe on my system and I am not familiar with that at all.

[Aravisian]

@FrenchPress

I do not have any NVMe on my system

Neither do I. @337harvey does...
It probably does not help that I appear semi-braindead today... You bunch really should be using Small Words.

[FrenchPress]

@Aravisian

Small Words.

?
You lost me (which is not so hard to do).

[Aravisian]

It is more of a Western Expression. When someone seems to be a bit distracted, we say to "use small words" because they will not understand "big words."

[FrenchPress]

I will see if I can help OP to revert back to the supported kernel.

[FrenchPress]

Can you open Synaptic and search for the keyword below?
linux-headers

Then sort the result to show the installed kernel.

Mine looks like this:

[nooze]

Done. Which specific kernel should I DL?

[FrenchPress]

@nooze

Done. Which specific kernel should I DL?

I need a screenshot like what I posted above.
The list of all installed kernels.