When trying to extend dom0’s disk size through the commands:
sudo lvresize --size … /dev/qubes_dom0/root sudo resize2fs /dev/mapper/qubes_dom0-root
I accidentally increased the size & then decreased it right after. This bricked my dom0.
Now whenever I try to start qubesOS I get:
Failed to start File System Check on /dev/mapper/qubes_dom0-root
Running fsck -y /dev/mapper/qubes_dom0-root tells me the filesystem has been modified (I could tell!)
I am on QubesOS 4.3. Any help is appreciated.
In case nothing can be done, is it possible to extract the disk image of my standaloneVMs?
I do not have backups (I was trying to make some in dom0 & that’s why I tried this in the first place).
After I had resized I couldn’t modify anything in dom0 (‘read-only filesystem’). I rebooted once & it worked so I thought nothing of it until I turned it on again.
What other info does fsck print? Also, try running it a couple times in a row, I’ve had occasions where a single pass did not help.
3 Likes
I tried running fsck multiple times, nothing happens.
The output is:
:/root# fsck -y /dev/mapper/qubes_dom0-root isck from util-linux 2.40.4 eZfsck 1.47.1 (20-May-2024)
/dev/mapper/qubes_dom@-root contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
node bitmap differences: +(1703937--1703950) +(1703952--1703956) +(1783958--1703961)
Fix? yes
Free inodes count wrong (6274968, counted=6274945).
Fix? yes
Padding at end of inode bitmap is not set. Fix? yes Error writing file system info: Input/output error
evapper/qubes_domd-root: ***** FILE SYSTEM WAS MODIFIED *****
Edit: the input/output error particularly worries me. Does it mean my drive’s dead? I didn’t have problems with it until now.
Edit 2:
By running smartctl -H /dev/nvme0n1 (where I installed QubesOS) I get;
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
This should mean my drive has no issues, but then why the I/O error?
Have you made a copy of this disk since the error?
No; I have reinstalled qubesOS and I’ll see if the nvme has issues. Nothing of value was lost since I backup my stuff so at worst I’ll have to buy a new one.
1 Like
