Unable to force disk geometry past 8TB for recovery

How to use TestDisk to recover lost partition
Post Reply
Message
Author
murkyl
Posts: 6
Joined: 19 Jun 2012, 17:00

Unable to force disk geometry past 8TB for recovery

#1 Post by murkyl » 20 Jun 2012, 02:11

I was hoping someone might be able to help me recover an EXT4 partition. I lost 2 drives in my RAID5 the other day and trying to find some instructions online led me to hose the existing file system. For some reason, all the tools complain that my partition is larger than the space allowed, not by much, but it's still larger. I tried going to the section of the tool to adjust the disk geometry to try and get it to work but it doesn't let me enter any cylinder values that would result in a partition larger than 8 TiB. The partitions it finds I think are the correct ones.

Any assistance would be greatly appreciated. I'm copying some screen dumps below of the RAID itself and the output of the tool:

======================================================================
RAID rebuild
======================================================================

medusa ~ # mdadm --verbose --create /dev/md5 --level=5 --raid-devices 8 /dev/sd{c..i}1 missing
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: chunk size defaults to 512K
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdd1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: partition table exists on /dev/sdf1 but will be lost or
meaningless after creating array
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1863368260K mtime=Sun Feb 26 11:52:06 2012
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: partition table exists on /dev/sdh1 but will be lost or
meaningless after creating array
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdi1 appears to be part of a raid array:
level=raid5 devices=8 ctime=Mon Jun 18 19:20:37 2012
mdadm: size set to 1953510400K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md5 started.
medusa ~ # mount /mnt/raid2/


======================================================================
Screen output
======================================================================

Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4

The harddisk (14 TB / 12 TiB) seems too small! (< 14 TB / 12 TiB)
Check the harddisk size: HD jumpers settings, BIOS detection...

The following partitions can't be recovered:
Partition Start End Size in sectors
ext4 28743 1 2 3418674631 1 1 27349167104
ext4 1602567 1 2 3420248455 1 1 27349167104
> ext4 2651143 1 2 3421297031 1 1 27349167104

======================================================================
Log output
======================================================================

Tue Jun 19 08:57:06 2012
Command line: TestDisk

