And while I guess I've at some point in the past sigint'ed pacman, I don't see anything like that in the log (but I've also likely never done that *during* an update)
]]>Could [2021-11-12T22:26:06-0300] [PACKAGEKIT] synchronizing package lists be related to Discover app store (I use KDE Plasma) checking for updates in the background?
Probably. Not related to the problem, though.
How to prevent this problem?
Pay attention to the pacman outputs. If you're using some GUI or other wrapper around pacman - maybe don't.
]]>[2021-11-12T19:21:53-0300] [ALPM-SCRIPTLET] ==> depmod 5.14.16-arch1-1
[2021-11-12T22:26:06-0300] [PACKAGEKIT] synchronizing package lists
I can be wrong though. My memory is not very good.
Could
[2021-11-12T22:26:06-0300] [PACKAGEKIT] synchronizing package lists
be related to Discover app store (I use KDE Plasma) checking for updates in the background?
]]>[2021-11-12T19:17:45-0300] [PACMAN] Running 'pacman -Syu'
[2021-11-12T19:17:45-0300] [PACMAN] synchronizing package lists
[2021-11-12T19:17:57-0300] [PACMAN] starting full system upgrade
[2021-11-12T19:21:47-0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2021-11-12T19:21:47-0300] [ALPM] running '70-dkms-upgrade.hook'...
[2021-11-12T19:21:48-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m vhba-module -v 20211023 -k 5.15.0-zen1-1-zen
[2021-11-12T19:21:48-0300] [ALPM-SCRIPTLET] rmdir: falhou em remover '': Arquivo ou diretório inexistente
[2021-11-12T19:21:49-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m vhba-module -v 20211023 -k 5.14.16-arch1-1
[2021-11-12T19:21:49-0300] [ALPM] running '71-dkms-remove.hook'...
[2021-11-12T19:21:50-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m vboxhost -v 6.1.28_OSE -k 5.14.16-arch1-1
[2021-11-12T19:21:51-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m r8168 -v 8.049.02 -k 5.14.16-arch1-1
[2021-11-12T19:21:52-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m vboxhost -v 6.1.28_OSE -k 5.15.0-zen1-1-zen
[2021-11-12T19:21:53-0300] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod -m r8168 -v 8.049.02 -k 5.15.0-zen1-1-zen
[2021-11-12T19:21:53-0300] [ALPM-SCRIPTLET] ==> depmod 5.14.16-arch1-1
[2021-11-12T22:26:06-0300] [PACKAGEKIT] synchronizing package lists
[2021-11-13T09:07:17-0300] [PACMAN] Running 'pacman -S linux-zen linux-zen-headers'
[2021-11-13T09:07:50-0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2021-11-13T09:07:50-0300] [ALPM] running '71-dkms-remove.hook'...
[2021-11-13T09:07:50-0300] [ALPM-SCRIPTLET] ==> Unable to remove module vboxhost/6.1.28_OSE for kernel 5.15.0-zen1-1-zen: Not found in dkms status output.
[2021-11-13T09:07:50-0300] [ALPM-SCRIPTLET] ==> Unable to remove module vhba-module/20211023 for kernel 5.15.0-zen1-1-zen: Not found in dkms status output.
[2021-11-13T09:07:50-0300] [ALPM-SCRIPTLET] ==> Unable to remove module r8168/8.049.02 for kernel 5.15.0-zen1-1-zen: Not found in dkms status output.
[2021-11-13T09:07:50-0300] [ALPM] transaction started
And I assume the -Syu on 11/12 was the compromising one.
It starts, cleans up syncs the package list and then does nothing and after ~3h PACKAGEKIT shows up (what seems an unrelated frequent injection) and then nothing happens until you ran 'pacman -S linux-zen linux-zen-headers' the next morning (11/13)
So: what happened that evening?
There's no explanation as to why the hooks were triggered, what was supposed to be updated at all and why apparently the update didn't happen.
The log shows a gap, but you'll have to fill in the blanks from your memory.
https://www.mediafire.com/file/p03ccwdj … n.log/file
The log is too long to share via pastebin services.
]]>If that's all that's in the log, it looks like pacman was killed before actually updating.
That's why we need to see the full log (and or get an explanation for its abrupt ending)
]]>To update the kernel, at least the vanilla one is at 5.15.2.
Yes, but as far as the logs posted show, no package upgrade actually happened.
]]>60-mkinitcpio-remove.hook was run, for some reason.
Both linux 5.14.16 (stable) and linux-zen 5.15 (testing) were installed on my system. Yesterday I updated my system by running 'pacman -Syu'
To update the kernel, at least the vanilla one is at 5.15.2
If that's all that's in the log, it looks like pacman was killed before actually updating.
=> Upload the complete log to some pastebin service or google drive or wetransfer or whatever.
]]>You are right Ammako. Yesterday I edited my fstab to enable ACL permissions for ntfs partitions mounted with ntfs3 driver.
I was getting "denied permisison" error when trying to write files into folders created with another user account.
Nah, forget what I said about that. 60-mkinitcpio-remove.hook was run, for some reason. That would be why your vmlinuz kernel files were deleted. Why? No clue. Your packages weren't uninstalled or upgraded.
]]>[2021-11-12T22:26:06-0300] [PACKAGEKIT] synchronizing package lists
Last time I tried PackageKit, it uninstalled my DE and many other packages for no apparent reason. Pretty sure this is its fault. Can you check its logs? I think they were in /var/log/Packagekit.log
/var/log/pacman.PackageKit.log has thousands of lines saying
[date/time] [PACKAGEKIT] synchronizing package lists
and nothing else.
Strangiato wrote:What has happened here? How to prevent this problem?
Well, for starters, you don't just blindly answer Yes to pacman -Syu. You're expected to check what it's doing first, if you spot anything wrong then you abort and figure out why it's trying to do what it's trying to do.
From the looks of your logs though, it never uninstalled any of your kernels. I'm guessing you misconfigured your system (fstab?) and grub is looking for kernel and initramfs in a different location than where the OS is placing them.
You are right Ammako. Yesterday I edited my fstab to enable ACL permissions for ntfs partitions mounted with ntfs3 driver.
I was getting "denied permisison" error when trying to write files into folders created with another user account.
If that's all that's in the log, it looks like pacman was killed before actually updating.
it's the log of the last update before the problem. A few days ago pacman crashed on my system after kernel update.
$coredumpctl|grep pacman
Wed 2021-11-03 19:57:07 -03 1452 0 0 SIGSEGV missing /usr/bin/pacman n/a
What has happened here? How to prevent this problem?
Well, for starters, you don't just blindly answer Yes to pacman -Syu. You're expected to check what it's doing first, if you spot anything wrong then you abort and figure out why it's trying to do what it's trying to do.
From the looks of your logs though, it never uninstalled any of your kernels. I'm guessing you misconfigured your system (fstab?) and grub is looking for kernel and initramfs in a different location than where the OS is placing them.
]]>