Can't open filesystem. Filesytem seems damaged.

Using TestDisk to repair the filesystem
Post Reply
Message
Author
Induna123
Posts: 15
Joined: 17 Jul 2012, 13:21

Can't open filesystem. Filesytem seems damaged.

#1 Post by Induna123 » 30 Oct 2013, 11:05

I've had two IDE PATA hard drives go like this on me in the past couple of weeks. Not sure why. Basically, the drive is still visible in Windows XP. It shows up in My Computer with the drive letter but with no volume showing. It won't let me do chkdsk on the drive either.

Image

I've ran TestDisk on it and the partition shows up but when I try to list files I get the following message "Can't open filesystem. Filesystem seems damaged." I went to the boot option and it says boot sector is OK.

Image

Any ideas on how to at least to view the files and copy them?

Another thing, in Partition Magic 8 the drive shows up as ?m?

Image

Sponsored links

Induna123
Posts: 15
Joined: 17 Jul 2012, 13:21

Re: Can't open filesystem. Filesytem seems damaged.

#2 Post by Induna123 » 01 Nov 2013, 09:38

I forgot to attach the log. Very strange message shows up. Something about "MFT has invalid magic"?

Code: Select all


Wed Oct 30 10:19:11 2013
Command line: TestDisk


TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows XP SP3
Compiler: GCC 4.7, Cygwin 1007.17
Compilation date: 2013-07-30T14:08:52
ext2fs lib: 1.42.2, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=122941242880
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=203927027200
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=122941242880
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=203927027200
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=10618804224
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=112316166144
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=203912884224
Hard disk list
Disk /dev/sda - 122 GB / 114 GiB - CHS 14946 255 63, sector size=512 - Maxtor 6Y120P0, S/N:335958325a504533202020202020202020202020, FW:YAR41BW0
Disk /dev/sdb - 203 GB / 189 GiB - CHS 24792 255 63, sector size=512 - Maxtor 6L200P0, S/N:344c52304c424845202020202020202020202020, FW:BAH41G10

Partition table type (auto): Intel
Disk /dev/sdb - 203 GB / 189 GiB - Maxtor 6L200P0
Partition table type: Intel

Analyse Disk /dev/sdb - 203 GB / 189 GiB - CHS 24792 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 1/1/1
get_geometry_from_list_part_aux head=255 nbr=4
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=255 nbr=4
Current partition structure:
 1 E extended LBA             1   0  1 24791 254 63  398267415
No partition is bootable
 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
$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.

search_part()
Disk /dev/sdb - 203 GB / 189 GiB - CHS 24792 255 63
NTFS at 1/1/1
filesystem size           398267352
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               24891709
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
file_pread(5,2,buffer,398295040(24792/183/32)) lseek err Invalid argument
file_pread(5,1,buffer,398295040(24792/183/32)) lseek err Invalid argument
file_pread(5,1,buffer,398295039(24792/183/31)) lseek err Invalid argument
file_pread(5,14,buffer,398295041(24792/183/33)) lseek err Invalid argument
file_pread(5,3,buffer,398295055(24792/183/47)) lseek err Invalid argument
file_pread(5,3,buffer,398295102(24792/184/31)) lseek err Invalid argument
file_pread(5,8,buffer,398295118(24792/184/47)) lseek err Invalid argument
file_pread(5,11,buffer,398295165(24792/185/31)) lseek err Invalid argument
file_pread(5,2,buffer,398297087(24792/215/63)) lseek err Invalid argument
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2

Results
   L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
Not an exFAT boot sector.

   L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
Can't open filesystem. Filesystem seems damaged.
add_ext_part_i386: max
add_ext_part_i386: min

interface_write()
 1 E extended LBA             1   0  1 24791 254 63  398267415
 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
write_all_log_i386: CHS: 1/0/1,lba=16065

Interface Advanced
Geometry from i386 MBR: head=255 sector=63
NTFS at 1/1/1
get_geometry_from_list_part_aux head=255 nbr=4
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=255 nbr=4
 1 E extended LBA             1   0  1 24791 254 63  398267415
 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB

ntfs_boot_sector
 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
NTFS at 1/1/1
NTFS at 1/1/1
filesystem size           398267352
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               24891709
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.

 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
Can't open filesystem. Filesystem seems damaged.

ntfs_boot_sector
 5 L HPFS - NTFS              1   1  1 24791 254 63  398267352
     NTFS, blocksize=4096, 203 GB / 189 GiB
NTFS at 1/1/1
NTFS at 1/1/1
filesystem size           398267352
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               24891709
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.

TestDisk exited normally.


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

Re: Can't open filesystem. Filesytem seems damaged.

#3 Post by cgrenier » 02 Nov 2013, 11:33

What is the results if you try Repair MFT ?

Induna123
Posts: 15
Joined: 17 Jul 2012, 13:21

Re: Can't open filesystem. Filesytem seems damaged.

#4 Post by Induna123 » 03 Nov 2013, 11:37

Image
Not sure why this happened. It was working perfectly normal. The two drives that have done this were connected to the USB port via USB-to-IDE cable like this one;

http://www.amazon.co.uk/Neewer-SATA-Dri ... 43-9554601

Would this be causing them to go bad like this?

Induna123
Posts: 15
Joined: 17 Jul 2012, 13:21

Re: Can't open filesystem. Filesytem seems damaged.

#5 Post by Induna123 » 06 Nov 2013, 14:14

Seems my screenshots have disappeared.

The message was MFT and MFT mirror are bad. Failed to repair them.

Not good news by the looks of it. I've googled the term and it seems TeskDisk has limited options from here. If both the $MFT and $MFT Mirror are bad then is there no way to reapir the MFT? Some suggestions were use GetDataBack to recover the data and then format the drive, is this the only option left?

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

Re: Can't open filesystem. Filesytem seems damaged.

#6 Post by cgrenier » 08 Nov 2013, 19:28

Yes, you can try this utility. If it doesn't work, use PhotoRec to recover your files (files will have generic filenames instead of the original ones).

yvann
Posts: 1
Joined: 31 Jul 2015, 11:00

Re: Can't open filesystem. Filesytem seems damaged.

#7 Post by yvann » 31 Jul 2015, 12:03

Hi everyone.
I also got to the point where I encountered the very same messages (file system damaged) finally performed the "Write" using TestDisk and it reallocated a partition letter "D:" to my external USB disk (SAMSUNG Momentus ST320LM001 320GB);
I could not anymore open the disk using windows but another thing: CHKDSK D: /F /R and seems to find again the files; But this is the very first time I seek CHKDSK taking that much time (hours).
However, it seems to recover most files.

User avatar
Fiona
Posts: 2836
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: Can't open filesystem. Filesytem seems damaged.

#8 Post by Fiona » 04 Aug 2015, 06:40

You should never use Partition Magic.
It's an old obsolete program and doesn´t support most new features.
It often caused loss of data.
Daterecovery software would be a good solution.
To have another try to run chkdsk would be:
You can run testdisk / Advanced / RebuildBS.
If the boot sector (extrapolated) is different to the current one, you can have a try to list your data and write it.
Then you can have another try to run chkdsk.
You should open your terminal with administrator privileges.
You should run chkdsk from system root like C: or C:\Windows\System32.
Please try the parameter chkdsk Driveletter: /r.
If it doesn´t work for you, after datarecovery using datarecoverty software, you can create a new partition and reformat it and copy your data back.

Fiona

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests