HFS+ or NTFS damaged file system Topic is solved

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
Locked
Message
Author
lester
Posts: 3
Joined: 23 Feb 2021, 22:57

HFS+ or NTFS damaged file system

#1 Post by lester »

Hello,

After 8 years of keeping the old Lacie/Western Digital 1 TB external drive in a box, I decided to bring it back to life. As I remember, a friend of mine connected the drive to the Mac and accidentally agreed to the NTFS to HFS+ partition format. I don't remember if he tried to restore it to NTFS afterward, but at the moment this is how Testdisk recognizes it after deep scanning:

https://ibb.co/tHfPPS3

Photorec probably found all the files that were on the disk, so I had hope that the partition could be restored as well. Fix CHKDSK didn't help. So I decided to use Testdisk. The sectors were not identical, so I tried unsuccessfully to boot from the original sector and then rebuild it. Now they're identical, but when I trying to open a missing disk partition in NTFS (there is also "Lacie Share" partiition in FAT 32) in windows explorer the system suggests that it is damaged and unreadable. Also the list (P) after a deep Testdik scan doesn't let me browse the files ("Can't open filesystem. Filesystem seems damaged"). MBR and MFT repairs did not help either.

Although I cannot view the list of files after a deep scan, the write option is still available. Does it make sense to fight, or should I give up and this disk should be formatted?

This is what the SMART analysis looks like

https://ibb.co/qssqdYg

And here is the beginning of the Testdisk log:
Partition table type (auto): Intel
Disk /dev/sdb - 1000 GB / 931 GiB - WDC WD10 TPVT-00U4RT1
Partition table type: Intel

Interface Advanced
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
FAT32 at 103361/54/54
Info: size boot_sector 293023744, partition 293023744
FAT1 : 32-35792
FAT2 : 35793-71553
start_rootdir : 71554 root cluster : 2
Data : 71554-293023681
sectors : 293023744
cluster_size : 64
no_of_cluster : 4577377 (2 - 4577378)
fat_length 35761 calculated 35761
1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
2 P FAT32 LBA 103361 54 54 121601 25 24 293023744 [LACIE SHARE]
FAT32, blocksize=32768, 150 GB / 139 GiB
Not an exFAT boot sector.

1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
Can't open filesystem. Filesystem seems damaged.

ntfs_boot_sector
1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
filesystem size 83891367
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 5243210
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.
Attachments
Przechwytywanie.jpg
Przechwytywanie.jpg (64.33 KiB) Viewed 5573 times
Przechwytywanie (1).jpg
Przechwytywanie (1).jpg (103.66 KiB) Viewed 5573 times
smartmontools log.txt
(5.34 KiB) Downloaded 282 times
Last edited by lester on 25 Feb 2021, 01:35, edited 4 times in total.

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

Re: HPFS or NTFS damaged file system

#2 Post by recuperation »

lester wrote: 24 Feb 2021, 00:08 Hello,

After 8 years of keeping the old external drive in a box, I decided to bring it back to life. As I remember, a friend of mine connected the drive to the Mac and accidentally agreed to the NTFS to HFS partition format. I don't remember if he tried to restore it to NTFS afterward, but at the moment this is how Testdisk recognizes it after deep scanning:

Image

Photorec probably found all the files that were on the disk, so I had hope that the partition could be restored as well. Fix CHKDSK didn't help.
I don't understand " Fix CHKDSK didn't help."

The sectors were not identical, so I tried unsuccessfully to boot from the original sector and then rebuild it. Now they're identical, but the drive in Windows keeps calling for formatting, and the list (P) after a deep Testdik scan doesn't let me browse the files ("Can't open filesystem. Filesystem seems damaged"). MBR and MFT repairs did not help either.

Although I cannot view the list of files after a deep scan, the write option is still available. Does it make sense to fight, should this disk already be formatted?
Formatting deletes data and is no mean of recovery.

This is what the SMART analysis looks like

Image

And here is the beginning of the Testdisk log:
Partition table type (auto): Intel
Disk /dev/sdb - 1000 GB / 931 GiB - WDC WD10 TPVT-00U4RT1
Partition table type: Intel

Interface Advanced
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
FAT32 at 103361/54/54
Info: size boot_sector 293023744, partition 293023744
FAT1 : 32-35792
FAT2 : 35793-71553
start_rootdir : 71554 root cluster : 2
Data : 71554-293023681
sectors : 293023744
cluster_size : 64
no_of_cluster : 4577377 (2 - 4577378)
fat_length 35761 calculated 35761
1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
2 P FAT32 LBA 103361 54 54 121601 25 24 293023744 [LACIE SHARE]
FAT32, blocksize=32768, 150 GB / 139 GiB
Not an exFAT boot sector.

1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
Can't open filesystem. Filesystem seems damaged.

ntfs_boot_sector
1 * HPFS - NTFS 0 32 33 103361 54 53 1660495872
NTFS, blocksize=4096, 850 GB / 791 GiB
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
NTFS at 0/32/33
Info: size boot_sector 83891367, partition 1660495872
filesystem size 83891367
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 5243210
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.
I don't know if the Input/output error is caused by failed sectors or by data pointing to a location beyond the end of the disk.
You might produce a smartmontools log file that you can post here to check for errors.
If Testdisk does not work Photorec would be an option or any commercial software.

I can't see your pictures unfortunately - please upload them to this site using the attachment tab.

lester
Posts: 3
Joined: 23 Feb 2021, 22:57

Re: HPFS or NTFS damaged file system

#3 Post by lester »

recuperation wrote: 24 Feb 2021, 21:27
Thank you for your response.
I don't understand " Fix CHKDSK didn't help."
What I meant was that the first thing I did after the drive was detected by the system but Windows Explorer was unable to open it was to open cmd with administrator privileges and try to fix errors using chkdsk e: / f or r /. In both cases he was popping up the same message: "Unable to determine volume version and state. Chkdsk aborted".
I don't know if the Input/output error is caused by failed sectors or by data pointing to a location beyond the end of the disk.
You might produce a smartmontools log file that you can post here to check for errors.
I put it to my first post now with missing screens from Testdisk and SMART analisys.

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

Re: HFS+ or NTFS damaged file system

#4 Post by recuperation »

Your smartmontools report does not show any visible sign of dammage of your disk.

lester
Posts: 3
Joined: 23 Feb 2021, 22:57

Re: HFS+ or NTFS damaged file system

#5 Post by lester »

So how can I recover partition with original names of files?

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

Re: HFS+ or NTFS damaged file system

#6 Post by recuperation »


Locked