Hey everyone, hoping for some help. My Qubes laptop stopped booting after a dom0 update got cut off partway through (a low-memory popup appeared and the update just stopped). Since then it won’t boot normally anymore. System: Qubes R4.3, kernel 7.1.6 What happens on boot Every time I boot, it drop…

Fixed it, turned out to be exactly what a couple of people suspected: the LVM thin pool ran out of space and locked itself read-only, which is why fsck kept throwing “Input/output error” instead of actually repairing anything. For anyone else who hits this, here’s what worked: 1. Boot into the dra…

[image] Martin32: My Qubes laptop stopped booting after a dom0 update got cut off partway through (a low-memory popup appeared and the update just stopped). [image] Martin32: That “Input/output error” at the end, does that usually mean the drive itself is failing (bad sectors, dying SSD/N…

I am very ignorant about LVM recovery, but I have this bookmark from redhat - some of the things cannot be un-done, so I woul recommend to make a backup of everything before trying to repair… …but the “gathering information” parts may help. I saved it a little time ago, but I cannot guarantee it wa…

Thank you very much for the help

I think I did not do much… Your explanation of your fix seems very clear - thank you for writing it all. I am keeping a bookmark for it! It seems annoying that a disk-full problem can look like a disk-fail problem. Maybe there was some clue in dom0 journal?

How should we interpret Martin’s statement again? When exactly does a hard drive like this become unresponsive, even when there is still enough free space available?

[image] phceac: It seems annoying that a disk-full problem can look like a disk-fail problem. Maybe there was some clue in dom0 journal? Yeah there are some messages in the kernel log when this happens: [image] Q 4.3 Backup Restore process running out of space, but wh…

Laptop won't boot after dom0 update got interrupted, stuck in emergency mode, fsck shows I/O error

User Support

rustybird September 1, 2026, 10:26am 9

Yeah there are some messages in the kernel log when this happens:

But if they’re about the root pool (not the VM pool), they won’t survive a restart.