LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
Reload this Page Data recovery
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 08-30-2016, 10:40 PM   #1
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Rep: Reputation: 48
Data recovery

This is a fine mess I've gotten myself into this time. I've got a 2TB WD external HD for backups. There is/was about 1600GB of data on it. I accidentally wrote an ISO of parted magic to it.

At first it wouldn't show up in thunar when plugged in, the OS couldn't see it, but when booting with it plugged in, it would boot to Parted Magic.

So I installed testdisk to my ubuntu OS and ran the scan. Took all night. I tried to restore the only partition it found but it said something wasn't matching up. However, it is now showing up when plugged in. However, the OS can't mount it.

I've got a second 2TB WD external drive with about half of the data backed up on it so it's not a total loss.

So...any suggestions on what can be done here? TIA
 
Old 08-30-2016, 11:46 PM   #2
agillator
Member
 
Registered: Aug 2016
Distribution: Mint 19.1
Posts: 419

Rep: Reputation: Disabled
A little more information, please. What distribution and version are you using? What is your level of experience. Being a member since 2010 would indicate you know what you are doing. So, I assume you tried lsusb to make sure the drive is seen when connected and that you have tried to manually mount the drive. A few more details and perhaps someone can help.
 
Old 08-31-2016, 12:32 AM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,126

Rep: Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120
No, a lot more info. You were in recover mode and didn't bother to note the message ?. And we are supposed to divine what the matter is ?.
Not even a "fdisk -l" to see what testdisk created. Hard to feel sympathetic.

Depending on the size of the iso, that much data at the front of the disk is gone - including partition table and beginning of (at least) the first partition and filesystem metadata. Never to be seen again - without this metadata the filesystem can't be mounted. Files after that point may be recoverable by scraping the disk and looking for file signatures - testdisk or its sister product photorec might work. Long, slow process that won't recover the actual file names. Worth a try though.
 
Old 08-31-2016, 11:54 AM   #4
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by syg00 View Post
No, a lot more info. You were in recover mode and didn't bother to note the message ?. And we are supposed to divine what the matter is ?.
Not even a "fdisk -l" to see what testdisk created. Hard to feel sympathetic.

Depending on the size of the iso, that much data at the front of the disk is gone - including partition table and beginning of (at least) the first partition and filesystem metadata. Never to be seen again - without this metadata the filesystem can't be mounted. Files after that point may be recoverable by scraping the disk and looking for file signatures - testdisk or its sister product photorec might work. Long, slow process that won't recover the actual file names. Worth a try though.


Here's the testdisk log:


