I cant add up your numbers. Was the backup made on the same system, or
on some other Qubes system - what version was running on that system?
What filesystem were you running on the source?
It would be helpful if you said what errors you saw when you tried to do
something with the private.img file. “Nothing” is unhelpful when you
haven’t given any detail on what you were doing.
I made a backup on my Laptop, Qubes 4.1
After I backed up everything I made a fresh install.
I installed again 4.1 on same machine.
Same settings, same user, everything was selected same as before.
Filesystem is ext4.
mount: wrong fs type, bad option, bad superblock,
missing codepage or helper program, or other error
With lomount I managed to get my private.img in Qubes Devices and I managed to mount it to some qube.
But when I try to open this disk in Thunar, I just can’t.
Nothing happens.
I tried also to guestfist in my private.img
run
list-filesystem
nothing
Now I can’t mount it, I do not know how to extract it.
Test restore your backup. Follow the restore procedure, selecting Verify backup integrity, do not restore the data. This step is optional but strongly recommended. A backup is useless if you can’t restore your data from it, and you can’t be sure that your backup is good until you try to restore.
To save others from a similar fate, I think it would be very helpful to implement an automatic verification option in the backup interface, if any community devs reading this are willing to help:
You could copy private.img to a no-network VM and run testdisk on it, from the package of the same name. It can recover data from truncated ext4 images (“Non partitioned media”).