Hi,
I have a big problem, something happend with my HP DL380 G7 serwer, two disk from six stop working, after reebot server looks fine but, vmware can't see 8,12TB disk, problem is:
"Error: Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted's rescue feature to recover partitions."
I use test disk to recover - log:
TestDisk 7.0-WIP, Data Recovery Utility, October 2014
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 4.7, Cygwin 1007.25
Compilation date: 2014-11-13T18:59:50
ext2fs lib: 1.42.8, 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)=9001677840384
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=4009754624
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=9001677840384
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=4009754624
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=489127936
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\X:)=3162112
Hard disk list
Disk /dev/sda - 9001 GB / 8383 GiB - CHS 1094391 255 63, sector size=512 - HP LOGICAL VOLUME, S/N:PACCRID11330K2F, FW:5.12
Disk /dev/sdb - 4009 MB / 3824 MiB - CHS 487 255 63, sector size=512 - USB DISK 2.0, FW:PMAP
Drive D: - 489 MB / 466 MiB - CHS 116 64 32, sector size=2048 - hp DVD RW AD-7586H, FW:KH04
Drive X: - 3162 KB / 3088 KiB - CHS 193 16 2, sector size=512 - Microsoft Corporation RamDisk
Partition table type (auto): Intel
Disk /dev/sda - 9001 GB / 8383 GiB - HP LOGICAL VOLUME
Partition table type: Intel
Analyse Disk /dev/sda - 9001 GB / 8383 GiB - CHS 1094391 255 63
Geometry from i386 MBR: head=256 sector=63
BAD_RS LBA=1 16450622
check_part_i386 1 type EE: no test
Current partition structure:
1 P EFI GPT 0 0 2 267349 89 4 4294967295
Warning: Bad starting head (CHS and LBA don't match)
No partition is bootable
search_part()
Disk /dev/sda - 9001 GB / 8383 GiB - CHS 1094391 255 63
VMFS 0 32 33 1094363 158 3 17580949504
VMFS 5, 9001 GB / 8383 GiB
file_pread(4,2,buffer,401532928(1094391/169/51)) lseek err Invalid argument
file_pread(4,1,buffer,401532928(1094391/169/51)) lseek err Invalid argument
file_pread(4,1,buffer,401532927(1094391/169/50)) lseek err Invalid argument
file_pread(4,14,buffer,401532929(1094391/169/52)) lseek err Invalid argument
file_pread(4,3,buffer,401532943(1094391/170/3)) lseek err Invalid argument
file_pread(4,3,buffer,401532990(1094391/170/50)) lseek err Invalid argument
file_pread(4,8,buffer,401533006(1094391/171/3)) lseek err Invalid argument
file_pread(4,11,buffer,401533053(1094391/171/50)) lseek err Invalid argument
file_pread(4,2,buffer,401534975(1094391/202/19)) lseek err Invalid argument
Results
* VMFS 0 32 33 1094363 158 3 17580949504
VMFS 5, 9001 GB / 8383 GiB
interface_write()
1 * VMFS 0 32 33 1094363 158 3 17580949504
search_part()
Disk /dev/sda - 9001 GB / 8383 GiB - CHS 1094391 255 63
VMFS 0 32 33 1094363 158 3 17580949504
VMFS 5, 9001 GB / 8383 GiB
NTFS at 401024/6/6
filesystem size 4294703104
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 133691 30 36 401024 6 6 4294703104
NTFS found using backup sector, blocksize=4096, 2198 GB / 2047 GiB
recover_EXT2: s_block_group_nr=0/111662, s_mnt_count=14/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3658969088
recover_EXT2: part_size 3501948928
Linux 546582 50 29 2368664 135 47 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
This partition ends after the disk limits. (start=8780843008, size=29271752704, end=38052595711, disk end=17581402032)
recover_EXT2: s_block_group_nr=0/111662, s_mnt_count=14/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3658969088
recover_EXT2: part_size 3501948928
Linux 546585 98 10 2368667 183 28 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
This partition ends after the disk limits. (start=8780894208, size=29271752704, end=38052646911, disk end=17581402032)
recover_EXT2: s_block_group_nr=0/111662, s_mnt_count=14/30, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 3658969088
recover_EXT2: part_size 3501948928
Linux 546587 205 51 2368670 36 6 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
This partition ends after the disk limits. (start=8780933120, size=29271752704, end=38052685823, disk end=17581402032)
file_pread(4,2,buffer,401532928(1094391/169/51)) lseek err Invalid argument
file_pread(4,1,buffer,401532928(1094391/169/51)) lseek err Invalid argument
file_pread(4,1,buffer,401532927(1094391/169/50)) lseek err Invalid argument
file_pread(4,14,buffer,401532929(1094391/169/52)) lseek err Invalid argument
file_pread(4,3,buffer,401532943(1094391/170/3)) lseek err Invalid argument
file_pread(4,3,buffer,401532990(1094391/170/50)) lseek err Invalid argument
file_pread(4,8,buffer,401533006(1094391/171/3)) lseek err Invalid argument
file_pread(4,11,buffer,401533053(1094391/171/50)) lseek err Invalid argument
file_pread(4,2,buffer,401534975(1094391/202/19)) lseek err Invalid argument
Disk /dev/sda - 9001 GB / 8383 GiB - CHS 1094391 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (9001 GB / 8383 GiB) seems too small! (< 19 TB / 17 TiB)
The following partitions can't be recovered:
Linux 546582 50 29 2368664 135 47 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
Linux 546585 98 10 2368667 183 28 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
Linux 546587 205 51 2368670 36 6 29271752704
ext4 blocksize=4096 Large file Sparse superblock Recover, 14 TB / 13 TiB
Results
VMFS 0 32 33 1094363 158 3 17580949504
VMFS 5, 9001 GB / 8383 GiB
HPFS - NTFS 133691 30 36 401024 6 6 4294703104
NTFS found using backup sector, blocksize=4096, 2198 GB / 2047 GiB
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition
I's possible to fix this disk?
After Raid error GPT tables missing
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
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
- cgrenier
- Site Admin
- Posts: 5439
- Joined: 18 Feb 2012, 15:08
- Location: Le Perreux Sur Marne, France
- Contact:
Re: After Raid error GPT tables missing
Run TestDisk, select your disk and force EFI GPT table partition instead of PC Intel.
Re: After Raid error GPT tables missing
What I do:
First I analise dysk (select intel partition), Quick search not working so I do deep search after 10 hours test disk say about small disk, next I again do deep search (now is in progress it should be done in one hour). deep search done: Again qucik search:
First I analise dysk (select intel partition), Quick search not working so I do deep search after 10 hours test disk say about small disk, next I again do deep search (now is in progress it should be done in one hour). deep search done: Again qucik search:
Re: After Raid error GPT tables missing
I can't post more images so reply the post.
I'm start what You say but I'm not quit from testdisk just back to disk select (Q button), next select EFI GPT, analyse and quick search, but it working very slowly, about 2 unit/second, in my case it's take 151 hours (1094391/2/3600sec), do I somenthing wrong or this is ok? It's possible to do something else like extend the cylinder?
I'm start what You say but I'm not quit from testdisk just back to disk select (Q button), next select EFI GPT, analyse and quick search, but it working very slowly, about 2 unit/second, in my case it's take 151 hours (1094391/2/3600sec), do I somenthing wrong or this is ok? It's possible to do something else like extend the cylinder?