RAW external HDD, filesystem damaged. Boot sector and MFT OK

Using TestDisk to repair the filesystem
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
nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

RAW external HDD, filesystem damaged. Boot sector and MFT OK

#1 Post by nowrooziali77 » 09 Jul 2019, 14:36

Hi. I have a WD My Passport external hard drive which went RAW a few days ago and I recovered the data as much as I could with PhotoRec, but I really prefer not formatting it. TestDisk says boot sector and MFT are OK, but I cannot list the files and "filesystem damaged" shows up. I even tried to rebuild the boot sector. WD Smartware (the software associated with the drive) mounts on the system with no problem so I think Windows has some access to the data. I do not understand the log so I put the parts I think are useful here, but it seems that something is really wrong! No need to mention chkdsk didn't work.
I have Windows 10 pro 64 bit

ntfs_boot_sector
1 P HPFS - NTFS 0 32 33 60715 229 58 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
NTFS at 0/32/33
NTFS at 0/32/33
filesystem size 975398912
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 60962431
clusters_per_mft_record -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
rebuild_NTFS_BS
file_pread(5,16,buffer,23076800(1436/118/27)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076801(1436/118/28)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076802(1436/118/29)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076803(1436/118/30)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076804(1436/118/31)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076805(1436/118/32)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076806(1436/118/33)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076807(1436/118/34)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,23076808(1436/118/35)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076808(1436/118/35)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076809(1436/118/36)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076810(1436/118/37)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076811(1436/118/38)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076812(1436/118/39)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076813(1436/118/40)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076814(1436/118/41)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,23076815(1436/118/42)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723601(2099/50/17)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723602(2099/50/18)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723603(2099/50/19)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723604(2099/50/20)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723605(2099/50/21)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723606(2099/50/22)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723607(2099/50/23)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33723608(2099/50/24)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723608(2099/50/24)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723609(2099/50/25)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723610(2099/50/26)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723611(2099/50/27)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723612(2099/50/28)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723613(2099/50/29)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723614(2099/50/30)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33723615(2099/50/31)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731457(2099/174/61)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731458(2099/174/62)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731459(2099/174/63)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731460(2099/175/1)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731461(2099/175/2)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731462(2099/175/3)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731463(2099/175/4)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731464(2099/175/5)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731465(2099/175/6)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731466(2099/175/7)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731467(2099/175/8)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33731468(2099/175/9)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731469(2099/175/10)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731470(2099/175/11)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731471(2099/175/12)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33731472(2099/175/13)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33731472(2099/175/13)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731473(2099/175/14)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731474(2099/175/15)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731475(2099/175/16)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33731476(2099/175/17)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731477(2099/175/18)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731478(2099/175/19)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33731479(2099/175/20)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732985(2099/199/14)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732986(2099/199/15)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732987(2099/199/16)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732988(2099/199/17)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33732989(2099/199/18)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732990(2099/199/19)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33732991(2099/199/20)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732992(2099/199/21)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732993(2099/199/22)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732994(2099/199/23)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732995(2099/199/24)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33732996(2099/199/25)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732997(2099/199/26)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33732998(2099/199/27)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33732999(2099/199/28)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33733000(2099/199/29)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733000(2099/199/29)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733001(2099/199/30)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33733002(2099/199/31)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733003(2099/199/32)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733004(2099/199/33)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733005(2099/199/34)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733006(2099/199/35)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33733007(2099/199/36)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33745137(2100/137/7)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33745138(2100/137/8)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33745139(2100/137/9)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33745140(2100/137/10)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33745141(2100/137/11)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33745142(2100/137/12)) ReadFile Data error (cyclic redundancy check).

file_pread(5,16,buffer,33745143(2100/137/13)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33745144(2100/137/14)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33745144(2100/137/14)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33745145(2100/137/15)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33745146(2100/137/16)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33745147(2100/137/17)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33745148(2100/137/18)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33745149(2100/137/19)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33745150(2100/137/20)) ReadFile Data error (cyclic redundancy check).

file_pread(5,1,buffer,33745151(2100/137/21)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33746657(2100/161/15)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33746658(2100/161/16)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33746659(2100/161/17)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33882980(2109/30/6)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33882981(2109/30/7)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33882982(2109/30/8)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33882983(2109/30/9)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,33882984(2109/30/10)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882984(2109/30/10)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882985(2109/30/11)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882986(2109/30/12)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882987(2109/30/13)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882988(2109/30/14)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882989(2109/30/15)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882990(2109/30/16)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,1,buffer,33882991(2109/30/17)) ReadFile The request failed due to a fatal device hardware error.

file_pread(5,16,buffer,34511729(2148/65/15)) ReadFile Data error (cyclic redundancy check).

