PhotoRec stuck scanning Vista drive

Using PhotoRec to recover lost data
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
Post Reply
Message
Author
kaunis
Posts: 4
Joined: 14 Sep 2020, 16:18

PhotoRec stuck scanning Vista drive

#1 Post by kaunis »

Hello friendly and helpful internet strangers,

Disclaimer: I am new at 1) using this specific software, 2) using this kind of command-prompt terminal ui, and 3) generally bad at using computers on this level. So go easy on me. :)

The details:

* Trying to recover deleted photos and videos off an old Windows Vista NTFS internal HDD, ~65GB capacity.

* Using: PhotoRec 7.2 (WIP) (got the folder I’m running it from on an external HDD connected to the Vista pc)

* Workflow: I start PhotoRec from the external HDD (ExFAT), I select the Vista HDD, I don’t touch any options (all default - including brute force which is on by default), the output folder is also default (on my external HDD in a testdisk-7.2-wip folder), and I initiate the search.

* Issue: The scan stops around the vicinity of 129147800 (out of 139511515). Curiously, there is NOT a sector range in the .ses file even covering this numbers (stops at 129145xxx and the next one’s at 130xxxxxx) - perhaps this is why there’s an issue?

* What I have tried thus far: Well, I have perused your forums and read I am supposed to simply stop and exit PhotoRec, edit the .ses file by deleting the sector in question which the scan stops at, save and resume the scan. Merely deleting it does nothing: except slightly change the typical number the scan stops at (to 129146896 rather than 129147800). So I have also tried changing the number at the end of the second line in the .ses file to where I wish the scan to start up (this is what I assume it does!), but the scan resumes at the same point regardless of what I enter there. It always resumes around 114xxxxxx, no matter what I do to the .ses file.

I tried deleting every sector that has already been scanned, to force it to skip the sector area it always stops at - to no avail. The scan still just resumes around 114xxx The .ses looks like this currently:

#1136165368
/dev/sda partition_i386,2,blocksize,4096,fileopt,options,paranoid,keep_corrupted_file_no,freespace,search,status=ext2_off,131776405,inter
131776405-132103796
132104565-132114652
132114981-132137756
132137765-132138124
etc. etc.

So, I am lost. I have really tried looking for solutions on this forum but I can’t.

Please help!

Sponsored links

recuperation
Posts: 788
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: PhotoRec stuck scanning Vista drive

#2 Post by recuperation »

It's not your fault.
kaunis wrote:
14 Sep 2020, 20:24
* Workflow: I start PhotoRec from the external HDD (ExFAT), I select the Vista HDD, I don’t touch any options (all default - including brute force which is on by default), the output folder is also default (on my external HDD in a testdisk-7.2-wip folder), and I initiate the search.
Good error description! :)

viewtopic.php?p=31771#p31771

"brute force" would have been the keyword to search for but you could not have known this.

kaunis
Posts: 4
Joined: 14 Sep 2020, 16:18

Re: PhotoRec stuck scanning Vista drive

#3 Post by kaunis »

Oh no I’m so sorry. I just realised I made a huge mistake here in my description. I assumed “paranoid = yes” always equalled “brute force” but I see the default actually appears to be “Brute force disabled”. So it was disabled all along, though paranoid was turned on... 🤦🏼‍♂️

recuperation
Posts: 788
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: PhotoRec stuck scanning Vista drive

#4 Post by recuperation »

Please make sure that Photorec does not get sabotaged by broken sectors.

For a quick health check install smartmontools.
Run the command

smartctl -a /dev/sdX > C:\mylog.txt

Replace "X" by your drive letter to generate a full report about your drive named "mylog.txt" in the root directory of your C-drive.
Post this log here as an attachment using the attachment tab on the bottom of the forum page.

Depending on the result it might be necessary to duplicate your old drive using ddrescue as described in the manual:

https://www.cgsecurity.org/testdisk.pdf

You would then apply Photorec on your duplicated drive which would not have broken sectors but empty sectors where the source drive was unable to deliver.

kaunis
Posts: 4
Joined: 14 Sep 2020, 16:18

Re: PhotoRec stuck scanning Vista drive

#5 Post by kaunis »

Good evening, sir.

TLDR: Couldnt run the smartmontools test but installed GSmartControl. Test says no errors were found.

Long version: I tried to do as you instructed however I encountered a few bumps. I downloaded smartmontools 7.1 (win32; latest available release), installed successfully, and attempted to run the command you said (“smartctl -a /dev/sdc > C:\mylog.txt“), but was consistently greeted by “Access denied”. Getting root permissions on Vista seems like a nightmare as it’s so broken as it is (I cant connect to the internet on it, I have tried everything; a reinstallation of the OS is probably needed at this point). So I did some googling and found that an app called GSmartControl should be able to yield a similar data output. Output is copypasted below. There’s an option to perform a more extensive test than the one below, by the way.


smartctl 7.1 2019-12-30 r5022 [i686-w64-mingw32-vista-sp2] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 5400.3
Device Model: ST980811AS
Serial Number: 5LY3GGBR
Firmware Version: 3.ALC
User Capacity: 80†026†361†856 bytes [80,0 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Tue Jan 03 03:36:24 2006
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]

