On 6/3/20 6:47 AM, Boot problems wrote:
I tried all that in my new ssd but could not make it work, however I made an
Ubuntu live CD and it worked like a charm, I can mount and see the files on
each vm, so at least my files are not lost forever, but you said that the Attr
should not have an -a- and it does in every single one, is that a problem?
At this point I think is better for me to save the files I really need and
forget about the restoring the vms
That is exact. If you can boot a live linux, first step is ALWAYS data
recovery. Repair attempts come second. You could use an external drive
for that. In this case, the emergency backup procedure is:
cd /externaldrive
(go to mounted external vlume)
truncate -s 200G backup.luks
(where 200G means 200 giga, change appropriately)
losetup /dev/loop0 backup.luks
(make the file a device)
cryptsetup luksCreate /dev/loop0
(setup crypto, you may use your qubes disc-pwd.)
cryptsetup luksOpen /dev/loop0 BACKUP
(open it)
mkfs.ext2 /dev/mapper/BACKUP
(generate easy fs for backup purposes)
mkdir /backup
(make backup path)
mount /dev/mapp/BACKUP /backup
(mount it)
Then create a subfolder for each VM and save all data in the right subdir.
rsync -auv /path-to-vm/ /backup/vm-name/
THINK TO PUT the final "/" at both paths!
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/160fa5e5-4720-c80c-1946-0e746b45708e%40web.de.