mft at 221242344
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 75520
ntfs_find_mft: mftmirr_lcn 2
ntfs_find_mft: mft_record_size 1024

mft at 221583008
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 75520
ntfs_find_mft: mftmirr_lcn 2
ntfs_find_mft: mft_record_size 1024

mft at 221923672
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 75520
ntfs_find_mft: mftmirr_lcn 2
ntfs_find_mft: mft_record_size 1024

mft at 222264336
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 75520
ntfs_find_mft: mftmirr_lcn 2
ntfs_find_mft: mft_record_size 1024

mft at 272153510
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 2058
ntfs_find_mft: mftmirr_lcn 5162
ntfs_find_mft: mft_record_size 1024

mft at 272156614
read_mft_info failed
ntfs_find_mft: sectors_per_cluster invalid
ntfs_find_mft: mft_lcn 2058
ntfs_find_mft: mftmirr_lcn 5162
ntfs_find_mft: mft_record_size 1024

file_pread(5,1,buffer,975400960(60715/229/59)) ReadFile The drive cannot find the sector requested.

Potential partition:
1 P HPFS - NTFS 16940 196 53 77656 139 15 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
Failed to rebuild NTFS boot sector.

ntfs_boot_sector
1 P HPFS - NTFS 0 32 33 60715 229 58 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
NTFS at 0/32/33
NTFS at 0/32/33
filesystem size 975398912
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 60962431
clusters_per_mft_record -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
repair_MFT
NTFS at 0/32/33
MFT and MFT mirror match perfectly.
MFT and MFT mirror match perfectly.

ntfs_boot_sector
1 P HPFS - NTFS 0 32 33 60715 229 58 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
NTFS at 0/32/33
NTFS at 0/32/33
filesystem size 975398912
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 60962431
clusters_per_mft_record -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
Failed to startup volume: Input/output error.
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
Failed to startup volume: Input/output error.
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
Not an exFAT boot sector.

1 P HPFS - NTFS 0 32 33 60715 229 58 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
Can't open filesystem. Filesystem seems damaged.

ntfs_boot_sector
1 P HPFS - NTFS 0 32 33 60715 229 58 975398912
NTFS, blocksize=4096, 499 GB / 465 GiB
NTFS at 0/32/33
NTFS at 0/32/33
filesystem size 975398912
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 60962431
clusters_per_mft_record -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.

Sponsored links

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

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#2 Post by cgrenier » 10 Jul 2019, 06:15

The log file shows a lot of CRC errors. There are bad sectors. You should clone the disk to a new empty one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf
Once it's done, remove the original disk and try to recover your files from the clone.

nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#3 Post by nowrooziali77 » 10 Jul 2019, 06:23

Thanks! Will give it a try and post the result

nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#4 Post by nowrooziali77 » 17 Jul 2019, 21:35

cgrenier wrote:
10 Jul 2019, 06:15
The log file shows a lot of CRC errors. There are bad sectors. You should clone the disk to a new empty one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf
Once it's done, remove the original disk and try to recover your files from the clone.
I did the ddrescue, but I still do not have direct access to the files on the new drive which I think it's normal. If I recover the files from the new drive, will I get the original names back? I was able to recover almost everything from the old drive, so could you please explain what is the benefit of recovering from the new one?

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

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#5 Post by recuperation » 17 Jul 2019, 23:51

nowrooziali77 wrote:
17 Jul 2019, 21:35
cgrenier wrote:
10 Jul 2019, 06:15
The log file shows a lot of CRC errors. There are bad sectors. You should clone the disk to a new empty one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf
Once it's done, remove the original disk and try to recover your files from the clone.
I did the ddrescue, but I still do not have direct access to the files on the new drive which I think it's normal. If I recover the files from the new drive, will I get the original names back?
No.

I was able to recover almost everything from the old drive, so could you please explain what is the benefit of recovering from the new one?
The benefit is that photorec does not get confused by time-consuming failing sector read operations. Photorec was not designed with failing sectors in mind, otherwise it would behave similarly to ddrescue. Photorescue is about having as much file signatures as possible.
The benefit is that your old drive stops degrading.
The benefit is that SMART parameters get updated so that you can see the real extent of the dammage arisen.
The benefit is that the logfile tells you where the defective sectors are located.

nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#6 Post by nowrooziali77 » 18 Jul 2019, 16:20

recuperation wrote:
17 Jul 2019, 23:51
nowrooziali77 wrote:
17 Jul 2019, 21:35
cgrenier wrote:
10 Jul 2019, 06:15
The log file shows a lot of CRC errors. There are bad sectors. You should clone the disk to a new empty one using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf
Once it's done, remove the original disk and try to recover your files from the clone.
I did the ddrescue, but I still do not have direct access to the files on the new drive which I think it's normal. If I recover the files from the new drive, will I get the original names back?
No.

