Accidentally deleted partition, how long should Quick Scan take for a 2TB drive?

[house3272]

I was re-imaging my computers (via Win 10 boot image) and accidentally forgot to unplug the storage drive and fat finger deleted the partition on it instead of clicking my OS drive.
(Storage SSD's disk was detected as Disk 0 while the OS SSD was Disk 1, didn't look and just clicked Delete on 1st thing)
Immediately quit the reimage, booted back into the OS. Had a heart attack when my D drive was gone and is now just unallocated space.
I do have a couple of backups, but haven't synced in a while


Running testdisk, there's 243200 cylinders for my 2TB SSD formatted as NTFS, but the initial quick scan is very slow, is this normal?
20 minutes and it's only done about 1000/243200.
Is that normal?

Code: Select all

Mon Nov  1 11:26:07 2021
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, September 2021
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 11.2, Cygwin32 3001.4
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=500107862016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=62176362496
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=999546739712
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=559566848
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=62175297024
Hard disk list
Disk \\.\PhysicalDrive0 - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - CT2000MX500SSD1, S/N:1851E1DF9D2E, FW:M3CR023
Disk \\.\PhysicalDrive1 - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - Samsung SSD 860 EVO 500GB, S/N:S4XANE0M743318Z, FW:RVT03B6Q
Disk \\.\PhysicalDrive2 - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - Samsung SSD 970 EVO Plus 1TB, S/N:0025_3856_0142_298D., FW:2B2QEXM7
Disk \\.\PhysicalDrive3 - 62 GB / 57 GiB - CHS 7559 255 63, sector size=512 - SanDisk Ultra, S/N:4C530001070716109501, FW:1.00
Drive D: - 559 MB / 533 MiB - CHS 133 64 32, sector size=2048 - Msft Virtual DVD-ROM, FW:1.0

Partition table type (auto): EFI GPT
Disk \\.\PhysicalDrive0 - 2000 GB / 1863 GiB - CT2000MX500SSD1
Partition table type: EFI GPT

Analyse Disk \\.\PhysicalDrive0 - 2000 GB / 1863 GiB - CHS 243201 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=3907029167 (expected 3907029167)
hdr_lba_start=34
hdr_lba_end=3907029134
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
check_part_gpt failed for partition
 1 P MS Reserved                   34      32767      32734 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
 1 P MS Reserved                   34      32767      32734 [Microsoft reserved partition]
 1 P MS Reserved                   34      32767      32734 [Microsoft reserved partition]

[recuperation]

Running testdisk, there's 243200 cylinders for my 2TB SSD formatted as NTFS, but the initial quick scan is very slow, is this normal?
20 minutes and it's only done about 1000/243200.
Is that normal?

Ignoring the fact that the quick scan does not read every sector you arrive at a read speed of

[2 TB * 1000/243200]/ 20 min =
[2000 GB * 1000/243200/20 ] / min =
[2000 GB * 1000/243200/20 ] / (60 sec) =
[2000 000 MB * 1000/243200/20/60 ] / sec =

6,85 MB /sec

This is in fact very slow compared to the native transfer speed of a modern SSD and the fact that Testdisk does not reads every sector in quick scan.

You could interrupt your scan and post your SMART log here.
viewtopic.php?t=11092
Depending on the result it might be necessary to clone your drive.

(Storage SSD's disk was detected as Disk 0 while the OS SSD was Disk 1, didn't look and just clicked Delete on 1st thing)

You have succesfully hidden how you deleted your partition. At this stage of scan Testdisk should have already walked over your Microsoft reserved partition and should have found your main partition assuming that there is no empty storage hole between the Microsoft reserved partition and your desired partition. If you did something which should have just changed the partition table, your lost partition should already have appeared in Testdisk.

[house3272]

Sorry it was via the windows installer.

Delete button on that screen, which I'd guess uses diskpart's delete command.

Welp, that's what I thought as well.
That's scary. Guess I'll send it to a local shop then.