Update just got stuck, throwing errors can't seem to fix it

[kirk]

I was trying to update the device after a long time of inactivity.
Things seemed to be going ok, but after restart I was faced with the following errors.

I can’t get access to terminal via Ctrl+Alt+F2,F3,..,etc either.

Any suggestions on how to rollback, or any potential solutions to not loose the data?

sudo inxi --verbosity=8 --filter --width

System:
  Kernel: 5.4.242-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64
    root=UUID=0b26cbc0-8e1b-41b4-99e5-a63590294872 rw quiet apparmor=1
    security=apparmor resume=UUID=b1c07d83-1dee-4649-b555-634521c4346b
    udev.log_priority=3
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP 250 G6 Notebook PC
  Mobo: HP model: 8328 v: 23.45 UEFI: Insyde
    v: F.31 date: 11/01/2017
Battery:
  ID-1: BAT1 charge: 25.5 Wh (88.2%) condition: 28.9/31.1 Wh (93.1%)
    volts: 11.9 min: 10.9 model: Hewlett-Packard PABAS0241231 type: Li-ion
Memory:
  System RAM: available: 3.76 GiB used: 1.74 GiB (46.4%)
CPU:
  Info: model: Intel Core i3-6006U bits: 64 type: MT MCP arch: Skylake
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x4E (78) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 799 high: 800 min/max: 400/2000 scaling:
    driver: intel_pstate governor: powersave cores: 1: 799 2: 799 3: 800 4: 800
    bogomips: 16006
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports:
    active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
  Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: iris gpu: i915
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x15c6 built: 2013 res: 1366x768
    hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1366x768
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo missing.
RAID:
  Message: No RAID data found.
Drives:
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD fw-rev: 4C scheme: GPT
Info:
  Processes: 197 Uptime: 21m wakeups: 2 Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.27

[andreas85]

The initramdisk is probably damaged or incomplete. Please provide inxi ! (from usb-boot and chroot )

---

Welcome to Manjaro!

1. Please read the information behind this link. It will help you to post necessary information.

[HowTo] Request support

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major points. Provide context Simply signaling an issue is rarely enough to understand how it occurred. It is thus important to provide details on how it happened: Detail prior actions leading to the issue. List solutions and guides you already tried, with links whene…

2. Please press the three dots … below your post and then press the

• If you give us information about your system, we can see what we’re talking about and make better suggestions.
• You can do this by using inxi in a terminal or in console.

sudo inxi --verbosity=8 --filter --width 

• Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
• Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.

3. Copy the output from inxi (including the command) and paste it into your post.

• To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

[HowTo] Post command output and file content as formatted text

Difficulty: ★☆☆☆☆ Formatting differences Discourse – this forum’s engine – uses Markdown to format its posts, and removes “unnecessary” whitespace. Terminal commands often produce output formatted so that they are better readable by the user, taking advantage of the monospaced font used. Programming code often rely on indentation to make it more readable. Using preformatting in Markdown Markdown includes a pattern to provide preformatting when necessary. You only need to put the part to form…

4. Or we can try to play hide and seek
   Have you already for your problem in the forum ? (Wisdom lies in asking → listening → reading )

[scotty65]

Looks like the systemd v256 upgrade issue:

[Stable Update] 2024-07-01 - Kernels, Systemd, KDE Gear, LibreOffice, Firefox, Wine, Qemu

* Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default.

[yoel]

@scotty65 beat me to it .

If it is indeed related to the massive systemd 256 update, which I think it is, you will need to use a more recent kernel which you can do so by chrooting and install a newer kernel. I can see you are using kernel 5.4; it must be higher than that.

[Stable Update] 2024-07-01 - Kernels, Systemd, KDE Gear, LibreOffice, Firefox, Wine, Qemu

I can’t speak for kernel 5.4 but you should be using a newer kernel anyway. 6.1 and 6.6 are good LTS choices. It appears some users are having issues booting with older kernels, so you might want to install a newer kernel, reboot, then start the system update. If mount | grep cgroup outputs cgroup2, you shouldn’t have issues booting, unless you have a separate issue, of course.

If it still does not work, you will need to update your kernel boot parameters. You can do this by adding the following to the file /etc/default/grub in the GRUB_CMDLINE_LINUX_DEFAULT="" line:

SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 systemd.unified_cgroup_hierarchy=0

Then make sure to run:

update-grub

[cscs]

Just to piggy-back on @yoel’s good notes …

You can also edit boot flags on the fly by pressing E on your grub selection.

Then you will be shown a bunch of text … but your boot options will be on a line beginning with linux and likely be near something like “splash” or “quiet” or “rw”. You can remove or add options there and continue booting with Ctrl+X or F10.

These changes will NOT be persistent and will only affect this boot.

Heres a reference image as example:

https://i.imgur.com/u76ubGv.png

(it is old and from a search engine, so dont expect a perfect match)

[soundofthunder]

@kirk

I was trying to update the device after a long time of inactivity.

Exactly how long?

It’s likely that your system is in an unsupported state.

A rolling release distribution such as Manjaro is not designed to be left unmaintained for extended durations.

I believe this is the root cause, perhaps compounded by recent issues previously mentioned.

That being the case, there is no simple road to recovery.

[BG405]

@soundofthunder

It’s likely that your system is in an unsupported state.

Indeed: what is the result of

pacdiff -o

…?
I guess things like /etc/pacman.conf may need to be attended to, at least.

Stale installations can be fixed, but it takes a bit more time and effort, and probably a bit of research. I’ve done it myself on a few occasions, but then I’ve been ruining* my Manjaro systems for a number of years now.

* Current record is about 7 years on this installation.

[LinuxFreak]

Hi, a fast fix would be backup your /home, reinstall Manjaro and copy it to the new installation.
see

Move /home to another partition

Move /home to another partition After the stable updates 13 May, my PC and notebook were no longer running smoothly. But this also means that I always learn something new. Afterwards I decided to reinstall on the PC. But this time I had created an extra partition for my /home folder. Which worked better than expected. I only had to reinstall the missing programs. Now to my notebook, I would like to shrink the partition I am using now and create a second one. This should become my /home pa…

LF

[BG405]

Indeed; that’s assuming the OP remembers to include all the .dotfiles … would be much easier with a separate /home partition, though. In that case, a reinstall followed by putting the needed programs on, would work just as well, as long as /home isn’t formatted during the (re)installation.

[soundofthunder]

@LinuxFreak

Hi, a fast fix would be backup your /home, reinstall Manjaro and copy it to the new installation.

This is not necessarily a fast fix… we don’t know if the system is currently in a fit state to perform a backup…

Cloning the PO’s /home (with CloneZilla, for example) might well be a better way to go, assuming /home is actually on a separate partition, as @BG405 mentions.

The OP will need to decide which is best for them: Spend the time needed to reinstall Manjaro, along with all of their favourite software; or, spend that time working the problem(s), instead.

[dmt]

@soundofthunder

This is not necessarily a fast fix… we don’t know if the system is currently in a fit state to perform a backup…

All they need is a separate partition or drive with enough space to copy the data.

@soundofthunder

Cloning the PO’s /home (with CloneZilla, for example) might well be a better way to go, assuming /home is actually on a separate partition, as @BG405 mentions.

That’s just another way of copying the data. Also if it’s on a separate partition there’s no need to make a copy in the first place, other than as a part of a normal backup scheme.

[soundofthunder]

All true, but still…

@soundofthunder

not necessarily a fast fix…

…and…

@soundofthunder

The OP will need to decide which is best for them: Spend the time needed to reinstall Manjaro, along with all of their favourite software; or, spend that time working the problem(s), instead.

[andreas85]

@kirk

Drives:
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD fw-rev: 4C scheme: GPT

Where are your partitions ?

Is your disk full ?

Do you use btrfs ?

[Mirdarthos]

@kirk

/dev/sda

That looks like a SATA disk. And along with your screenshot and what I understand from the title and your short explanation of the problem, I’m sorry to say, I think at least your disk gave up the

[Ben]

@kirk

I was trying to update the device after a long time of inactivity.

After a long time of inactivity, your best strategy would be to first check you have snapshots and backups… and second, prepare a handy dandy Ventoy disk with a recent ISO.

Then run the update, if it fails - just reinstall and try restoring as much of your application/settings data as will not cause any issues.

Safety first.

This strategy worked well for me when I bought a new SSD which failed after just one week - I managed to transition to a HDD partition whilst waiting for a replacement SSD, then transition back to the new SSD without too many headaches.

[LinuxFreak]

When Manjaro dropped the support for Nvidia drivers, I got a black screen back then (Although I was on a LTS Kernel…). I tried several weeks to fix this and played with the nouveau driver. Then Manjaro paused quite a time for me. I had similar update problems. In the end I’ve copied my /home to a disk, and then I found an unused SSD in my inventory. So at last I have installed Manaro 24 on a SSD, and had my old /home still on the Sata-Hdd. This took me, only some hours. And now Manjaro is booting under 10 seconds (-;

[Mirdarthos]

Errm…

@LinuxFreak

Majaro

Don’t know that distro…and

@LinuxFreak

dropped the support for Nvidia drivers,

Manjaro supports and distributes the Nvidia driver. Unless you mean the older Nvidia drivers…

[soundofthunder]

@Mirdarthos

Unless you mean the older Nvidia drivers…

I suspect the 470 drivers would likely support most older Nvidia cards that might be reasonably expected to work well enough with a modern Manjaro distribution.

[Mirdarthos]

There are still 390xx drivers in the repositories, even:

$ pamac search --repos nvidia-3
opencl-nvidia-390xx  390.157-14                                            extra
    OpenCL implemention for NVIDIA
linux69-rt-nvidia-390xx  390.157-4                                         extra
    NVIDIA drivers for linux
linux69-nvidia-390xx  390.157-21                                           extra
    NVIDIA drivers for linux
linux66-rt-nvidia-390xx  390.157-19                                        extra
    NVIDIA drivers for linux
linux66-nvidia-390xx  390.157-75                                           extra
    NVIDIA drivers for linux
linux61-rt-nvidia-390xx  390.157-28                                        extra
    NVIDIA drivers for linux
linux61-nvidia-390xx  390.157-123                                          extra
    NVIDIA drivers for linux
linux611-nvidia-390xx  390.157-0.12                                        extra
    NVIDIA drivers for linux
linux610-rt-nvidia-390xx  390.157-4                                        extra
    NVIDIA drivers for linux
linux610-nvidia-390xx  390.157-23                                          extra
    NVIDIA drivers for linux
linux54-nvidia-390xx  390.157-73                                           extra
    NVIDIA drivers for linux
linux515-nvidia-390xx  390.157-102                                         extra
    NVIDIA drivers for linux
linux510-nvidia-390xx  390.157-88                                          extra
    NVIDIA drivers for linux
linux419-nvidia-390xx  390.157-72                                          extra
    NVIDIA drivers for linux
lib32-opencl-nvidia-390xx  390.157-4                                    multilib
    OpenCL implemention for NVIDIA (32-bit)
lib32-nvidia-390xx-utils  390.157-4                                     multilib
    NVIDIA drivers utilities (32-bit)
mhwd-nvidia-390xx  390.157-14 [Installed]                                  extra
    MHWD module-ids for nvidia 390.157
nvidia-390xx-utils  390.157-14                                             extra
    NVIDIA drivers utilities
nvidia-390xx-settings  390.157-4                                           extra
    Tool for configuring the NVIDIA graphics driver
nvidia-390xx-dkms  390.157-14                                              extra
    NVIDIA drivers - module sources

[soundofthunder]

My condolences for anyone still using Nvidia graphics of that vintage; or, Nvidia (at all), for that matter.