cgsecurity.org

Using Eraser (https://sourceforge.net/projects/eraser/reviews/) I destroyed my partition table - it's probably Eraser's bug - I pointed out correct partition (Lenovo V530-15ICR, Win 10 Pro, OS on 256 GB SSD - partition C:, data on Toshiba HDD 1TB - partition E:) - I had connected via USB 3.0 an old sata drive removed from another computer, from which I wanted to "erase" data with Eraser - a bsod appeared when trying to overwrite the aforementioned sata drive with Eraser. After restarting, only the message appears: "Warning, no operation system found". After booting from a USB stick with Microsoft's "media creation tool" diskpart shows "disk0" of 931GB (partition E: "DATA") and "disk1" of 238GB (system partition on SSD C:).
The command diskpart - "dir c:" - lists the former E: partition with the "DATA" label I once created. "dir e:" ends with the message: "device not ready". The Toshiba drive is available - with the Linux distribution on USB I copied the data. Partition C: ( /dev/nvme0n1 - SSD) in Gparted is shown as "unallocated".

Here is the fdisk log: https://ghostbin.com/McIOo/raw

The San Disk Cruzer Blade is the flash drive I used to boot Gparted with fdisk. Based on the logs, is it possible to determine what exactly would need to be done one by one in fdisk to repair the partitioning table?

Please post your Testdisk logfile.

My mistake in the first post - instead of "Here is the fdisk log: https://ghostbin.com/McIOo/raw"
should be: "here is the testdisk log: https://ghostbin.com/McIOo/raw".
The above is a record of the results of the "analyze" function in testdisk.