Dracut emergency: lvm lvscan shows no volumes at all, boot fails

apparatus · June 27, 2024, 5:56am

Maybe the same issue as here:

Unable to boot | "qubes_dom0-root does not exist" | Possible LVM problem

opened 11:25PM - 12 Nov 23 UTC

T: bug P: default needs diagnosis C: storage affects-4.1

As requested [here](https://github.com/QubesOS/qubes-issues/issues/5973#issuecom…ment-1806922191), I am opening a new issue for this bug. ### Qubes OS release R4.1.2 ### Affected component(s) or functionality Entire system ### Brief summary After months of using Qubes, system is unable to start after disk decryption. ### Steps to reproduce Unknown Uneducated guess to reproduce the bug (based on related previously reported issues): run out of disk space ### Expected behavior Normal system startup, with the login screen appearing after disk decryption. ### Actual behavior The following error screen appears after I enter the password to decrypt the disk: ![01](https://github.com/QubesOS/qubes-issues/assets/150536125/210d57e9-6e94-477f-a3a4-75412998950e) Here is the generated [rdsosreport.txt](https://github.com/QubesOS/qubes-issues/files/13329223/rdsosreport.txt) If I press Control-D to continue, this is what I get: ![02](https://github.com/QubesOS/qubes-issues/assets/150536125/fba25b59-bc4e-438d-845e-fa48800deb9b) ### Additional context - My keyboard strangely stopped working out of nowhere the session before the bug happened; - Still in the session before and in other previous (but recent) instances, system prompted a warning message stating that I was running out of space. I don't recall exactly, but at the time I assumed that the space it was referring to was one of my VMs, since that warning message only appeared after starting that VM, so I simply increased the space allocated to it in its settings; - After this bug started happening, the decryption process is taking a much longer time than before just to take me to that error screen. However, one thing I have certainly noticed is that the time to decrypt the disk has gradually become longer over time since Qubes fresh install. - I managed to recover the files that were in the VMs to an external drive by booting from a live usb Linux Mint image. After starting Mint, the drive in which Qubes is installed appeared as available. I just double clicked it, entered the password to decrypt the disk, and voila, the VMs showed up. ### Solutions you've tried After inspecting rdsosreport.txt (journalctl), I noticed a familiar “Manual repair required!” warning, something common in the other reported cases: > [ 40.070355] dom0 dracut-initqueue[1111]: Check of pool qubes_dom0/root-pool failed (status:1). Manual repair required! [ 181.207297] dom0 dracut-initqueue[554]: Warning: dracut-initqueue timeout - starting timeout scripts So I tried to follow the solutions suggested in these other cases. In the maintenance/emergency shell, I tried running the command `lmv lvconvert --repair qubes_dom0/root-pool`, which resulted in the same “Manual repair required!” error: ![03](https://github.com/QubesOS/qubes-issues/assets/150536125/c619cfef-ca9d-4dad-98d6-95005767413d) Following the assumptions that this problem was related to the lack of disk space, I deleted one of my VMs that had a large space allocated using the `lvremove` command. I was successful in removing the VMs, but the problem persisted. One of the helpful community members theorized that I ran out of space in dom0 (root-pool) and suggested me to free up the space in it by extending the volume. So I tried to extend it, but I was unsuccessful. ![04](https://github.com/QubesOS/qubes-issues/assets/150536125/fe818b0c-ec6b-4798-b170-0cc03838927c) I also misinterpreted one of his instructions, and ended up trying to extend the vm-pool as well, despite its lack of correlation with the root-pool. Still, I came across this rather questionable warning message that might be worth mentioning: ![05](https://github.com/QubesOS/qubes-issues/assets/150536125/e331de2a-fe66-4c61-a245-003c0c817a5f) ### Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues https://github.com/QubesOS/qubes-issues/issues/5372 https://github.com/QubesOS/qubes-issues/issues/5973 https://www.reddit.com/r/Qubes/comments/fszsu7/qubes_suddenly_broken_warning_devqubes_dom0root/?rdt=61290 https://forum.qubes-os.org/t/qubes-dom0-root-does-not-exist/8600/23 https://forum.qubes-os.org/t/emergency-dracut-shell-qubes-not-working-for-no-reason/6717/3

Possible LVM corruption because there was not enough free space?