=== 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: ( 426) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 84) minutes.
SCT capabilities: (0x0001) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 106 100 006 - 11518134
3 Spin_Up_Time PO---- 099 099 000 - 0
4 Start_Stop_Count -O--CK 099 099 020 - 1945
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 0
7 Seek_Error_Rate POSR-- 085 060 030 - 340180835
9 Power_On_Hours -O--CK 092 092 000 - 7456
10 Spin_Retry_Count PO--C- 100 100 034 - 0
12 Power_Cycle_Count -O--CK 099 099 020 - 1896
187 Reported_Uncorrect -O--CK 100 100 000 - 0
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 061 049 045 - 39 (Min/Max 25/39)
192 Power-Off_Retract_Count -O--CK 100 100 000 - 376
193 Load_Cycle_Count -O--CK 001 001 000 - 398938
194 Temperature_Celsius -O---K 039 051 000 - 39 (0 19 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 063 059 000 - 32845815
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
200 Multi_Zone_Error_Rate ------ 100 253 000 - 0
202 Data_Address_Mark_Errs -O--CK 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory not supported

SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 SL R/O 5 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 SL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 SL R/O 1 NCQ Command Error log
0x11 SL R/O 1 SATA Phy Event Counters log
0x20 SL R/O 1 Streaming performance log [OBS-8]
0x21 SL R/O 1 Write stream error log
0x22 SL R/O 1 Read stream error log
0x23 SL R/O 1 Delayed sector log [OBS-8]
0x80-0x9f SL R/W 16 Host vendor specific log
0xa0 SL VS 1 Device vendor specific log
0xa1 SL VS 20 Device vendor specific log
0xa2 SL VS 101 Device vendor specific log
0xa8 SL VS 20 Device vendor specific log
0xa9 SL VS 1 Device vendor specific log
0xe0 SL R/W 1 SCT Command/Status
0xe1 SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log (GP Log 0x03) not supported

SMART Error Log Version: 1
No Errors Logged

SMART Extended Self-test Log (GP Log 0x07) not supported

SMART Self-test log structure revision number 1

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.

SCT Status Version: 2
SCT Version (vendor specific): 521 (0x0209)
Device State: Active (0)
Current Temperature: 39 Celsius
Power Cycle Min/Max Temperature: --/ 0 Celsius
Lifetime Min/Max Temperature: --/ 0 Celsius

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy
0x8002 2 0 Vendor specific
0x8003 2 0 Vendor specific
0x8004 2 0 Vendor specific

kaunis
Posts: 4
Joined: 14 Sep 2020, 16:18

Re: PhotoRec stuck scanning Vista drive

#6 Post by kaunis »

I was hoping someone would tell me I’ve not edited the .ses file correctly, or something along those lines - as I found several postings on this here forum where users had their Photorec analysis get stuck, in a similar fashion.

I guess I will have to resort to some other option.

recuperation
Posts: 788
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: PhotoRec stuck scanning Vista drive

#7 Post by recuperation »

kaunis wrote:
15 Sep 2020, 20:12
TLDR: Couldnt run the smartmontools test but installed GSmartControl. Test says no errors were found.
What does TLDR means? Do not use abbreviations.
Long version: I tried to do as you instructed however I encountered a few bumps. I downloaded smartmontools 7.1 (win32; latest available release), installed successfully, and attempted to run the command you said (“smartctl -a /dev/sdc > C:\mylog.txt“), but was consistently greeted by “Access denied”. Getting root permissions on Vista seems like a nightmare as it’s so broken as it is (I cant connect to the internet on it, I have tried everything; a reinstallation of the OS is probably needed at this point). So I did some googling and found that an app called GSmartControl should be able to yield a similar data output. Output is copypasted below. There’s an option to perform a more extensive test than the one below, by the way.
You should not run your recovery software of your broken drive.
Three parameters exhibit unsual high figures for my opinion:
1 Raw_Read_Error_Rate POSR-- 106 100 006 - 11518134
7 Seek_Error_Rate POSR-- 085 060 030 - 340180835
195 Hardware_ECC_Recovered -O-RC- 063 059 000 - 32845815
Running your Photorec recovery on a healthy duplicate disc excludes the possibility of a possibly broken source drive as a culprit for a strange Photorec behaviour.

BitterColdSoul
Posts: 32
Joined: 07 Jun 2020, 20:38

Re: PhotoRec stuck scanning Vista drive

#8 Post by BitterColdSoul »

What does TLDR means? Do not use abbreviations.
Have you ever been on that thing called The Internet ? If you had, you'd have been bound to see quite a few TLDRs, unless you have ADD or some other SNAFU.
Three parameters exhibit unsual high figures for my opinion:
Some SMART values are tricky to interpret, as they vary wildly between manufacturers or HDD series. In my experience, Seagate drives tend to have very high “error rate” values, even when working well (people at forum.hddguru.com would say that they are junk to begin with, but I've got several of the reportedly lousy STxxxxDMxxx series, which have been running just fine for several years ; I've had trouble with two Seagate units, but could save almost everything on them, while during the same period a WD failed because of a head issue which is more sudden and more severe, and precludes any recovery attempt without a prior replacement of the head stack assembly, which is nearly impossible to perform in a DIY environment -- sorry, another abbreviation, you're SOL today).

User avatar
cgrenier
Site Admin
Posts: 5305
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: PhotoRec stuck scanning Vista drive

#9 Post by cgrenier »

@BitterColdSoul and @recuperation, please refrain from using abbreviations, it helps non-native English speakers, and keep a more cordial tone.

With some damaged disk, read operations may failed only after 30s. As PhotoRec read every sector, PhotoRec may seem to freeze and be unresponsive.
Sometimes the SMART overall-health self-assessment test result is PASSED for a damaged disk. When it's in FAILED status, there is always a huge problem.
By default, PhotoRec tries to recover fragmented files (simple cases only). In some cases, PhotoRec can be seen looping several times in the same sectors range, it has been improved in PhotoRec 7.2-WIP post August 7 2020 versions.

If you want to edit the photorec.ses file, you have to be very careful to
- respect the blocksize when modifying a range
- update the offset if deleting sector range to not point to a range that has been deleted.
- deal with the partition offset (Sector displayed in PhotoRec are related to the partition beginning, offset in the photorec file are in bytes and related to the disk beginning. Use the correct sector size when converting between sector and bytes).

Post Reply