These are my notes that I thought I would share. This still works with Precise 5.4.3.
## Access encrypted save file
## Note: you need to have a free loop device, you can't use them all up with
## mounted SFS files and expect this to work.
## Find a free loop device
#losetup-FULL -f
/dev/loop2
## Connect the loop device to the pupsave file
#losetup-FULL -e aes /dev/loop2 /mnt/sda1/downloads/lupusave_crypta-rob_2.2fs
Password:
## repair ext2 system on pupsave file ... before mounting...
# e2fsck /dev/loop2
## If you wish to mount and look at the files...
# mkdir /tmp/encrypt
# mount -t ext2 /dev/loop2 /tmp/encrypt
## unmount the mounted save file
#umount /tmp/encrypt
## unmount (release?) loop device
#losetup-FULL -d /dev/loop2
## Note: when I booted to ram without a pupsave file this process for fixing
## a save file did not work. Some issue with the LOOP devices. So you need to boot
## to a puppy with a save file and then run the repair on the save file that is not
## being currently used.
I hope this helps,
Rdog
How to repair a corrupted encrypted pupsave file
The pupsave file contains a filesystem that is compressed using squashfs and then layered using aufs with other filesystems which are also compressed and saved in files using squashfs.Flash wrote:Apparently it is the filesystem, not the encrypted file it contains, that is somehow corrupted. Is that correct?
So because the pupsave file is "a file" and "a filesystem" there are at least 2 filesystems that may be corrupted and require repair.
The filesystem within the pupsave file is what often requires repair when personal files become damaged or the pupsave file can no longer be accessed. The instructions in my first post are about repairing this filesystem which is contained within the pupsave file.
For example the filesystem in the pupsave file is of type ext2 in this case, where as the filesystem of where the pupsave file is saved is fat32 (on a usb key) but could also be ext4 on my hard drive etc..
Take Care,
Rdog