Preparing...
Resolving dependencies...
Checking inter-conflicts...
Download of linux-hardened (5.14.6.hardened1-1) started
Download of linux-hardened-headers (5.14.6.hardened1-1) started
Download of linux-hardened-headers (5.14.6.hardened1-1) finished
Download of linux-hardened (5.14.6.hardened1-1) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Running pre-transaction hooks...
Saving Linux kernel modules...
Installing linux-hardened (5.14.6.hardened1-1)...
Installing linux-hardened-headers (5.14.6.hardened1-1)...
Running post-transaction hooks...
Restoring Linux kernel modules...
++ uname -r
+ KVER=5.14.2-zen1-2-zen
+ test -e /usr/lib/modules/backup/5.14.2-zen1-2-zen
+ rsync -AHXal --ignore-existing /usr/lib/modules/backup/5.14.2-zen1-2-zen /usr/lib/modules/
+ rm -rf /usr/lib/modules/backup
Arming ConditionNeedsUpdate...
Updating module dependencies...
Install DKMS modules
==> dkms install --no-depmod -m vhba-module -v 20210418 -k 5.14.6-hardened1-1-hardened
==> dkms install --no-depmod -m v4l2loopback-dc -v 1.8.0 -k 5.14.6-hardened1-1-hardened
==> dkms install --no-depmod -m vboxhost -v 6.1.26_OSE -k 5.14.6-hardened1-1-hardened
==> depmod 5.14.6-hardened1-1-hardened
Cleaning up...
Cleaning up...
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'default'
-> -k /boot/vmlinuz-linux-hardened -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-hardened.img
==> Starting build: 5.14.6-hardened1-1-hardened
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-hardened.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'fallback'
-> -k /boot/vmlinuz-linux-hardened -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-hardened-fallback.img -S autodetect
==> Starting build: 5.14.6-hardened1-1-hardened
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-hardened-fallback.img
==> Image generation successful
GRUB update after transactions...
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-tkg-muqss
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-tkg-muqss.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-tkg-muqss-fallback.img
Found linux image: /boot/vmlinuz-linux-lts-tkg-cacule
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts-tkg-cacule.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-lts-tkg-cacule-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux-hardened
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-hardened.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-hardened-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-09-22 20:24:46 | timeshift-btrfs/snapshots/2021-09-22_20-24-46/@
Found snapshot: 2021-09-22 20:05:28 | timeshift-btrfs/snapshots/2021-09-22_21-08-14/@
Found snapshot: 2021-09-22 20:04:13 | timeshift-btrfs/snapshots/2021-09-22_20-04-13/@
Found snapshot: 2021-09-22 19:36:54 | timeshift-btrfs/snapshots/2021-09-22_19-36-54/@
Found snapshot: 2021-09-21 23:40:03 | timeshift-btrfs/snapshots/2021-09-21_23-40-03/@
Found snapshot: 2021-09-21 23:38:30 | timeshift-btrfs/snapshots/2021-09-21_23-38-30/@
Found snapshot: 2021-09-21 22:40:00 | timeshift-btrfs/snapshots/2021-09-21_22-40-00/@
Found snapshot: 2021-09-20 21:47:27 | timeshift-btrfs/snapshots/2021-09-22_20-05-28/@
Found snapshot: 2021-09-20 21:10:31 | timeshift-btrfs/snapshots/2021-09-20_21-47-27/@
Found 9 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Foreign/AUR package notification
chromium-extension-plasma-integration 1.8-1
heifthumbnailer 1.0-1
libpamac-full 1:11.1.0-1
libspeedhack-git r12.29e0bd6-1
pamac-all 10.2.0-1
sddm-git 0.19.0.63.g83e1ae5-1
snapd 2.52-2
snapd-glib 1.59-1
sndcpy-bin 1.0-1
surfshark-vpn 1.1.0-1
vlc-pause-click-plugin 2.2.0-1
wsdd 0.6.4-2
Checking for kernel changes...
Orphaned package notification...
asciidoc 9.1.1-2
extra-cmake-modules 5.86.0-1
go 2:1.17.1-1
go-tools 4:0.1.6-1
heroku-cli-bin 7.59.0-1
itstool 1:2.0.6-2
kinit 5.86.0-1
meson 0.59.1-1
python-docutils 0.17.1-1
vala 0.52.5-1
Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/dnscrypt-proxy/dnscrypt-proxy.toml.pacsave
/etc/pamac.conf.pacsave
/etc/pacman.d/mirrorlist.pacnew
Please check and merge
Updating pkgfile database...
Syncing all file systems...
A restart is required for the changes to take effect.
Transaction successfully finished.
Is there a new version of mkinitcpio or something? Or maybe it's an os-prober-btrfs bug? I know that my partitions between all the installs are kinda a mess, but judging between the successful boots, I don't think the problem is with the grub or later parts of the boot, since I didn't even get to plymouth.
Just in case, last night I made sure to test out if it'll eventually work, but 30min of waiting that was a nope.
The only difference is that there is a 'Booting command line' at the top, but otherwise it still stops at 'Loading Initial Ramdisk'.
That said, I recently tried to update plymouth-git, and while that failed, I booted to a timeshift auto-backup (currently still in that session), which opened Garuda Assistant automatically, and fount this in Journal Errors diagnostics:
-- Journal begins at Sun 2021-09-12 14:04:11 WIB, ends at Fri 2021-09-24 20:26:21 WIB. --
Sep 24 20:25:17 Garuda-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210604/psargs-330)
Sep 24 20:25:17 Garuda-PC kernel: ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Sep 24 20:25:17 Garuda-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210604/psargs-330)
Sep 24 20:25:17 Garuda-PC kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
Sep 24 20:25:17 Garuda-PC systemd[1]: Failed to start systemd-guest-user.service.
Sep 24 20:25:17 Garuda-PC systemd-modules-load[336]: Failed to find module 'ashmem_linux'
Sep 24 20:25:17 Garuda-PC systemd-modules-load[336]: Failed to find module 'binder_linux'
Sep 24 20:25:17 Garuda-PC systemd[355]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Read-only file system
Sep 24 20:25:17 Garuda-PC systemd-udevd[358]: /usr/lib/udev/rules.d/55-Argyll.rules:156 Unknown group 'colord', ignoring
Sep 24 20:25:18 Garuda-PC systemd[365]: haveged.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[365]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd-udevd[366]: vhba_ctl: /usr/lib/udev/rules.d/60-vhba.rules:1 Only network interfaces can be renamed, ignoring NAME="vhba_ctl".
Sep 24 20:25:18 Garuda-PC systemd-udevd[370]: host11: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write ATTR{/sys/devices/platform/vhba/host11/scsi_host/host11/link_power_management_policy}, ignoring: No such file or directory
Sep 24 20:25:18 Garuda-PC systemd[443]: haveged.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[443]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd-udevd[375]: host11: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write ATTR{/sys/devices/platform/vhba/host11/scsi_host/host11/link_power_management_policy}, ignoring: No such file or directory
Sep 24 20:25:18 Garuda-PC systemd-udevd[372]: host10: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb4/4-4/4-4:1.0/host10/scsi_host/host10/link_power_management_policy}, ignoring: No such file or directory
Sep 24 20:25:18 Garuda-PC systemd[513]: haveged.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[513]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[1]: Failed to start systemd-guest-user.service.
Sep 24 20:25:18 Garuda-PC systemd-udevd[391]: vhba_ctl: /usr/lib/udev/rules.d/60-vhba.rules:1 Only network interfaces can be renamed, ignoring NAME="vhba_ctl".
Sep 24 20:25:18 Garuda-PC systemd-udevd[388]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Sep 24 20:25:18 Garuda-PC systemd-udevd[386]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Sep 24 20:25:18 Garuda-PC systemd-udevd[388]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Sep 24 20:25:18 Garuda-PC systemd[543]: haveged.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[543]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Read-only file system
Sep 24 20:25:18 Garuda-PC systemd[1]: Failed to start Entropy Daemon based on the HAVEGE algorithm.
Sep 24 20:25:18 Garuda-PC systemd[1]: Failed to start systemd-gu
est-user.service.
Sep 24 20:25:23 Garuda-PC libvirtd[1265]: unable to set ownership of '/var/lib/libvirt/qemu' to user 65534:992: Read-only file system
Sep 24 20:25:23 Garuda-PC libvirtd[1265]: Initialization of QEMU state driver failed: unable to set ownership of '/var/lib/libvirt/qemu' to user 65534:992: Read-only file system
Sep 24 20:25:23 Garuda-PC libvirtd[1265]: Driver state initialization failed
Sep 24 20:25:32 Garuda-PC sddm-helper[1447]: pam_systemd(sddm-greeter:session): Failed to release session: Access denied
Sep 24 20:25:32 Garuda-PC systemd[4306]: Failed to start Profile-sync-daemon.
Just in case, I tried to update everything and then mkinitcpio last night, but it still didn't work. Also tried out mkinitcpio-git with the stock linux kernel, same thing.
Is there an mkinitcpio bug upstream or something? Also, is there no other config files and binaries that I could use? I remember fixing a broken lutris-git install by just reinstalling everything on a VM and then just replacing all the files from there. Or is there no way to update the kernel without updating the initial ramdisk?
That is caused because you are booted off a read-only snapshot.
You can mask the mkinitcpio hook but that will probably break your system unless you are re-installing the exact same version of the kernel. In general I donât recommend this approach.
Hm.... as a simple sanity check, I did made sure to install Garuda on a VM, update everything, install vhba-module-dkms, and then reboot. It's fine there. I then copy-pasted the initcpio.conf, but it still didn't work on the main machine side when I updated linux-lts.
Can anyone give me a checklist of the config files and packages that plays a role in kernel installl/upgrades? I'll go and check them one by one, see what could be causing it.
Worst case scenario, I guess I'll just reinstall Garuda, though without knowing what might be the cause of it, I'm afraid I might break it again.
I use grub-btrfs (4.9-1), though looking at my history, before that I used grub-garuda from the version that shipped with the August iso to version 2.06-1. Other than that, I had a bunch of -garuda to -btrfs transition recently, I currently have os-prober-btrfs (1.79-2), plymouth-git (0.9.5.r84), btrfs-progs (5.13.1-1) and cryptsetup (2.4.0-1).
About the only modification I did was trying to use the Garuda Boot Options to try find my Windows partition again, in-between the switch to grub-btrfs and os-prober-btrfs.
Your system is in a very strange and complicated state and the possible number of reasons/problems that have to be repaired is unknown. The possibilities are countless.
The quicker and easiest way to get a usable system seems to be a system re-installation, after preparing data backup and useful changes that you may have already done (custom packages and settings/configuration).
If you want to insist finding out the actual problems, you have to start from scratch, like
Boot to a successful snapshot. If there is not one, it is really difficult to continue.
Make sure you have not a partial upgrade (i.e. you have installed sddm-git, or others that we cannot know)
Set one good mirror for each mirrorlist, excluding geo-mirror(s).
Start an update and check for "newer local packages" messages. If there are, abort and change to another mirror on the relevant server.
Save grub.cfg to an external drive and reboot.
On grub menu, press "E" to a menu entry and get a picture with grub entry contents.
Try to boot (with F10).
If it fails to a message, log down and go to TTY, to get journalctl and systemctl errors.
Post to the topic to get advice (if there would be one ).
$ pacman -Qs grub
local/grub 2:2.06-2
GNU GRand Unified Bootloader (2)
local/grub-btrfs 4.9-1
Include btrfs snapshots in GRUB boot options
local/grub-garuda 2.06-1
meta pkg for grub
local/grub-theme-garuda-dr460nized r2.49d1e5e-1
Garuda Dr460nized grub theme
local/python-markdown 3.3.4-1
Python implementation of John Gruber's Markdown.
local/update-grub 0.0.1-7
Simple wrapper around grub-mkconfig
And I did used the Garuda Boot Options to reinstall bootloader. It didnât work.
I guess Iâll just reinstall this, since there are some new things in the latest .iso release anyways. Iâll back up my important settings first though. Thanks for the help, everyone.
).