Hey, so I am new to this site and software but it seems that TestDisk is running super slow no matter the interface I use.
I have 2x Seagate Baracudas 4TB HDD's and I installed windows and removed my Linux Gateway that managed my plex server, and one morning before I had my coffee I made a rookie move while in Disk Management I clicked OK without reading and initialized both disks are GPT in windows (while they were formatted with loads of DATA in EXT4)
I have been looking for ways to recover
I was using it over Type-C to 3.1 Type-A, Type-C to Type-C (the enclosure is Type-C 3.1) and I am currently using internal SATA interface.
It seems not what I do but the Analyze Cylinder to recover my EXT4 partitions is going dog slow.
for example 14 hours was like 3% over Type-C
and now with SATA it's been running for over 40minutes and not even 1%
This does not seem right, also these drives are perfectly healthy and are only about a year old and have never been close to filled with data, I just don't want to lose the data on it some would not be able to be recovered otherwise.
as for 'Send it to a professional' aside from not owning a whiteroom myself I am said professional who can do all types of recovery myself which is what lead my to TestDisk as I read it was capable of recovering linux filesystems even in windows... if I have to I suppose I can run a Linux VM and try a Linux recovery software but what would you recommend if any?
Normally I use Stellar Phoenix.
Well thanks for any assistance, have a great day.
~Bean
Drive Healthy Slow TestDisk Internal Read/Analyse
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
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
-
- Posts: 4
- Joined: 13 Jul 2022, 15:39
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
Post your Testdisk logfile and a smartmontools logfile:
viewtopic.php?f=5&t=10910
viewtopic.php?f=5&t=10910
-
- Posts: 4
- Joined: 13 Jul 2022, 15:39
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
I am currently still analyzing the first drive and it's only 3% done. Do you want the me to stop my scan as the current log file does not seem to have any useful information unless you're looking for S/N, Size and Model information on my drives.recuperation wrote: ↑13 Jul 2022, 22:16 Post your Testdisk logfile and a smartmontools logfile:
viewtopic.php?f=5&t=10910
I do have some info from the a different log file from when it was over USB 3.1
I don't know if it's doing that for the current scan unless I cancel it once again, but if you recommend that I will. I will note I am trying to use TestDisk on Windows 11 to try and recover an EXT4 partition.
Will await your response before I actually cancel the scan.file_win32_pread(560,1,buffer,7814035455(486401/53/52)) read err: read after end of file
file_win32_pread(560,1,buffer,7814035456(486401/53/53)) read err: read after end of file
file_win32_pread(560,14,buffer,7814035457(486401/53/54)) read err: read after end of file
file_win32_pread(560,3,buffer,7814035471(486401/54/5)) read err: read after end of file
file_win32_pread(560,3,buffer,7814035518(486401/54/52)) read err: read after end of file
file_win32_pread(560,8,buffer,7814035534(486401/55/5)) read err: read after end of file
file_win32_pread(560,11,buffer,7814035581(486401/55/52)) read err: read after end of file
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
simulate write!
Thank you again for the reply.
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
You should be able to copy your logfile even if your scan is running.
-
- Posts: 4
- Joined: 13 Jul 2022, 15:39
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
So it was not writing to the log file while doing the analyze I ended up passing out and the program froze so I was unable to retrieve the log file of it but I ran it again for a bit and here's basically all it was showing.recuperation wrote: ↑14 Jul 2022, 07:33 You should be able to copy your logfile even if your scan is running.
Code: Select all
Thu Jul 14 09:45:50 2022
Command line: TestDisk
TestDisk 7.2-WIP, Data Recovery Utility, June 2022
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 11.2, Cygwin 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)=4000787030016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=500107862016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=256060514304
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=255303090176
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=119446127104
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\R:)=500090011648
Hard disk list
Disk \\.\PhysicalDrive0 - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ST4000DM004-2CV104, S/N:#######, FW:0001
Disk \\.\PhysicalDrive1 - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - Samsung SSD 850 EVO 500GB, S/N:#######, FW:EMT03B6Q
Disk \\.\PhysicalDrive2 - 120 GB / 111 GiB - CHS 14593 255 63, sector size=512 - HP SSD S700 120GB, S/N:#######, FW:Q0616B1
Disk \\.\PhysicalDrive3 - 256 GB / 238 GiB - CHS 31130 255 63, sector size=512 - KXG60ZNV256G TOSHIBA, S/N:#######., FW:AGHA4101
Partition table type (auto): None
Disk \\.\PhysicalDrive0 - 4000 GB / 3726 GiB - ST4000DM004-2CV104
Partition table type: EFI GPT
Analyse Disk \\.\PhysicalDrive0 - 4000 GB / 3726 GiB - CHS 486401 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=7814037167 (expected 7814037167)
hdr_lba_start=34
hdr_lba_end=7814037134
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]
search_part()
Disk \\.\PhysicalDrive0 - 4000 GB / 3726 GiB - CHS 486401 255 63
block_group_nr 1
recover_EXT2: part_offset problem
block_group_nr 1
recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/29808, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 976754646
recover_EXT2: part_size 7814037168
Filesystem created: Mon Jun 4 14:33:26 2018
Linux filesys. data 0 7814037167 7814037168
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 4000 GB / 3726 GiB
Partition not added.
block_group_nr 3
recover_EXT2: part_offset problem
block_group_nr 3
recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/29808, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 976754646
recover_EXT2: part_size 7814037168
Filesystem created: Mon Jun 4 14:33:26 2018
Linux filesys. data 0 7814037167 7814037168
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 4000 GB / 3726 GiB
Partition not added.
block_group_nr 5
recover_EXT2: part_offset problem
block_group_nr 5
recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/29808, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 976754646
recover_EXT2: part_size 7814037168
Filesystem created: Mon Jun 4 14:33:26 2018
Linux filesys. data 0 7814037167 7814037168
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 4000 GB / 3726 GiB
Partition not added.
block_group_nr 7
recover_EXT2: part_offset problem
block_group_nr 7
recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/29808, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 976754646
recover_EXT2: part_size 7814037168
Filesystem created: Mon Jun 4 14:33:26 2018
Linux filesys. data 0 7814037167 7814037168
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 4000 GB / 3726 GiB
Partition not added.
block_group_nr 9
recover_EXT2: part_offset problem
block_group_nr 9
recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/29808, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 976754646
recover_EXT2: part_size 7814037168
Filesystem created: Mon Jun 4 14:33:26 2018
Linux filesys. data 0 7814037167 7814037168
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 4000 GB / 3726 GiB
Partition not added.
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
Code: Select all
smartctl 7.3 2022-02-28 r5338 [x86_64-w64-mingw32-w11-21H2] (sf-7.3-1)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate BarraCuda 3.5 (SMR)
Device Model: ST4000DM004-2CV104
Serial Number: ######
LU WWN Device Id: 5 000c50 0b03a7b63
Firmware Version: 0001
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5425 rpm
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Jul 14 10:33:51 2022 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 483) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x30a5) SCT Status supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 074 064 006 Pre-fail Always - 23359005
3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 719
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 045 Pre-fail Always - 22334454
9 Power_On_Hours 0x0032 062 062 000 Old_age Always - 33545h+38m+18.743s
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 224
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 071 043 040 Old_age Always - 29 (Min/Max 28/35)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 554
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6359
194 Temperature_Celsius 0x0022 029 057 000 Old_age Always - 29 (0 15 0 0 0)
195 Hardware_ECC_Recovered 0x001a 074 064 000 Old_age Always - 23359005
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10659h+34m+32.942s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2973020431
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 47211574207
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
I can't find anything in your smartmontools log file that indicates problems with the drive.
There is
You are using a SMR drive (shingled magnetic recording) but that should not be slow upon read activity.
Something is wrong either with your drive or with your setup.
I would stop Testdisk and duplicate the drive using ddrescue as described in the manual and operate Testdisk on the copy.
I consider SMR drives as garbage. My opinion is that they are not suitable for use as a single drive in a private environment.
There is
but that might be related to the SMR technology.195 Hardware_ECC_Recovered 0x001a 074 064 000 Old_age Always - 23359005
You are using a SMR drive (shingled magnetic recording) but that should not be slow upon read activity.
Something is wrong either with your drive or with your setup.
I would stop Testdisk and duplicate the drive using ddrescue as described in the manual and operate Testdisk on the copy.
I consider SMR drives as garbage. My opinion is that they are not suitable for use as a single drive in a private environment.
-
- Posts: 4
- Joined: 13 Jul 2022, 15:39
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
Thanks for the tip I will try that and get back if no success. Ya no they are Data Drives, the main drives in both of my systems are NVMe SSD's both pretty decent performing ones. I only used them for longtime persistence storage and read not often wrote too, so it's good I bought them for the size to price. I can't wait for SSD's to price to these pricesrecuperation wrote: ↑16 Jul 2022, 10:01 I can't find anything in your smartmontools log file that indicates problems with the drive.
There isbut that might be related to the SMR technology.195 Hardware_ECC_Recovered 0x001a 074 064 000 Old_age Always - 23359005
You are using a SMR drive (shingled magnetic recording) but that should not be slow upon read activity.
Something is wrong either with your drive or with your setup.
I would stop Testdisk and duplicate the drive using ddrescue as described in the manual and operate Testdisk on the copy.
I consider SMR drives as garbage. My opinion is that they are not suitable for use as a single drive in a private environment.
Re: Drive Healthy Slow TestDisk Internal Read/Analyse
I also initiallized / initialisiert my 6TB HDD EXT4 formated accidentally on Windows 10. The solution that helped me was
where xxx stands for the partition , with sudo fdisk -l I got the "xxx" , in my case it was sdd instead of xxx.
More details on the solution in this [urlhttps://notebookbft.wordpress.com/2017/04/27/recovering-accidentally-formatted-ext4-partition-fixing-superblock/comment-page-1/?unapproved=1880&moderation-hash=e518763590e44a4f3b3c39146d8c2d0d#comment-1880]blog-post[/url]
Code: Select all
sudo fsck.ext4 -vy /dev/xxx
More details on the solution in this [urlhttps://notebookbft.wordpress.com/2017/04/27/recovering-accidentally-formatted-ext4-partition-fixing-superblock/comment-page-1/?unapproved=1880&moderation-hash=e518763590e44a4f3b3c39146d8c2d0d#comment-1880]blog-post[/url]