Once in a while i do “pacman -Syu” in order to update the system. I know… This should be done more often. Maybe daily.
And then everything has broken… all applications closed, and then I restarted my pc. Once it boot up I encountered the message:
"error: file `/timeshift-btrfs/snapshots/2023-12-10_01-25-13/@boot/vmlinuz-6.1-x86_64’ not found.
Loading Microcode & initramfs: amd-ucode.img initramfs-6.1-x86_64-fallback.img …
error: you need to load the kernel first. "
And then… Yes! I freaked out.
Loaded my LiveCD(or pendrive?) and did mount the efi partition(/dev/sda5), the root partition(/dev/nvme0n1p3), chrooted and tried:
which game me: “Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `overlay’.”
then i have tried also to do pacman -Syu:
pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed retrieving file 'multilib.db' from osmirror.org : Could not resolve host: osmirror.org
warning: too many errors from osmirror.org, skipping for the remainder of this transaction
error: failed retrieving file 'core.db' from osmirror.org : Could not resolve host: osmirror.org
error: failed retrieving file 'extra.db' from osmirror.org : Could not resolve host: osmirror.org
error: failed retrieving file 'community.db' from osmirror.org : Could not resolve host: osmirror.org
error: failed retrieving file 'multilib.db' from kibo.remi.lu : Could not resolve host: kibo.remi.lu
warning: too many errors from kibo.remi.lu, skipping for the remainder of this transaction
error: failed retrieving file 'core.db' from kibo.remi.lu : Could not resolve host: kibo.remi.lu
error: failed retrieving file 'extra.db' from kibo.remi.lu : Could not resolve host: kibo.remi.lu
error: failed retrieving file 'community.db' from kibo.remi.lu : Could not resolve host: kibo.remi.lu
:: Starting full system upgrade...
there is nothing to do
Well, I dont what to do. Also worth mentioning the root partition is in BTRFS instead of ext4
(1/3) Creating Timeshift snapshot before upgrade...
timeshift: error while loading shared libraries: libicuuc.so.73: cannot open shared object file: No such file or directory
Unable to run timeshift-autosnap! Please close Timeshift and try again. Script will now exit...
error: command failed to execute correctly
error: failed to commit transaction (failed to run transaction hooks)
Errors occurred, no packages were upgraded.
Another thing I have realized…
once I am chrooted into my /dev/nvme0n1p3 partition, i cant see all my files in the directories which i expected…
The pinned comment and the PKGBUILD provides a way to directly download the binary, which can be used to reinstall pacman or to upgrade the entire system in case of partial upgrades.
So get that, and re-run the update to properly sync your system.
However, I do know that BTRFS has sub-volumes that also need to be mounted in a chroot environment. If you failed to mount those, perhaps that’s the reason your files/directories were so elusive.
Nice, pacman was able to install its packages (pacman -Syu).
Then, I tried
update-grub
and this is the output
update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-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.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
No snapshots found.
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Unmount /tmp/grub-btrfs.IdsPi2mhiv .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
Does your machine happen to be a Tuxedo, with Manjaro pre-installed?
It seems that Tuxedo installs using non-standard paths; specifically, --efi-directory=/boot points directly to $ESP/EFI; and bootloader-id=GRUB replaces bootloader-id=manjaro, resulting in a boot path of $ESP/EFI/GRUB (/boot/EFI/GRUB/grubx64.efi).
I expect this is convenient for Tuxedo when churning out multiple pre-installed distributions, however, this revelation has been an apparent contributor to at least one member’s grief in recent weeks, when attempting to update Grub.
