I did an update on Dom0 this morning and saw a message after creating a temp volume that it was out of space. It then failed to start any VM’s to update any templates, and after a reboot I was left with a system that would not boot. [failedboot] I saved the messages from that failed update but I …

I found the problem. The SSD started to fail during the update and when it made the temproary image device it got marked read only and thus it could not write to it and assumed it was out of space.

Total honesty: I never tried troubleshooting this problem before, but I think reinstall is not necessary… I hope others will give advice but first of all: Make a photo of those error messages! (Doh… you already did! It’s here on the forum.) It seems like at least some of the system has booted. qu…

Connecting a second keyboard to dom0 didn’t help. No joy. it does not respond to any keyboard control keys that I can find. Its not dom0 diskspace, but rather a temporary volume it created for something during the update process. I think that volume was for storing drivers or boot info during that …

Transaction failed: Rpm transaction failed. installing package amd-gpu-firmware-1:20260622-1.fc41.noarch needs 16MB more space on the / filesystem installing package atheros-firmware-1:20260622-1.fc41.noarch needs 46MB more space on the / filesystem installing package linux-firmware-1:20260622-1.fc4…

[image] Dom0 update fails General Trying to get the latest Dom0 update installed, but it fails with: Error Summary ------------- Disk Requirements: At least 133MB more space needed on the / filesystem. Where can I increase this? This is the solution

I also had errors this morning with the update of dom0. I got a transaction failed but my machine rebooted fine. If someone can help me find the actual failed transactions that might help some one

The below is the same step that broke my system this morning. I reinstalled qubes from scratch, and updated it again, and it was the /var/tmp/.. modules.img step that somehow ran out of space. My system still had about 4TB of free space at the time, so I have no clue how this would even happen. [B…

Probably a good idea to avoid restart if you have failed dom0 updates. For getting more space: Try this: sudo journalctl --disk-usage If it shows a lot of space is used by the journal, then there are some journalctl commands to delete some of the old logs. For example, to remove (or clean) everyt…

Hello, I have practically the same problem. I’m getting errors when trying to start the VMs that load at boot time. I’ve never had any problems with dom0 updates. I can’t access the page to enter my username and log in. Apparently, the LUKS decryption was successful because the VM names are showing…

Attached is my full conversation with an AI; it seems it is still recoverable, but I don’t have the expertise to know the right commands to run. Thanks, that is very important information. The fact that lightdm.service is failing explains the black screen: the graphical login manager isn’t startin…

[image] Failed to start qubes-qmemman.service: invalid ELF header User Support Just so you know, I’m having exactly the same problem—I just entered the commands The problem occurred during the major dom0 update to upgrade the kernel from 6.19 to 7.0. Atta…

Failed update this morning 7/2/2026

User Support

Nika July 2, 2026, 6:26pm 5

This is the solution