Puppy Linux Discussion Forum

I was trying the imppup64, and opened my main fossapup's save file from there. I don't know what happened...I didn't delete the contents of the save file, but somehow the save file got empty. I could not restore it. I thought that it might be something wrong with rox and just restarted. After I booted to my main puppy, I found that all the content of my save file had been lost. The worst part is that I don't even have a backup of my savefile, except for few files, and maybe my programmes' source code as well on github. But I don't think I had updated the repository. So I might have lost my latest changes to the important files as well.

Is there any way I can bring my savefile's contents back? Otherwise I will have to do every change that I made to my puppy again, by hand.

** Panicked **

Probably this is what happend: viewtopic.php?t=4720
It's already fixed upstream: https://github.com/puppylinux-woof-CE/woof-CE/pull/2691

As for the recovery, ntfsundelete works pretty well, but here the file itself wasn't deleted, but its contents, so I wouldn't expect much...
If the savefile wasn't encrypted/compressed, maybe testdisk/photorec could find some of the files, but even if, the filenames will be most likely lost...

Greetings!

This won't be much consolation, but I have found that the safest strategy with NTFS is to split off a Linux partition and use a save folder.

@user1234 :-

Little consolation, I know, but I back my saves up once a week, regular as clockwork. It's not a bad habit to get into, goes without saying.

All it takes is a simple copy/paste operation. That's all I've ever done.

It's saved my bacon on more than one occasion..!

Mike.

However.. clicking twice by accident, it promptly mounted the savefile to the same loop device.

I think that's what I did. I wish that I had deleted the overall savefile on its own. Then at least it would have been there in the hdd to get revived with the program that you mentioned .

mikewalsh wrote: Fri May 13, 2022 1:26 pm

It's not a bad habit to get into, goes without saying.

I'd say that rather not backing up is a bad habit, and of course bad habits need to be punished .

Thank you all for looking into my problem , and confirming that nothing can be done .

Next few days would be very tiring, I think .

Try this:

Need to boot not using the bad save so it is not loaded.

Mount the partition the save file is on.

Open a terminal, and enter:

e2fsck /path to save file

For example:
Partition is sda1
Save file name is pupsave.2fs

e2fsck /mnt/sda1/pupsave.2fs

bigpup wrote: Fri May 13, 2022 3:19 pm

Try this:

Need to boot not using the bad save so it is not loaded.

Mount the partition the save file is on.

Open a terminal, and enter:

e2fsck /path to save file

For example:
Partition is sda1
Save file name is pupsave.2fs

e2fsck /mnt/sda1/pupsave.2fs

Too late for that. Have removed the savefile completely .

It's OK for me now, since most of my files are backed up.

The only that is not backed up is a SDL2 (in C) program, which I made when I was learning SDL. It'd be a mere practice for me now to remake the program .