Can't open filesystem. Filesystem seems damaged.

How to use TestDisk to recover lost partition
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
SlickStretch
Posts: 3
Joined: 07 Jun 2019, 14:12

Can't open filesystem. Filesystem seems damaged.

#1 Post by SlickStretch » 07 Jun 2019, 14:23

Sorry if this has been asked, I searched but didn't find a post that seemed to match my problem.

Thanks for taking the time to read my post.

So, I was using this external Iomega HDD and after a while the USB port failed.

I removed the HDD from the enclosure and stuck it in my PC, but now the partition is gone and Windows is showing unallocated space. The same thing happens when I use a SATA-USB adapter.

I've tried using TestDisk and following the instructions here. but when I get to step 8 and press P to list files TestDisk tells me "Can't open filesystem. Filesystem seems damaged." I don't know how to continue with TestDisk.

PhotoRec can recover the files, so I know the data is still there. However, without the filenames/directory structure intact a lot of the files are useless. (For example, this partition contains my Launchbox DB with tens of thousands of small files.) Also, there doesn't appear to be any way to choose which files are recovered, and I don't have enough space to save everything. (There's almost 1TB of data on this drive, and I have about 35GB free space.)

I still have the PCB that it was connected to in the external drive case, but like I said, the USB port is broken and it fell off when I removed the drive from it's enclosure. I'm going to try to solder the USB cable directly to the PCB where the USB port was, but I doubt I will be successful.

Any suggestions on how I can recover the partition? Thanks.

Sponsored links

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

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

#2 Post by cgrenier » 08 Jun 2019, 08:03

Whn running testdisk, try Deeper Search. Check all partitions listed, if you can see your files, switch this partition to P(rimary), on next screen, choose Write, confirm, Quit
If it doesn't work, please copy and paste the testdisk.log file content.

SlickStretch
Posts: 3
Joined: 07 Jun 2019, 14:12

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

#3 Post by SlickStretch » 13 Jun 2019, 00:21

Sorry for the delay. I was waiting for an email notofication that I had a reply, but it never came...

Anyway, I followed your instructions. After the Deeper Scan it then showed the correct name of the partition, but I still get "Filesystem may be damaged" when I try to list files.

Here's the log:

Code: Select all



Wed Jun 12 04:18:23 2019
Command line: TestDisk

TestDisk 7.1-WIP, Data Recovery Utility, May 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 6.4, Cygwin32 2009.0
ext2fs lib: 1.43.1, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.0
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=64023257088
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=200049647616
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdh)=32473088
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=64023257088
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=200049647616
filewin32_getfilesize(\\.\PhysicalDrive4) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive4) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive4
filewin32_getfilesize(\\.\PhysicalDrive5) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive5) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive5
filewin32_getfilesize(\\.\PhysicalDrive6) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive6) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive6
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive7)=32473088
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=63445139456
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=120031543296
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=0
Warning: can't get size for \\.\H:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\J:)=0
Warning: can't get size for \\.\J:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\M:)=0
Warning: can't get size for \\.\M:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\S:)=32430592
Hard disk list
Disk /dev/sda - 64 GB / 59 GiB - CHS 7783 255 63, sector size=512 - M4-CT064M4SSD2, S/N:0000000012040903A52F, FW:0309
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - TOSHIBA MK1059GSM, S/N:X18DFVHRS, FW:GU001U
Disk /dev/sdc - 120 GB / 111 GiB - CHS 14593 255 63, sector size=512 - ST3120213AS, S/N:5LSGLBGD, FW:3.AHL
Disk /dev/sdd - 200 GB / 186 GiB - CHS 24321 255 63, sector size=512 - Maxtor 6L200M0, S/N:L42XXPEG, FW:BACE1GA0
Disk /dev/sdh - 32 MB / 30 MiB - CHS 3 255 63, sector size=512 - Generic- MS/MS-Pro, S/N:058F63646473, FW:1.03

Partition table type (auto): Intel
Disk /dev/sdb - 1000 GB / 931 GiB - TOSHIBA MK1059GSM
Partition table type: Intel

Analyse Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
Geometry from i386 MBR: head=255 sector=63
BAD_RS LBA=1 0
check_part_i386 1 type EE: no test
Current partition structure:
 1 P EFI GPT                  0   0  2 15200  41 63  244190645