TestDisk 6.13, Data Recovery Utility, November 2011
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 3.0.6-gentoo (#3 SMP PREEMPT Sat Nov 5 22:28:43 PDT 2011) x86_64
Compiler: GCC 4.4
Compilation date: 2011-11-15T02:42:19
ext2fs lib: 1.41.9, ntfs lib: libntfs-3g, reiserfs lib: 0.3.1-rc8, ewf lib: 20100226
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 117210240 sectors
/dev/sda: user_max 117210240 sectors
/dev/sda: native_max 117210240 sectors
/dev/sda: dco 117210240 sectors
/dev/sdb: LBA, HPA, LBA48, DCO support
/dev/sdb: size 117210240 sectors
/dev/sdb: user_max 117210240 sectors
/dev/sdb: native_max 117210240 sectors
/dev/sdb: dco 117210240 sectors
/dev/sdc: LBA, HPA, LBA48, DCO support
/dev/sdc: size 3907029168 sectors
/dev/sdc: user_max 3907029168 sectors
/dev/sdc: native_max 3907029168 sectors
/dev/sdc: dco 3907029168 sectors
/dev/sdd: LBA, HPA, LBA48, DCO support
/dev/sdd: size 3907029168 sectors
/dev/sdd: user_max 3907029168 sectors
/dev/sdd: native_max 3907029168 sectors
/dev/sdd: dco 3907029168 sectors
/dev/sde: LBA, HPA, LBA48, DCO support
/dev/sde: size 3907029168 sectors
/dev/sde: user_max 3907029168 sectors
/dev/sde: native_max 3907029168 sectors
/dev/sde: dco 3907029168 sectors
/dev/sdf: LBA, HPA, LBA48, DCO support
/dev/sdf: size 3907029168 sectors
/dev/sdf: user_max 3907029168 sectors
/dev/sdf: native_max 3907029168 sectors
/dev/sdf: dco 3907029168 sectors
/dev/sdg: LBA, HPA, LBA48, DCO support
/dev/sdg: size 3907029168 sectors
/dev/sdg: user_max 3907029168 sectors
/dev/sdg: native_max 3907029168 sectors
/dev/sdg: dco 3907029168 sectors
/dev/sdh: LBA, HPA, LBA48, DCO support
/dev/sdh: size 3907029168 sectors
/dev/sdh: user_max 3907029168 sectors
/dev/sdh: native_max 3907029168 sectors
/dev/sdh: dco 3907029168 sectors
/dev/sdi: LBA, HPA, LBA48, DCO support
/dev/sdi: size 3907029168 sectors
/dev/sdi: user_max 3907029168 sectors
/dev/sdi: native_max 3907029168 sectors
/dev/sdi: dco 3907029168 sectors
/dev/sdj: LBA, HPA, LBA48, DCO support
/dev/sdj: size 3907029168 sectors
/dev/sdj: user_max 3907029168 sectors
/dev/sdj: native_max 3907029168 sectors
/dev/sdj: dco 3907029168 sectors
/dev/sdk: LBA, HPA, LBA48, DCO support
/dev/sdk: size 3907029168 sectors
/dev/sdk: user_max 3907029168 sectors
/dev/sdk: native_max 3907029168 sectors
/dev/sdk: dco 3907029168 sectors
/dev/sdl: LBA, HPA, LBA48, DCO support
/dev/sdl: size 3907029168 sectors
/dev/sdl: user_max 3907029168 sectors
/dev/sdl: native_max 3907029168 sectors
/dev/sdl: dco 3907029168 sectors
/dev/sdm: LBA, HPA, LBA48, DCO support
/dev/sdm: size 3907029168 sectors
/dev/sdm: user_max 3907029168 sectors
/dev/sdm: native_max 3907029168 sectors
/dev/sdm: dco 3907029168 sectors
/dev/sdn: LBA, HPA, LBA48, DCO support
/dev/sdn: size 3907029168 sectors
/dev/sdn: user_max 3907029168 sectors
/dev/sdn: native_max 3907029168 sectors
/dev/sdn: dco 3907029168 sectors
/dev/sdo: LBA, HPA, LBA48, DCO support
/dev/sdo: size 3907029168 sectors
/dev/sdo: user_max 3907029168 sectors
/dev/sdo: native_max 3907029168 sectors
/dev/sdo: dco 3907029168 sectors
/dev/sdp: LBA, HPA, LBA48 support
/dev/sdp: size 3907029168 sectors
/dev/sdp: user_max 3907029168 sectors
/dev/sdp: native_max 3907029168 sectors
/dev/sdq: LBA, HPA, LBA48, DCO support
/dev/sdq: size 3907029168 sectors
/dev/sdq: user_max 3907029168 sectors
/dev/sdq: native_max 3907029168 sectors
/dev/sdq: dco 3907029168 sectors
/dev/sdr: LBA, HPA, LBA48, DCO support
/dev/sdr: size 3907029168 sectors
/dev/sdr: user_max 3907029168 sectors
/dev/sdr: native_max 3907029168 sectors
/dev/sdr: dco 3907029168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - CHS 1 1 1, sector size=512
Hard disk list
Disk /dev/sda - 60 GB / 55 GiB - CHS 7296 255 63, sector size=512 - TOSHIBA MK6037GSX, S/N:674MT0A4T, FW:DL330G
Disk /dev/sdb - 60 GB / 55 GiB - CHS 7296 255 63, sector size=512 - TOSHIBA MK6037GSX, S/N:674MT0A5T, FW:DL330G
Disk /dev/sdc - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00R6B0, S/N:WD-WCAVY1357327, FW:01.00A01
Disk /dev/sdd - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00R6B0, S/N:WD-WCAVY1333756, FW:01.00A01
Disk /dev/sde - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EARX-00PASB0, S/N:WD-WMAZA6953333, FW:51.0AB51
Disk /dev/sdf - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-22R6B0, S/N:WD-WCAVY5208359, FW:01.00A01
Disk /dev/sdg - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-22R6B0, S/N:WD-WCAVY5187468, FW:01.00A01
Disk /dev/sdh - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00R6B0, S/N:WD-WCAVY5447218, FW:01.00A01
Disk /dev/sdi - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00S2B0, S/N:WD-WCAVY5376419, FW:01.00A01
Disk /dev/sdj - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00S2B0, S/N:WD-WCAVY4671438, FW:01.00A01
Disk /dev/sdk - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EARX-00PASB0, S/N:WD-WMAZA6949978, FW:51.0AB51
Disk /dev/sdl - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00R6B0, S/N:WD-WCAVY1067600, FW:01.00A01
Disk /dev/sdm - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EARX-00PASB0, S/N:WD-WMAZA6948967, FW:51.0AB51
Disk /dev/sdn - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00R6B0, S/N:WD-WCAVY1358850, FW:01.00A01
Disk /dev/sdo - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00S2B0, S/N:WD-WCAVY1316914, FW:01.00A01
Disk /dev/sdp - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EADS-00W4B0, S/N:WD-WCAVY4624704, FW:01.00A01
Disk /dev/sdq - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EARX-00PASB0, S/N:WD-WMAZA6836631, FW:51.0AB51
Disk /dev/sdr - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EARX-00PASB0, S/N:WD-WCAZAD171957, FW:51.0AB51
Disk /dev/md1 - 41 MB / 39 MiB - CHS 10016 2 4, sector size=512
Disk /dev/md2 - 12 GB / 11 GiB - CHS 2931840 2 4, sector size=512
Disk /dev/md3 - 47 GB / 44 GiB - CHS 11709360 2 4, sector size=512
Disk /dev/md4 - 14 TB / 12 TiB - CHS 3418645888 2 4, sector size=512
Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4, sector size=512

Partition table type (auto): None
Disk /dev/md5 - 14 TB / 12 TiB
Partition table type: None
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : Yes

Analyse Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=3/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
Current partition structure:
P ext4 0 0 1 3418643199 1 4 27349145600

search_part()
Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=3/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Recover, 14 TB / 12 TiB

Results
P ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Recover, 14 TB / 12 TiB

interface_write()
P ext4 0 0 1 3418643199 1 4 27349145600

Write isn't available because the partition table type "None" has been selected.

search_part()
Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=3/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Recover, 14 TB / 12 TiB

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=10/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418645888
recover_EXT2: part_size 1579363328
ext4 28743 1 2 3418674631 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB
This partition ends after the disk limits. (start=229949, size=1579363328, end=1579593276, disk end=1579341824)

block_group_nr 1

recover_EXT2: part_offset problem

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 3

recover_EXT2: part_offset problem

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 5

recover_EXT2: part_offset problem

block_group_nr 5

recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 7

recover_EXT2: part_offset problem

block_group_nr 7

recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 9

recover_EXT2: part_offset problem

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 25

recover_EXT2: part_offset problem

block_group_nr 25

recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=25/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 27

recover_EXT2: part_offset problem

block_group_nr 27

recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=27/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=10/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418645888
recover_EXT2: part_size 1579363328
ext4 1602567 1 2 3420248455 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB
This partition ends after the disk limits. (start=12820541, size=1579363328, end=1592183868, disk end=1579341824)

block_group_nr 49

recover_EXT2: part_offset problem

block_group_nr 49

recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=49/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=10/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418645888
recover_EXT2: part_size 1579363328
ext4 2651143 1 2 3421297031 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB
This partition ends after the disk limits. (start=21209149, size=1579363328, end=1600572476, disk end=1579341824)

block_group_nr 81

recover_EXT2: part_offset problem

block_group_nr 81

recover_EXT2: "e2fsck -b 2654208 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=81/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 125

recover_EXT2: part_offset problem

block_group_nr 125

recover_EXT2: "e2fsck -b 4096000 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=125/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 243

recover_EXT2: part_offset problem

block_group_nr 243

recover_EXT2: "e2fsck -b 7962624 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=243/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB

block_group_nr 343

recover_EXT2: part_offset problem

block_group_nr 343

recover_EXT2: "e2fsck -b 11239424 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=343/104328, s_mnt_count=0/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Backup superblock, 14 TB / 12 TiB
Search for partition aborted
Disk /dev/md5 - 14 TB / 12 TiB - CHS 3418643200 2 4
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (14 TB / 12 TiB) seems too small! (< 14 TB / 12 TiB)
The following partitions can't be recovered:
ext4 28743 1 2 3418674631 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB
ext4 1602567 1 2 3420248455 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB
ext4 2651143 1 2 3421297031 1 1 27349167104
EXT4 Large file Sparse superblock Recover, 14 TB / 12 TiB

Results
P ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Recover, 14 TB / 12 TiB

interface_write()
P ext4 0 0 1 3418643199 1 4 27349145600

Write isn't available because the partition table type "None" has been selected.

Interface Advanced

recover_EXT2: s_block_group_nr=0/104328, s_mnt_count=3/21, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3418643200
recover_EXT2: part_size 1579341824
P ext4 0 0 1 3418643199 1 4 27349145600
EXT4 Sparse superblock Recover, 14 TB / 12 TiB

TestDisk exited normally.

Sponsored links

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

Re: Unable to force disk geometry past 8TB for recovery

#2 Post by Fiona » 20 Jun 2012, 09:11

Would it be possible to use the version 6.14 to have another try?

Fiona

murkyl
Posts: 6
Joined: 19 Jun 2012, 17:00

Re: Unable to force disk geometry past 8TB for recovery

#3 Post by murkyl » 20 Jun 2012, 17:49

So a little more progress. The latest test version of the program does allow me to change the cylinders to be > 8 TiB. I ran a deeper scan again and it came back with the same partitions as before. When I try to list files in it I get:

TestDisk 6.14-WIP, Data Recovery Utility, May 2012
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
P ext4 28743 1 2 3418674631 1 1 27349167104
Directory /

No file found, filesystem may be damaged.


I've selected NONE for the partition type so I can't write the old partition table to the disk. This is a PC running Linux. I formatted originally with the EXT4 file system. Should I choose a different partition type, try to reload the partition table and do a file system repair of some sort?

murkyl
Posts: 6
Joined: 19 Jun 2012, 17:00

Re: Unable to force disk geometry past 8TB for recovery

#4 Post by murkyl » 20 Jun 2012, 17:52

Some more information. I think I may have created the RAID array right on top of the underlying partitioned drives. So I don't think there is a "partition" per se on my /dev/md5 device. :( Have I totally messed myself up?

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

Re: Unable to force disk geometry past 8TB for recovery

#5 Post by Fiona » 20 Jun 2012, 18:30

I think I may have created the RAID array right on top of the underlying partitioned drives. So I don't think there is a "partition" per se on my /dev/md5 device. :( Have I totally messed myself up?
Hopefully that you created your RAID exactly like before.
Your disks must be in sequential order and you stripe size must fit also.
8 TB must be a GPT disk.
It's a lot better not to write anything to your disk.
If TestDisk doesn't find a partition (to write it to tha GUID partition table) then it might be possible to create an empty partition exactly like before (infos will follow).
Don't format your partition or disk, you'd override your previous file system.
On this partition you could have a superblock diagnose.
Some infos about;
http://www.cgsecurity.org/wiki/Advanced ... SuperBlock
Ext4 has the same procedure like ext2/3 (asked our Linux tech savvy).

Fiona

murkyl
Posts: 6
Joined: 19 Jun 2012, 17:00

Re: Unable to force disk geometry past 8TB for recovery

#6 Post by murkyl » 20 Jun 2012, 20:49

I'm sure I recreated the RAID correctly. I had tried using the foremost tool and I was able to at least recover some files, however with the foremost tool most of the files are corrupt, it only recovers certain files that it knows the signature for and there are no file names.

What I'm afraid of is that when I tried to repair the file system on my own, I ran mkfs.ext4 -S on top of the array because it was complaining about the size of the old file system being incorrect.

I followed the link you provided about restoring a superblock. How can I restore a super block from the old filesystem? I created a new ext4 on top of the old array, hoping that would allow me to undelete files, but that wasn't the case.

My ideal case I guess would be somehow restore the old file system super blocks but I don't know how to do that.

murkyl
Posts: 6
Joined: 19 Jun 2012, 17:00

Re: Unable to force disk geometry past 8TB for recovery

#7 Post by murkyl » 26 Jun 2012, 01:10

Any suggestions on how to restore a super block from partition that is found via a deep scan? Restoring the super blocks from the current partition won't help.

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

Re: Unable to force disk geometry past 8TB for recovery

#8 Post by Fiona » 26 Jun 2012, 15:46

If you'd like to diagnose a superblock from a partition found during Deeper Search, you have to write it first to your GUID partition table in TestDisk using the menu Write.
Then your partition would be available to use the menu Advanced to have a boot sector diagnose.
If you have the values from a screen, you can stop Quick Search and press a to add this partition.
GPT is always primary.

Fiona

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 2 guests