Fsck killed the ext4 partition. How to recover data?

Question

linux

Good afternoon!
The story is sad. There was a server at home, under ubuntu, for torrents and backups of the system. At some point, there was not enough space and I connected another screw. But it worked strangely and I often ran fsck on it. Once I missed a partition and ran fsck -y on the main hard drive. He found something on it, corrected something and that's it, after that the system does not boot.

mount: mounting /dev on /root/dev failed: No such file or directory<br/>
mount: mounting /sys on /root/sys failed: No such file or directory<br/>
mount: mounting /proc on /root/proc failed: No such file or Direcoty<br/>
<br/>

Dear gurus, tell me what to do? booted from live cd, tried to run fsck. answer:

Filesystem mounted or opened exclusively by another program?

Same thing when running e2fsck, and mount doesn't help either.

mount /dev/sda2 /mnt<br/>
mount: /dev/sda2 already mounted or /mnt busy<br/>

Ps. google did not give answers, it is advised to go through fsck - does not work, mounting - does not work, e2fsck - does not work.

Answer 1

the stump is clear, all of the following must be done with a copy of the FS, in order not to lose it completely if there is still a chance
1. tune2fs -l / dev / sd? - what does he say? (The command means "print the contents of the superblock in human-readable form")
2. if tune2fs shows some "extra" flags, etc., they can be fixed using debugfs set_super_value (read man!). And in general, debugfs will demonstrate whether something can be done with the FS, or is that all. By the way, with it you can also pull spare superblocks, if their contents are different and more adequate - you're in luck. after that - fsck By the
way, just fsck with another (spare) superblock for reading information about the file system can help

Answer 2

show mount

Answer 3

This can happen by running fsck on the mounted partition. I was unable to restore the FS. You can try to recover data using testdisk and photorec.