I was trying to set up a family member up with Linux as a windows replacement. I installed MX Linux xfce on their laptop with separate “/” and “/home” partitions.
Through a comedy of errors, the following occurred:
- On day one, Timeshift was configured to take weekly snapshots of the system files AND their user home folder.
- The initial timeshift snapshot was begun, and then cancelled when they discovered that home files aren’t the intended target, but they noticed growing snapshot files, indicating the cancelation wasn’t complete.
- NCDU was used to remove the files in /home/timeshift
- The family member’s only copies of three days of paid work in a writing program called Bibisco (Java app) disappeared after reboot
The system was rebooted twice before the cause was discovered and shutdown with minimal (5min) use.
I’ve never done any ext4 data recovery, but the tools in Kali seem geared toward common and known filetypes (pdf, jpg, etc).
Should I be looking to restore the timeshift files, or the writing documents (with .bibisco2 file extensions)?
Is this a lost cause?
.bibisco2 are really just zip files which PhotoRec can find, if you want to use that. Good luck.
It seems the files were all living in a timeshift snapshot file, as photorec/testdisk showed no deleted files, and a few deleted empty folders in the /home/timeshift folder. I think this is just a painful lesson that we’ll move on from.
How full is the home partition? I’m surprised the files didn’t show up in testdisk. Sometimes files show up in the incorrect folder in testdisk after being deleted
This system was built last Thursday and had about 204GB of 220GB free.
Sorry for the delay in reply. I was unable to edit my post or make comments for a chunk of the day yesterday.
No worries 😁 lol I’ve been kind of obsessing over this issue, reading timeshift’s code and stuff. Timeshift uses rsync under the hood to do file copying when not in btrfs mode, which uses the delete excluded option to keep excluded files out of snapshots. I was not able to determine if a cancelled snapshot would be rolled back with rsync going the other way, but it would be a major timeshift bug to delete excluded files on restore so I doubt that happened.
Timeshift dos say that it has rsync create hard links for local snapshots on the same fs, so that could complicate matters. even though ncdu supports hard links and not double counting them, I tested deleting hard linked files and it only deletes the file entry from one folder even though it’s aware that the file is used in another folder in the tree.
With that much free space you’re almost guaranteed that the files are still there, even after a rebuild. Idk if you want to get more in depth let me know
Give testdisk a go, see for example this tutorial. It is a terminal utility, so it might take some time to get used to it. But no one can guarantee that it will successfully recover anything, the deleted files stay on the disk only as long as they are not overwritten.
Do you have any idea why the files disappeared after reboot? One thing that comes to mind is that they might have been saved in /tmp, in that case I believe recovery would not be possible.
Regarding to which files you should recover, try all of them and see if you have any luck.
Good luck with recovering the files!
I highly recommend testdisk, but definitely shut down the machine and use another disk (USB drive?) To boot and avoid mounting the disk that may have your files at all. mount read only if you have to. Save the recovered files to a different drive as well, which can be the same USB drive you’re using for recovery. If testdisk doesn’t show the files (in my experience, for drives that have significant free space they will almost certainly be there) you could try photorec, the companion app that does signature based file searches.
Do you have any idea why the files disappeared after reboot?
I suspect the files were actually in a timeshift snapshot, so when those files were deleted, so were the files.
I’ll give your links a thorough read, thanks!
From my understanding, files cannot be directly stored only in a timeshift snapshot – they must be first stored on the disk and only then timeshift can make a backup inside the snapshot. But I have never used timeshift myself, maybe I just completely misunderstand how it works.
Deleting the snapshot files lost considerable data including all files created after the aborted snapshot. The reboot that initially uncovered the problem led to a boot in “basic” xfce, and searching for the work files in read only mode from live boot shows no files/folders created in /home/username after the snapshot. It seems to have behaved like a VMware snapshot that had files living in the snapshot.
Bibisco2 is a JavaScript app, unlike version 1. It seems .bibisco2 files are only created when exported, otherwise it’s in a database somewhere. You can add custom formats in recovery tools like TestDisk and Photorec. I could look around and see if the database or the bibisco2 export files have a header, which I think is required to add a format.
Edit: Nevermind, there’s a paid version which creates bibisco2 files automatically.
Yes, the paid version (in use here) can create those bibisco2 files, though only the auto-save backups are by default. As you said, by default, the work is in a type of database format with a gibberish GUID-like naming convention.
It’s the auto-save files we’re after.
I’m getting setup with an external drive large enough to write recovered files to, but I don’t like my odds at discerning how to add custom formats based on headers. I’ll watch some tutorials and see what I make of it.
Thanks for your comment!!!
Where were the .bibisco2 files stored before they vanished?