I was able to recover almost everything from the old drive, so could you please explain what is the benefit of recovering from the new one?
The benefit is that photorec does not get confused by time-consuming failing sector read operations. Photorec was not designed with failing sectors in mind, otherwise it would behave similarly to ddrescue. Photorescue is about having as much file signatures as possible.
The benefit is that your old drive stops degrading.
The benefit is that SMART parameters get updated so that you can see the real extent of the dammage arisen.
The benefit is that the logfile tells you where the defective sectors are located.
I see. Thanks for the information. But since I have all my important data back thanks to PhotoRec, and I can't do anything to fix my old drive, I think I can skip doing another long recovery on the new one. Just one more question, according to the log above, is my old drive any good now? Or will it get messed up again even if I format it?

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

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#7 Post by recuperation » 18 Jul 2019, 20:37

nowrooziali77 wrote:
18 Jul 2019, 16:20
I see. Thanks for the information. But since I have all my important data back thanks to PhotoRec, and I can't do anything to fix my old drive, I think I can skip doing another long recovery on the new one. Just one more question, according to the log above, is my old drive any good now? Or will it get messed up again even if I format it?
Given the high number of read errors I would not reuse it.
Use Crystaldiskinfo or smartmontools to create a logfile of SMART parameters. Compare those to a logfile of a presumably good drive.
Use the same type of drive for comparison - compare hdd to hdd or ssd to ssd.

In your case, look particularly at pending and reallocated sectors.

nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#8 Post by nowrooziali77 » 19 Jul 2019, 11:27

recuperation wrote:
18 Jul 2019, 20:37
nowrooziali77 wrote:
18 Jul 2019, 16:20
I see. Thanks for the information. But since I have all my important data back thanks to PhotoRec, and I can't do anything to fix my old drive, I think I can skip doing another long recovery on the new one. Just one more question, according to the log above, is my old drive any good now? Or will it get messed up again even if I format it?
Given the high number of read errors I would not reuse it.
Use Crystaldiskinfo or smartmontools to create a logfile of SMART parameters. Compare those to a logfile of a presumably good drive.
Use the same type of drive for comparison - compare hdd to hdd or ssd to ssd.

In your case, look particularly at pending and reallocated sectors.
Here's the latest SMART log (unfortunately I didn't have any other external drive to compare with, the only other one is the one I did the ddrescue on :D ):

[WDC WD5000BMVV-11GNWS0WD-WX81A30S0165]
Date=2019/07/19 14:47:19
HealthStatus=2
Temperature=30
PowerOnCount=7438
01=197
03=151
04=85
05=199
ReallocatedSectorsCount=5
07=200
09=70
0A=100
0B=100
0C=93
C0=192
C1=186
C2=117
C4=198
ReallocationEventCount=2
C5=200
CurrentPendingSectorCount=30
C6=100
UncorrectableSectorCount=0
C7=200
C8=100
PowerOnHours=22186
[WDC WD5000BMVV-11GNWS0WD-WX81A30S0165THRESHOLD]
01=51
03=21
04=0
05=140
07=0
09=0
0A=0
0B=0
0C=0
C0=0
C1=0
C2=0

Can you figure out anything from it?

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

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#9 Post by recuperation » 19 Jul 2019, 12:09

nowrooziali77 wrote:
19 Jul 2019, 11:27

ReallocatedSectorsCount=5
ReallocationEventCount=2

CurrentPendingSectorCount=30

UncorrectableSectorCount=0
PowerOnHours=22186
[WDC WD5000BMVV-11GNWS0WD-WX81A30S0165THRESHOLD]
Can you figure out anything from it?
Yes. With 30 unreadable sectors and 5 additional ones that have already been replaced I strongly recommend not to use that drive anymore.
I have drives running for years with zero unreadable sectors.

nowrooziali77
Posts: 6
Joined: 08 Jul 2019, 18:24

Re: RAW external HDD, filesystem damaged. Boot sector and MFT OK

#10 Post by nowrooziali77 » 20 Jul 2019, 19:48

recuperation wrote:
19 Jul 2019, 12:09
nowrooziali77 wrote:
19 Jul 2019, 11:27

ReallocatedSectorsCount=5
ReallocationEventCount=2

CurrentPendingSectorCount=30

UncorrectableSectorCount=0
PowerOnHours=22186
[WDC WD5000BMVV-11GNWS0WD-WX81A30S0165THRESHOLD]
Can you figure out anything from it?
Yes. With 30 unreadable sectors and 5 additional ones that have already been replaced I strongly recommend not to use that drive anymore.
I have drives running for years with zero unreadable sectors.
Thanks a lot. I think this topic can be closed now.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests