P to list files freezes and I can only quit

[mariannagr1]

Hello,
I have a 1T external hard drive that suddenly became Raw. Quick scan recognises the 2 partitions, I can read files on the ''recovery'' partition of the drive, that is small and reserved for Seagate system files, but when I press p on main partition, scandisk freezes. Had to press the x button and quit after 6 hours of deep scan
Should I wait longer for listing of files? I waited like 30 minutes. I have disabled antivirus.
Now I have started deep scan again I am 24 hours stuck on PC, please help asap. Do you see any issues here?
I do not suspect great physical damage, as I can see my files on my smart TV, but not on either of my laptops.

Hard disk list
Disk /dev/sda - 512 GB / 476 GiB - CHS 62260 255 63, sector size=512 - SAMSUNG MZVLB512HAJQ-000H1, S/N:0025_3887_9107_D14A., FW:EXA73H1Q
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - WDC WD10 EALX-009BA0, S/N:788151703102, FW:15.0

Partition table type (auto): Intel
Disk /dev/sdb - 1000 GB / 931 GiB - WDC WD10 EALX-009BA0
Partition table type: Intel

Analyse Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
NTFS at 120721/55/39
Current partition structure:
1 * HPFS - NTFS 0 32 33 120721 55 38 1939384320 [All 2017]
2 P HPFS - NTFS 120721 55 39 121600 215 23 14131200 [Recovery]

search_part()
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
NTFS at 0/32/33
filesystem size 1939384320
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 32 33 120721 55 38 1939384320 [All 2017]
NTFS, blocksize=4096, 992 GB / 924 GiB
NTFS at 120721/55/39
filesystem size 14131200
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 120721 55 39 121600 215 23 14131200 [Recovery]
NTFS, blocksize=4096, 7235 MB / 6900 MiB
file_pread(5,2,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,1,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,2,buffer,1953525760(121601/90/26)) lseek err Invalid argument
file_pread(5,1,buffer,1953525760(121601/90/26)) lseek err Invalid argument
file_pread(5,8,buffer,1953525248(121601/82/18)) lseek err Invalid argument
file_pread(5,1,buffer,1953525248(121601/82/18)) lseek err Invalid argument
file_pread(5,8,buffer,1953525376(121601/84/20)) lseek err Invalid argument
file_pread(5,8,buffer,1953525504(121601/86/22)) lseek err Invalid argument
file_pread(5,8,buffer,1953525632(121601/88/24)) lseek err Invalid argument
file_pread(5,7,buffer,1953525761(121601/90/27)) lseek err Invalid argument
file_pread(5,2,buffer,1953525760(121601/90/26)) lseek err Invalid argument
file_pread(5,8,buffer,1953525768(121601/90/34)) lseek err Invalid argument
file_pread(5,3,buffer,1953525776(121601/90/42)) lseek err Invalid argument
file_pread(5,3,buffer,1953525823(121601/91/26)) lseek err Invalid argument
file_pread(5,8,buffer,1953525839(121601/91/42)) lseek err Invalid argument
file_pread(5,11,buffer,1953525886(121601/92/26)) lseek err Invalid argument
file_pread(5,2,buffer,1953527808(121601/122/58)) lseek err Invalid argument

Results
* HPFS - NTFS 0 32 33 120721 55 38 1939384320 [All 2017]
NTFS, blocksize=4096, 992 GB / 924 GiB
P HPFS - NTFS 120721 55 39 121600 215 23 14131200 [Recovery]
NTFS, blocksize=4096, 7235 MB / 6900 MiB

interface_write()
1 P HPFS - NTFS 0 32 33 120721 55 38 1939384320 [All 2017]
2 P HPFS - NTFS 120721 55 39 121600 215 23 14131200 [Recovery]

[cgrenier]

No need to search for a lost partition as you didn't lost one.
If TestDisk, Advanced, List doesn't work and your computer freeze, check the CPU or memory usage by testdisk is high.
Does the disk make some unusual noise ?
If there are bad sectors, clone your disk to a new one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf

[mariannagr1]

Thank you for your reply
I cannot seem to be able to mount disk to use with linux. I get the msg ''failed to read...'' and prompted to run chkdsk in windows.
I tried creating a disk image with another program, was getting an astimated time of 24 days to finish!

1. Initialising photorec, just started, nothing on screen yet, hpe it is not frozen as well. How much time should I wait until I start to get results?
2. OK, got results. Estimated time for completion 162,036 hours! That is a lifetime.
3. It is getting better,down to 61,000 hours estimated completion time. 0 files found but it is still early I hope

[recuperation]

1. Initialising photorec, just started, nothing on screen yet, hpe it is not frozen as well. How much time should I wait until I start to get results?

You should not ignore the advice you were given:

If there are bad sectors, clone your disk to a new one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf

Use smartmontools to check your SMART status. You can redirect the output into a SMART log file with
smartctl -a /dev/sdX > yourlogfile.txt
where X dnotes the letter of the dubious drive.

[mariannagr1]

I am not ignoring it. It was just impossible to see the drive with linux, as I said above.

Also, I get: SMART data not available

[recuperation]

I am not ignoring it. It was just impossible to see the drive with linux, as I said above.

Also, I get: SMART data not available

Seeing is not mounting. You spoke about mounting.
You can see a drive with the lsblk command without having it mounted.

https://www.smartmontools.org/browser/t ... rtctl.8.in

Try out the -d parameter with sat,12 or sat,16

[mariannagr1]

Oh my... this is getting too technical for me... Could you please try to explain a little bit?

[recuperation]

Oh my... this is getting too technical for me... Could you please try to explain a little bit?

You can see a device using diskmgmt.msc in Windows without being able to store and load files there.
You either have to assign a drive letter or to assign it to some folder.
Assigning a drive letter is what Windows does automatically.

In linux you can see a device with lsblk. You can only acess the files on its file system if you integrate it in a defined way into your directory tree using the mount command.

[mariannagr1]

Alright. I wonder why ddrescue is suggested while it seems possible to create a disk image using disks. It seems much more simple and user friendly.

[recuperation]

Alright. I wonder why ddrescue is suggested while it seems possible to create a disk image using disks. It seems much more simple and user friendly.

Ddrescue has been programmed to handle discs with broken sectors. Your description in terms of time figures suggests broken sectors.