You are not logged in.
Changing the UUID is an "if all else fails" option, as I said, in worst case scenario. If you're sure your UUID for the drive is sound then don't change it.
As to why this happened it's hard to say. I would look at backing up anything you want to keep in case the drive is beginning to fail.
Offline
On a side note; The following error in your OP suggests you don't have the linux-firmware package installed. Not a major problem but no harm in fixing it.
[2020-04-02T16:05:13+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2020-04-02T16:05:13+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
The firmware for aic94xx and wd719x is not provided by linux-firmware. As the output is from producing the fallback initrd only the modules have not been detected as required and the warning is normal.
Offline
As for the "No IRQ for vector" issue that appears to be a Motherboard compatability issue/bug. The acccepted solution seems to be this one; https://ubuntuforums.org/showthread.php?p=7759222
Which suggests (for Grub2) to;
1. sudo gedit /etc/default/grub
2. change GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
3.sudo update-grub
Offline
Lander1 wrote:On a side note; The following error in your OP suggests you don't have the linux-firmware package installed. Not a major problem but no harm in fixing it.
[2020-04-02T16:05:13+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2020-04-02T16:05:13+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719xThe firmware for aic94xx and wd719x is not provided by linux-firmware. As the output is from producing the fallback initrd only the modules have not been detected as required and the warning is normal.
https://wiki.archlinux.org/index.php/Mkinitcpio
Possibly missing firmware for module XXXX
When initramfs are being rebuild after a kernel update, you might get these or similar warnings:==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
These appear to any Arch Linux users, especially those who have not installed these firmware modules. If you do not use hardware which uses these firmwares you can safely ignore this message.Most common firmware files can be acquired by installing the linux-firmware package. For other packages proving firmware, try searching for the module name in the official repositories or AUR.
Making sure the firmware is installed may help and certainly can't hurt.
Offline
These appear to any Arch Linux users, especially those who have not installed these firmware modules. If you do not use hardware which uses these firmwares you can safely ignore this message.
Most common firmware files can be acquired by installing the linux-firmware package. For other packages proving firmware, try searching for the module name in the official repositories or AUR.
If you are inferring from the two lines above that linux-firmware provides the firmware for aic94xx and/or wd719x modules or that the output indicates linux-firmware was not installed you are mistaken.
https://aur.archlinux.org/packages/aic94xx-firmware/
https://aur.archlinux.org/packages/wd719x-firmware/
As for the "No IRQ for vector" issue that appears to be a Motherboard compatability issue/bug. The acccepted solution seems to be this one; https://ubuntuforums.org/showthread.php?p=7759222
Which suggests (for Grub2) to;
1. sudo gedit /etc/default/grub
2. change GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
3.sudo update-grub
Kernel_parameters documents how to add kernel parameters temporarily for testing. It also links to the wiki page for each boot loader which provides instructions for making such a change permanent.
Please do not suggest running graphical editors as root Running_GUI_applications_as_root#GVFS
Last edited by loqs (2020-04-20 02:43:52)
Offline
Just trying to help.
Last edited by Lander1 (2020-04-22 11:27:52)
Offline
Just trying to help.
Help is appreciated.
Offline
The issue remains and I try after every largish update to see if anything is fixed.
Speculative but reasonable suggestions for what I can try to investigate is welcome. I'll update the thread with what efforts and results I make.
Offline