Bad relative sector.
No partition is bootable

search_part()
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
NTFS at 0/32/33
Warning: number of bytes per sector mismatches 4096 (NTFS) != 512 (HD)
filesystem size           244138752
sectors_per_cluster       1
mft_lcn                   54537727
mftmirr_lcn               54520146
clusters_per_mft_record   1
clusters_per_index_record 1
     HPFS - NTFS              0  32 33 121575 153 50 1953110016
     NTFS, blocksize=4096, 999 GB / 931 GiB
file_pread(5,2,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,1,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,2,buffer,1953525760(121601/90/26)) lseek err Invalid argument
file_pread(5,14,buffer,1953525762(121601/90/28)) lseek err Invalid argument
file_pread(5,3,buffer,1953525776(121601/90/42)) lseek err Invalid argument
file_pread(5,3,buffer,1953525823(121601/91/26)) lseek err Invalid argument
file_pread(5,8,buffer,1953525839(121601/91/42)) lseek err Invalid argument
file_pread(5,11,buffer,1953525886(121601/92/26)) lseek err Invalid argument
file_pread(5,2,buffer,1953527808(121601/122/58)) lseek err Invalid argument

Results
   * HPFS - NTFS              0  32 33 121575 153 50 1953110016
     NTFS, blocksize=4096, 999 GB / 931 GiB

interface_write()
 1 * HPFS - NTFS              0  32 33 121575 153 50 1953110016

search_part()
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
NTFS at 0/32/33
Warning: number of bytes per sector mismatches 4096 (NTFS) != 512 (HD)
filesystem size           244138752
sectors_per_cluster       1
mft_lcn                   54537727
mftmirr_lcn               54520146
clusters_per_mft_record   1
clusters_per_index_record 1
     HPFS - NTFS              0  32 33 121575 153 50 1953110016
     NTFS, blocksize=4096, 999 GB / 931 GiB
NTFS at 25/159/7
Warning: number of bytes per sector mismatches 4096 (NTFS) != 512 (HD)
filesystem size           244138752
sectors_per_cluster       1
mft_lcn                   54537727
mftmirr_lcn               54520146
clusters_per_mft_record   1
clusters_per_index_record 1
     HPFS - NTFS             25 159  7 121601  25 24 1953110016 [Iomega1T]
     NTFS, blocksize=4096, 999 GB / 931 GiB

LVM magic value at 38061/47/3
file_pread(5,2,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,1,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,2,buffer,1953525760(121601/90/26)) lseek err Invalid argument
file_pread(5,8,buffer,1953525248(121601/82/18)) lseek err Invalid argument
file_pread(5,1,buffer,1953525248(121601/82/18)) lseek err Invalid argument
file_pread(5,8,buffer,1953525376(121601/84/20)) lseek err Invalid argument
file_pread(5,8,buffer,1953525504(121601/86/22)) lseek err Invalid argument
file_pread(5,8,buffer,1953525632(121601/88/24)) lseek err Invalid argument
file_pread(5,1,buffer,1953525759(121601/90/25)) lseek err Invalid argument
file_pread(5,1,buffer,1953525760(121601/90/26)) lseek err Invalid argument

Results
     HPFS - NTFS              0  32 33 121575 153 50 1953110016
     NTFS, blocksize=4096, 999 GB / 931 GiB
     HPFS - NTFS             25 159  7 121601  25 24 1953110016 [Iomega1T]
     NTFS, blocksize=4096, 999 GB / 931 GiB
NTFS Volume is dirty.


dir_partition inode=5
     HPFS - NTFS             25 159  7 121601  25 24 1953110016 [Iomega1T]
     NTFS, blocksize=4096, 999 GB / 931 GiB
ntfs_dir: ntfs_inode_open failed
Directory /
SIGHUP detected! TestDisk has been killed.


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

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

#4 Post by cgrenier » 13 Jun 2019, 05:46

Choose EFI GPT instead of Intel.
Try to list the files from each partition found by TestDisk.

SlickStretch
Posts: 3
Joined: 07 Jun 2019, 14:12

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

#5 Post by SlickStretch » 13 Jun 2019, 19:37

Ok, I tried EFI GPT and got the same error.

The log file exceeds the post character limit, so I posted it on Pastebin here: https://pastebin.com/Tj3hCpyY

Thanks for taking the time to help me.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests