Recovering ext4-Partition: "Large File Sparse SB Backup SB"

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Locked
Message
Author
PhilippL
Posts: 2
Joined: 18 Nov 2019, 18:45

Recovering ext4-Partition: "Large File Sparse SB Backup SB"

#1 Post by PhilippL »

Hello,
I had Linux on my notebook with 2 primary partitions, system and data, both ext4. Then I had to switch to Windows and changed the second partition to a logical FAT32-partition. Then I realised what I had done and that my backup is a couple months old. Stupid decision.

Here are screenshots from testdisk:

Image

Image

It says "Large File Sparse SB Backup SB" and testdisk doesn't show me any files: "filesystem may be damaged"

Is there any chance to recover the data from the partition at least partialy?

Thank you very much, Philipp
User avatar
cgrenier
Site Admin
Posts: 5441
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Recovering ext4-Partition: "Large File Sparse SB Backup SB"

#2 Post by cgrenier »

To try to recover your ext4 partition, use the arrow keys to switch this partition to P(rimary).
On next screen, choose Write, confirm, Quit
After a reboot, run again TestDisk, Advanced, select the Linux partition, SuperBlock, use the information to run fsck.
You can run fsck from a Linux LiveDVD/LiveUSB.
If fsck failed to repair your filesystem, use PhotoRec to recover your data. PhotoRec will not recover the original filenames.
Good luck
PhilippL
Posts: 2
Joined: 18 Nov 2019, 18:45

Re: Recovering ext4-Partition: "Large File Sparse SB Backup SB"

#3 Post by PhilippL »

Thank you very much for your help!

I did run fsck with this result:
Image

Now the filesystem looks like this:
Image

Should I run fsck manually, like fsck recommends?
Locked