Qubes OS Emergency Backup Recovery Issue

User Support
#1

I used Qubes OS for awhile, but eventually decided to move to Fedora. Right now, I’m trying to extract a file from my Qubes OS backup. I’m using the instructions here:

I was able to go through steps 1-6 without any issues.

When I execute step 7:

[user@restore vm1]$ sudo mkdir /mnt/img
[user@restore vm1]$ sudo mount -o loop vm1/private.img /mnt/img/

I get an error message, and learn more from the dmesg command:

dmesg | tail:
[379210.165574] loop11: detected capacity change from 0 to 4962553
[379210.166889] EXT4-fs (loop11): bad geometry: block count 52428800 exceeds size of device (620319 blocks

I didn’t quite understand this and thought it was a memory issue. I copied the “vm1” directory to my main Fedora drive where there’s tons of memory, but I got the exact same error.

Some people online say that using “resize2fs” can help, but I don’t really understand exactly how I would apply that in my situation.

My “vm1” directory looks like this:
-rw-r–r–. 1 user user 2540827136 Sep 17 18:06 private.img
-rw-r–r–. 1 user user 104857728 Sep 17 18:04 private.img.000.enc
-rw-r–r–. 1 user user 104857728 Sep 17 18:04 private.img.001.enc
-rw-r–r–. 1 user user 104857728 Sep 17 18:04 private.img.002.enc
…
-rw-r–r–. 1 user user 104857728 Sep 17 18:06 private.img.379.enc
-rw-r–r–. 1 user user 7180041 Sep 17 18:06 private.img.380.enc

Any thoughts would be most welcome.

Thank you.

#2 
resize2fs private.img
#3

Don’t - there’s no point in resizing the filesystem inside the image file. It’s the image file itself that’s incomplete.

private.img looks like it wasn’t fully extracted: The (compressed!) .enc parts already sum up to 380*104857728 + 7180041 = 39853116681 bytes, so the decompressed private.img should take up more disk space than that instead of much less.

No errors or warnings at all?