I just did the update as I do every time I see mirrors refreshed.
Black screen on restart.
Left it for an hour.
Still black.
PowerOff.
Can get to kernel versions to select, but after some HD light activity, nothing.
Let it sit for hours. Still black.
I remember seeing from different things in the update fly by that said “not enough room” etc. As I was watching I would open up the disk manager and check to see that there was plenty of space.
I am currently booted onto a Live USB, and my next step is to see if I have a pretty recent TimeShift.
I will check back here to see if anyone suggests getting information from logs, etc. At one point trying to boot, I was able to do the systemctl ??? that allows one to see logs. I took pictures
I am stuck on step 4:
:: Proceed with installation? [Y/n]
(3/3) checking keys in keyring [###################] 100%
downloading required keys…
error: key “6D42BDD116E0068F” could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
error: target not found: mhwd-chroot
[manjaro@manjaro ~]$
However!
I mounted sda3 and I can indeed see my home with things in it.
sda2 is a swap
Sorry for my english.
Is it Manjaro who runs Grub, or is it another distro ? Others one does not load the necessary microcode for Arch & Manjaro .
In this case, you need edit grub menu with E key and add the intel-ucode our amd-ucode after the linux /boot… line like this eg:
I don’t want to try to go down two different paths, so, do you feel your recommendation is helpful beyond the previous direction?
And even if you do, I will need more direction since I do not understand what you are suggesting to do.
If I had to guess… It seems like the issue is init, obviously, so maybe the only issue is just what it says… That I need to give it a proper init (location?)
I have successfully booted from a Live USB with Manjaro 20 on it.
Once booted, I opened a terminal CTRL-Alt-T and offered this command:
sudo timeshift --restore
This gave me a listing of all of my backups.
I put in the right number and took the defaults to restore.
I just started the latest stable update via terminal and noticed some failures.
They seem to indicate they have been dealt with, but I am concerned and will put off reboot until I hear back form someone. I thought this was the best place to put this, because this MAY be connected to why I had to restore on the last update.
Please let me know what you think?
( 6/16) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'default'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'fallback'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: '/lib/modules/5.8.18-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.8.18-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default'
-> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
==> Starting build: 5.9.11-3-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback'
-> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
==> Starting build: 5.9.11-3-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
==> Image generation successful
error: command failed to execute correctly
( 7/16) Reloading system bus configuration...
( 8/16) Warn about old perl modules
( 9/16) fix appstream datas for pamac
archive usr/share/app-info/xmls/community.xml.gz fixed
(10/16) Compiling GSettings XML schema files...
(11/16) Updating icon theme caches...
(12/16) Hiding redundant menu entries
(13/16) Updating the info directory file...
(14/16) Updating the appstream cache...
AppStream cache update completed successfully.
(15/16) Updating the desktop file MIME type cache...
(16/16) Updating the MIME type database...
The 5.7 & 5.8 kernel are EOL (End Of Life) and are no longer supported. Use Manjaro Settings Manager > Kernel to remove them. I see you’re already using the stable 5.9. It’s also good to have an LTS kernel installed as backup like 5.4.