Code:
Sun Aug 28 19:54:24 2016
Command line: TestDisk

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 4.5.0-040500-generic (#201603140130 SMP Mon Mar 14 05:32:22 UTC 2016) x86_64
Compiler: GCC 5.3
ext2fs lib: 1.42.13, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.0
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size       1953525168 sectors
/dev/sda: user_max   1953525168 sectors
/dev/sda: native_max 1953525168 sectors
/dev/sda: dco        1953525168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512
Hard disk list
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - WDC WD10JPVT-22A1YT0, S/N:WD-WX21EB1YR339, FW:01.01A01
Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32, sector size=512 - WD My Passport 0748, FW:1019

Partition table type (auto): None
Disk /dev/sdb - 2000 GB / 1862 GiB - WD My Passport 0748
Partition table type: Intel

Analyse Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32
Geometry from i386 MBR: head=64 sector=32
check_part_i386 failed for partition type 17
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1
Current partition structure:
Invalid NTFS or EXFAT boot
 1 * hid. HPFS/NTFS           0   0  1   486  63 32     997376
 1 * hid. HPFS/NTFS           0   0  1   486  63 32     997376

search_part()
Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32

LVM magic value at 269130/1/1

recover_EXT2: s_block_group_nr=0/127, s_mnt_count=93/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4194048
recover_EXT2: part_size 33552384
     Linux                414456   1  1 430839   0 32   33552384
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 17 GB / 15 GiB

recover_EXT2: s_block_group_nr=0/127, s_mnt_count=125/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4194048
recover_EXT2: part_size 33552384
     Linux                444707   0  1 461089  63 32   33552384
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 17 GB / 15 GiB
BAD_RS LBA=970373120 1056
check_part_i386 failed for partition type 07
     HPFS - NTFS          473815   0  1 494292  63 32   41938944

recover_EXT2: s_block_group_nr=0/384, s_mnt_count=8/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 12582912
recover_EXT2: part_size 100663296
     Linux                510626   0  1 559777  63 32  100663296
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 51 GB / 48 GiB

recover_EXT2: s_block_group_nr=0/147, s_mnt_count=80/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4849408
recover_EXT2: part_size 38795264
     Linux                628182   1  1 647125   0 32   38795264
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 19 GB / 18 GiB

recover_EXT2: s_block_group_nr=0/784, s_mnt_count=16/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 25690112
recover_EXT2: part_size 205520896
     Linux                704092   0  1 804443  63 32  205520896
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 105 GB / 98 GiB

recover_EXT2: s_block_group_nr=0/152, s_mnt_count=4/33, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 5012992
recover_EXT2: part_size 40103936
     Linux                828963   0  1 848544  63 32   40103936
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 20 GB / 19 GiB

recover_EXT2: s_block_group_nr=0/384, s_mnt_count=15/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 12582912
recover_EXT2: part_size 100663296
     Linux                903299   1  1 952451   0 32  100663296
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 51 GB / 48 GiB

recover_EXT2: s_block_group_nr=0/103, s_mnt_count=1/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3406080
recover_EXT2: part_size 27248640
     Linux                954935   1  1 968240   0 32   27248640
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 13 GB / 12 GiB

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=8/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                992496   1  1 1006972   0 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=7/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                1025353   0  1 1039828  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=7/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                1041016   0  1 1055491  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=7/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                1061607   0  1 1076082  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=7/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                1076744   1  1 1091220   0 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
BAD_RS LBA=2314908515 454036
check_part_i386 failed for partition type 07
     HPFS - NTFS          1130326  27  4 1920915  11 26 1619125783
This partition ends after the disk limits. (start=2314908515, size=1619125783, end=3934034297, disk end=3906963456)

recover_EXT2: s_block_group_nr=0/113, s_mnt_count=7/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8128
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3705856
recover_EXT2: part_size 29646848
     Linux                1100665   0  1 1115140  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB

recover_EXT2: s_block_group_nr=0/152, s_mnt_count=3/33, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 5012992
recover_EXT2: part_size 40103936
     Linux                1150472   1  1 1170054   0 32   40103936
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 20 GB / 19 GiB

recover_EXT2: s_block_group_nr=0/147, s_mnt_count=64/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4849408
recover_EXT2: part_size 38795264
     Linux                1336043   1  1 1354986   0 32   38795264
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 19 GB / 18 GiB

recover_EXT2: s_block_group_nr=0/135, s_mnt_count=25/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4456192
recover_EXT2: part_size 35649536
     Linux                1385119   0  1 1402525  63 32   35649536
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 18 GB / 16 GiB

recover_EXT2: s_block_group_nr=0/139, s_mnt_count=41/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4579328
recover_EXT2: part_size 36634624
     Linux                1847995   0  1 1865882  63 32   36634624
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 18 GB / 17 GiB

block_group_nr 25

recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=25/143, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 4716800
recover_EXT2: part_size 37734400
     Linux                1872079   0  1 1890503  63 32   37734400
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 19 GB / 17 GiB
NTFS at 1907696/63/32
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (2000 GB / 1862 GiB) seems too small! (< 2014 GB / 1875 GiB)
The following partition can't be recovered:
     HPFS - NTFS          1130326  27  4 1920915  11 26 1619125783
get_geometry_from_list_part_aux head=64 nbr=34
get_geometry_from_list_part_aux head=8 nbr=34
get_geometry_from_list_part_aux head=16 nbr=34
get_geometry_from_list_part_aux head=32 nbr=34
get_geometry_from_list_part_aux head=64 nbr=34
get_geometry_from_list_part_aux head=128 nbr=11

Results
     HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
     Linux                414456   1  1 430839  63 32   33554400
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 17 GB / 15 GiB
     Linux                444707   0  1 461089  63 32   33552384
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 17 GB / 15 GiB
     HPFS - NTFS          473815   0  1 494292  63 32   41938944
     Linux                510626   0  1 559777  63 32  100663296
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 51 GB / 48 GiB
     Linux                628182   1  1 647125  63 32   38797280
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 19 GB / 18 GiB
     Linux                704092   0  1 804443  63 32  205520896
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 105 GB / 98 GiB
     Linux                828963   0  1 848544  63 32   40103936
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 20 GB / 19 GiB
     Linux                903299   1  1 952451  63 32  100665312
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 51 GB / 48 GiB
     Linux                954935   1  1 968240  63 32   27250656
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 13 GB / 12 GiB
     Linux                992496   1  1 1006972  63 32   29648864
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1025353   0  1 1039828  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1041016   0  1 1055491  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1061607   0  1 1076082  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1076744   1  1 1091220  63 32   29648864
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1100665   0  1 1115140  63 32   29646848
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 15 GB / 14 GiB
     Linux                1150472   1  1 1170054  63 32   40105952
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 20 GB / 19 GiB
     Linux                1336043   1  1 1354986  63 32   38797280
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 19 GB / 18 GiB
     Linux                1385119   0  1 1402525  63 32   35649536
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 18 GB / 16 GiB
     Linux                1847995   0  1 1865882  63 32   36634624
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 18 GB / 17 GiB
     Linux                1872079   0  1 1890503  63 32   37734400
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 19 GB / 17 GiB

Hint for advanced users. dmsetup may be used if you prefer to avoid to rewrite the partition table for the moment:
echo "0 3906961408 linear /dev/sdb 2048" | dmsetup create test0
echo "0 33554400 linear /dev/sdb 848805920" | dmsetup create test1
echo "0 33552384 linear /dev/sdb 910759936" | dmsetup create test2
echo "0 41938944 linear /dev/sdb 970373120" | dmsetup create test3
echo "0 100663296 linear /dev/sdb 1045762048" | dmsetup create test4
echo "0 38797280 linear /dev/sdb 1286516768" | dmsetup create test5
echo "0 205520896 linear /dev/sdb 1441980416" | dmsetup create test6
echo "0 40103936 linear /dev/sdb 1697716224" | dmsetup create test7
echo "0 100665312 linear /dev/sdb 1849956384" | dmsetup create test8
echo "0 27250656 linear /dev/sdb 1955706912" | dmsetup create test9
echo "0 29648864 linear /dev/sdb 2032631840" | dmsetup create test10
echo "0 29646848 linear /dev/sdb 2099922944" | dmsetup create test11
echo "0 29646848 linear /dev/sdb 2132000768" | dmsetup create test12
echo "0 29646848 linear /dev/sdb 2174171136" | dmsetup create test13
echo "0 29648864 linear /dev/sdb 2205171744" | dmsetup create test14
echo "0 29646848 linear /dev/sdb 2254161920" | dmsetup create test15
echo "0 40105952 linear /dev/sdb 2356166688" | dmsetup create test16
echo "0 38797280 linear /dev/sdb 2736216096" | dmsetup create test17
echo "0 35649536 linear /dev/sdb 2836723712" | dmsetup create test18
echo "0 36634624 linear /dev/sdb 3784693760" | dmsetup create test19
echo "0 37734400 linear /dev/sdb 3834017792" | dmsetup create test20

interface_write()
 1 P HPFS - NTFS          473815   0  1 494292  63 32   41938944
write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition
You will have to reboot for the change to take effect.

Analyse Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32
Geometry from i386 MBR: head=64 sector=32
check_part_i386 failed for partition type 07
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2
Current partition structure:
Invalid NTFS or EXFAT boot
 1 P HPFS - NTFS          473815   0  1 494292  63 32   41938944
 1 P HPFS - NTFS          473815   0  1 494292  63 32   41938944
No partition is bootable

search_part()
Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 1907697 64 32
NTFS at 1907696/63/32
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
Search for partition aborted
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2

Results
   * HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB

Hint for advanced users. dmsetup may be used if you prefer to avoid to rewrite the partition table for the moment:
echo "0 3906961408 linear /dev/sdb 2048" | dmsetup create test0

interface_write()
 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

ntfs_boot_sector
 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
NTFS at 1/0/1
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size           18159121727489 3906961408
sectors_per_cluster       0 8
mft_lcn                   1 4
mftmirr_lcn               2312 244185087
clusters_per_mft_record   2 -10
clusters_per_index_record 0 1
Boot sector
Status: Bad

Backup boot sector
Warning: number of heads/cylinder mismatches 255 (NTFS) != 64 (HD)
Warning: number of sectors per track mismatches 63 (NTFS) != 32 (HD)
Status: OK

Sectors are not identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
rebuild_NTFS_BS
mft at 1953480696
ntfs_find_mft: mft_lcn             4
ntfs_find_mft: mftmirr_lcn         244185087
ntfs_find_mft: sectors_per_cluster 8
ntfs_find_mft: mft_lcn             4
ntfs_find_mft: mftmirr_lcn         244185087
ntfs_find_mft: mft_record_size     1024
ntfs_find_mft: index_block_size    4096
             New / Current boot sector
filesystem size           3906961408 18159121727489
sectors_per_cluster       8 0
mft_lcn                   4 1
mftmirr_lcn               244185087 2312
clusters_per_mft_record   -10 2
clusters_per_index_record 1 0
Extrapolated boot sector and current boot sector are different.
filesystem size           3906961408 18159121727489
sectors_per_cluster       8 0
mft_lcn                   4 1
mftmirr_lcn               244185087 2312
clusters_per_mft_record   -10 2
clusters_per_index_record 1 0
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented
Not an exFAT boot sector.
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented

 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
Can't open filesystem. Filesystem seems damaged.
filesystem size           3906961408 18159121727489
sectors_per_cluster       8 0
mft_lcn                   4 1
mftmirr_lcn               244185087 2312
clusters_per_mft_record   -10 2
clusters_per_index_record 1 0
Write new boot!

ntfs_boot_sector
 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
NTFS at 1/0/1
NTFS at 1/0/1
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
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.
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
rebuild_NTFS_BS
mft at 1953480696
ntfs_find_mft: mft_lcn             4
ntfs_find_mft: mftmirr_lcn         244185087
ntfs_find_mft: sectors_per_cluster 8
ntfs_find_mft: mft_lcn             4
ntfs_find_mft: mftmirr_lcn         244185087
ntfs_find_mft: mft_record_size     1024
ntfs_find_mft: index_block_size    4096
Extrapolated boot sector and current boot sector are identical.
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
clusters_per_mft_record   -10
clusters_per_index_record 1
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented
Not an exFAT boot sector.
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented

 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
Can't open filesystem. Filesystem seems damaged.
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
clusters_per_mft_record   -10
clusters_per_index_record 1

ntfs_boot_sector
 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1862 GiB
NTFS at 1/0/1
NTFS at 1/0/1
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
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.
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x00020105  size: 1024   usa_ofs: 204  usa_count: 65535: Invalid argument
Record 0 has no FILE magic (0x20105)
Failed to load $MFT: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65534: Invalid argument
Record 6 has no FILE magic (0xffffffff)
Failed to open inode FILE_Bitmap: Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff  size: 1024   usa_ofs: 65535  usa_count: 65534: Invalid argument
Record 5 has no FILE magic (0xffffffff)
repair_MFT
NTFS at 1/0/1
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented
ntfs_device_testdisk_io_ioctl() unimplemented
NTFS filesystem need to be repaired.
ntfs_dir: ntfs_inode_open failed
MFT and MFT mirror are bad. Failed to repair them.
MFT and MFT mirror are bad. Failed to repair them.

ntfs_boot_sector
 1 P HPFS - NTFS              1   0  1 1907696  63 32 3906961408
     NTFS, blocksize=4096, 2000 GB / 1862 GiB
NTFS at 1/0/1
NTFS at 1/0/1
filesystem size           3906961408
sectors_per_cluster       8
mft_lcn                   4
mftmirr_lcn               244185087
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.
Last edited by onebuck; 08-31-2016 at 04:49 PM. Reason: Please learn to use code tags. Mod Edit to clean up post
 
Old 08-31-2016, 12:02 PM   #5
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by agillator View Post
A little more information, please. What distribution and version are you using? What is your level of experience. Being a member since 2010 would indicate you know what you are doing. So, I assume you tried lsusb to make sure the drive is seen when connected and that you have tried to manually mount the drive. A few more details and perhaps someone can help.
I'm using Xubuntu 16.04.1, I indicated that the drive is now "seen" but that my OS fails when trying to mount it.

BTW, thanks for the input.
 
Old 08-31-2016, 12:14 PM   #6
agillator
Member
 
Registered: Aug 2016
Distribution: Mint 19.1
Posts: 419

Rep: Reputation: Disabled
Next question: when you try to manually mount the drive, what is the error message in /var/log/syslog? I suspect syg00 is right in that the first x gb is gone and that would probably include the super block or else somehow the stated fs type is no longer what is there.
 
Old 08-31-2016, 12:15 PM   #7
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by syg00 View Post
Hard to feel sympathetic.
Actually, I don't need sympathy, but if you could send some beer that would be great...LOL

Any way, thanks for the response.

And one of you guys asked if I "know what I'm doing". Well I've been using linux for about 10 yrs so I like to think I do know. However I just "accidentally" wrote an ISO to one of my backup drives, so that really didn't make me look intelligent.
 
Old 08-31-2016, 12:20 PM   #8
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,779

Rep: Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212
What do you recall of how that disk was partitioned/formatted? Single partition or several? Filesystem type(s)? I see that an LVM header was found. Was LVM involved? If so, there would be ASCII information in that LVM header with all the details of the LVM configuration.
 
Old 08-31-2016, 12:31 PM   #9
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by agillator View Post
Next question: when you try to manually mount the drive, what is the error message in /var/log/syslog? I suspect syg00 is right in that the first x gb is gone and that would probably include the super block or else somehow the stated fs type is no longer what is there.
Failed to mount "Parted Magic 2015_05_04".

Error mounting /dev/sdb1 at /media/xxxx/Parted Magic 2015_05_04: Command-line `mount -t "udf" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8" "/dev/sdb1" "/media/xxxx/Parted Magic 2015_05_04"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

And here's what I get with "dmesg | tail:

jars@jars-Satellite-S855D:~$ dmesg | tail
[40959.139414] sd 3:0:0:0: [sdb] Mode Sense: 47 00 10 08
[40959.141944] sd 3:0:0:0: [sdb] No Caching mode page found
[40959.141953] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[40959.161951] sdb: sdb1
[40959.164402] ses 3:0:0:1: Attached Enclosure device
[40959.169918] sd 3:0:0:0: [sdb] Attached SCSI disk
[40963.250055] UDF-fs: warning (device sdb1): udf_load_vrs: No VRS found
[40963.250061] UDF-fs: warning (device sdb1): udf_fill_super: No partition found (2)
[40969.469787] UDF-fs: warning (device sdb1): udf_load_vrs: No VRS found
[40969.469796] UDF-fs: warning (device sdb1): udf_fill_super: No partition found (2)
dd
.
Actually, that was the on screen error message. Here's the /var/log/syslog:

Aug 31 12:29:11 xxxx-Satellite-S855D kernel: [41585.806520] UDF-fs: warning (device sdb1): udf_load_vrs: No VRS found
Aug 31 12:29:11 xxxx-Satellite-S855D kernel: [41585.806528] UDF-fs: warning (device sdb1): udf_fill_super: No partition found (2)
Aug 31 12:29:33 xxxx-Satellite-S855D kernel: [41608.478353] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
Aug 31 12:29:33 xxxx-Satellite-S855D udisksd[3299]: Mounted /dev/sda9 at /media/jars/75f4f25f-1eda-492b-926b-1d2cfaa758d1 on behalf of uid 1000
 
Old 08-31-2016, 12:44 PM   #10
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by rknichols View Post
What do you recall of how that disk was partitioned/formatted? Single partition or several? Filesystem type(s)? I see that an LVM header was found. Was LVM involved? If so, there would be ASCII information in that LVM header with all the details of the LVM configuration.
There was a single NTFS partition on it. As for the LVM, I have no clue, however every linux distro I've installed in the last few years wants LVM partition which I always override with normal partition formatted ext4.

Thx for the input.
 
Old 08-31-2016, 01:19 PM   #11
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 21 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925Reputation: 2925
This doesn't help the OP at all, for which I apologise, but for anyone else perusing this thread, always keep complete copies of your data on two separate devices, preferably in two separate physical locations if you can.

You can never trust a device, whether it be a CD/DVD, memory stick, hard disk drive, cloud storage, or external device, not to give up the ghost and lose your data. So backing up your data should always involve keeping a copy on the source device or, if you need to clear space on your source device, copying the data to 2 target devices.
 
Old 08-31-2016, 01:29 PM   #12
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,661

Rep: Reputation: Disabled
Yea, that's what I was thinking, you have your data and you have backup. When backup gets destroyed you still have your data ... looks like OP's drive does not qualify as a backup.
 
Old 08-31-2016, 02:13 PM   #13
agillator
Member
 
Registered: Aug 2016
Distribution: Mint 19.1
Posts: 419

Rep: Reputation: Disabled
That message is what I expected. To me it means unless you have something that will forensically examine the drive you are out of luck. Do you happen to have a friend at the NSA? As to 10 years of experience, remember there are only two types of people when it comes to things like this: those who have and those who will. Anyone who says otherwise is in the second category well down the road toward transitioning to the first.
 
Old 08-31-2016, 03:30 PM   #14
DVOM
Member
 
Registered: Nov 2010
Posts: 223

Original Poster
Rep: Reputation: 48
Quote:
Originally Posted by agillator View Post
That message is what I expected. To me it means unless you have something that will forensically examine the drive you are out of luck. Do you happen to have a friend at the NSA? As to 10 years of experience, remember there are only two types of people when it comes to things like this: those who have and those who will. Anyone who says otherwise is in the second category well down the road toward transitioning to the first.
That's all I wanted to know. I just needed justification to format the drive and start over. You folks seem to have missed that I have a second 2TB drive that I said had about 50% of the "problem" drives data. I was wrong about that. The "problem" drive had about 1.6TB of data on it, the other drive has 1.4TB of data on it. So, you know, all the stuff I value. All I really lost was about 200 VMs starting at about Ubuntu 8.04 up thru 14.04 and windows 311 thru win10. The ones I actually use I've still got. I also lost about 80 clonezilla images, all of which I actually use I still have. So really all I lost was about 250GB of useless stuff.

So thanks for all the input. I appreciate it.
 
Old 08-31-2016, 05:50 PM   #15
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,779

Rep: Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212
Glad to hear that. Unless the NTFS Master File Table was overwritten (and on a 2TB partition it should be far enough into the disk not to have been touched), there was a good chance that most of the data could have been recovered. But, that would have been quite a bit of work and certainly could not have recovered everything.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: 5 Best Linux Distributions To Recover Dead Computers Data (Linux Data Recovery) LXer Syndicated Linux News 1 08-05-2016 11:10 PM
LXer: 5 Best Data Recovery Tools For Linux To Recover Data Or Deleted Partitions LXer Syndicated Linux News 0 04-18-2015 02:32 PM
Linux rescue disk for data recovery of data on windows laptop with corrupt os Jonjo-k Linux - Newbie 10 01-04-2014 06:00 PM
[SOLVED] Combining anti-virus + data recovery + image recovery? littlebigman Linux - Software 8 08-12-2010 02:39 AM
LXer: Linux Data Recovery on Windows - Is possible through Disk Doctors Linux Recovery Software LXer Syndicated Linux News 0 10-22-2006 12:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 02:21 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration