System stops / freezes while updating virtualbox

I’m running the UPdate 2026-10-28 on another machine right now and the system stops / freezes at VirtualBox 7.2.16-1 -> 7.2-20-1 [533 / 590].
How to proceed?


Moderator edit: Edited topic title to be clear and concise about the issue. Please see How to Post.

Is the virtualbox from the repos or aur? And how are you updating - pamac, pacman, gui? Can you paste the log?

virtualbox from repos, updating $ pamac update, machine is frozen, so no log accessible right now.

Pamac has the habit of crashing the frontend but the backend continues…usually. Is only this terminal frozen or everything, i mean can you open another terminal. If so then wait it out for a bit. If everything is frozen then it is not the frontend i am afraid, and you will end up restarting with the power button and without kernels and with broken system. I hope you has snapshot and usb with iso.

The keyboard is no longer responsive, no CAPS-LOCK LED, no ALT-F1 doing nothing.

  1. Is it save to shutdown the system over night, one processor is at 100 % right now. How should this been done?

  2. I run a backup rsync and timeshift just before $ pamac update, also I have an USB-stick with MANJARO-ISO. Please advice my steps and I will run it tomorrow.

If you restart right now you will definitely have an interrupted update and will have to recover. Not that you really have a choice. If the pc is not overheating (if it is only 1 core maybe it is not), leave it overnight, even if the chance is 1% you have nothing to lose. And maybe the “night shift” i.e. the guys from Australia, Asia and USA will post some more ideas “overnight”(for us). Tomorrow - power button, fsck, timeshift or chroot and repeat update and manually install kernels. :cry:

Thank you @Teo,
no, it’s not overheating. So I will leave it running.
In case the “night shift” has no idea, for sure I will some more detail on

Power button is clear, but the rest? System is ext4.

Well, the filesystems tend to fix themselves automatically these days. Are you with btrfs or ext4? man fsck is a good read :slight_smile: The system should not be mounted, that means live usb without chrooting.

And then you either go back with restoring from timeshift (if on ext4, boot from usb, run timeshift, select the hard disk with the snapshot, hit restore) or go forward trying to repair.

And you might neet to install a kernel after that. pacman -S linux618

This has happened to me in the past when the root partition became too full. It’s well worth checking this, and attending to if needed, e.g. clearing your pacman cache and any other cruft which has accumulated over time.

Since you’re using ext4, manjaro-chroot -a will work fine even if it’s a slightly older .ISO. Then you can check for space issues and (attempt to) re-run the update, after running fsck, of course. :wink:

There is a check for free space before the update begins. In theory it has to prevent this, but sometimes the theory is not like practice.

Indeed. It’s why I always run df -h / before proceeding. :wink:

Thoughts: perhaps pacman can’t accurately estimate the space needed for unpacking stuff. :thinking:

Thank you @BG405,

I always check free space on \ befor updating: It was about 8 GB.

But:

or

The idea is to boot from the Live USB, then do the fsck, and after that, go in with chroot. :wink:

Well, both. For running fsck the partition should be unmounted, for installing stuff with pacman it has to be and you have to be chroot.

You’re not in WinDOS anymore, Toto! :grinning_face:

Thank you @Aragorn,

What am I doing wrong?

In UNIX, the backslash (\) is an escape character. It is not a directory separator. :wink:

@MaMicha / and not \
BUT…
@Aragorn one can never be sure :wink:
A project i am working on now:

Nice, a?

Thank you @Aragorn, my apologies that i did not see my stupid mistyping. Of course, I checked root / using DOLPHIN and got the result of about 8 GB free space.

That’s not very much, it sounds like your Partition is nearly full. I’m pretty sure you should have at least 15GB free on your root partition.