I’m currently over two days into a scan and have a question. I’ve got a HFS formatted 2TB RAID 0 drive that isn’t mounting. I’ve run testdisk and so far I'm getting a lot of input/output errors during 'Quick Search'. Do I need to continue to do this to restore the partition? Do I have the partition information needed to fix it already? I'm attaching the first part of the log since it's already such a big file! Any help, advice would be greatly appreciated!!!
Thanks!
--cy
Fri Oct 18 18:57:25 2013
Command line: TestDisk
TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Darwin, kernel 10.8.0 (Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.1
Compiler: GCC 4.0
Compilation date: 2013-07-30T14:08:37
ext2fs lib: 1.41.8, ntfs lib: libntfs-3g, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504
Hard disk list
Disk /dev/disk0 - 2000 GB / 1863 GiB - 3907029168 sectors (RO), sector size=512
Disk /dev/disk1 - 1000 GB / 931 GiB - 1953525168 sectors (RO), sector size=512
Disk /dev/disk2 - 1000 GB / 931 GiB - 1953525168 sectors (RO), sector size=512
Disk /dev/disk3 - 640 GB / 596 GiB - 1250263728 sectors (RO), sector size=512
Disk /dev/disk4 - 2000 GB / 1863 GiB - 3907050332 sectors, sector size=512
Disk /dev/rdisk0 - 2000 GB / 1863 GiB - 3907029168 sectors (RO), sector size=512
Disk /dev/rdisk1 - 1000 GB / 931 GiB - 1953525168 sectors (RO), sector size=512
Disk /dev/rdisk2 - 1000 GB / 931 GiB - 1953525168 sectors (RO), sector size=512
Disk /dev/rdisk3 - 640 GB / 596 GiB - 1250263728 sectors (RO), sector size=512
Disk /dev/rdisk4 - 2000 GB / 1863 GiB - 3907050332 sectors, sector size=512
Partition table type (auto): Mac
Disk /dev/rdisk4 - 2000 GB / 1863 GiB
Partition table type: Mac
Analyse Disk /dev/rdisk4 - 2000 GB / 1863 GiB - 3907050332 sectors
HFS+ magic value at 512/0/1
Current partition structure:
1 P partition_map 1 511 511
2 P HFS 512 3907039743 3907039232
3 P Free 3907039744 3907040129 386
search_part()
Disk /dev/rdisk4 - 2000 GB / 1863 GiB - 3907050332 sectors
file_pread(13,16,buffer,510(510/0/1)) read err: Input/output error
file_pread(13,16,buffer,513(513/0/1)) read err: Input/output error
file_pread(13,1,buffer,513(513/0/1)) read err: Input/output error
file_pread(13,16,buffer,518(518/0/1)) read err: Input/output error
file_pread(13,1,buffer,519(519/0/1)) read err: Input/output error
file_pread(13,16,buffer,511(511/0/1)) read err: Input/output error
file_pread(13,1,buffer,513(513/0/1)) read err: Input/output error
file_pread(13,16,buffer,519(519/0/1)) read err: Input/output error
file_pread(13,1,buffer,519(519/0/1)) read err: Input/output error
file_pread(13,16,buffer,512(512/0/1)) read err: Input/output error
file_pread(13,1,buffer,513(513/0/1)) read err: Input/output error
file_pread(13,16,buffer,514(514/0/1)) read err: Input/output error
file_pread(13,1,buffer,515(515/0/1)) read err: Input/output error
file_pread(13,4,buffer,516(516/0/1)) read err: Input/output error
file_pread(13,16,buffer,5176(5176/0/1)) read err: Input/output error
file_pread(13,16,buffer,5184(5184/0/1)) read err: Input/output error
file_pread(13,1,buffer,5185(5185/0/1)) read err: Input/output error
file_pread(13,2,buffer,5192(5192/0/1)) read err: Input/output error
file_pread(13,16,buffer,5200(5200/0/1)) read err: Input/output error
file_pread(13,1,buffer,5201(5201/0/1)) read err: Input/output error
file_pread(13,2,buffer,5208(5208/0/1)) read err: Input/output error
file_pread(13,16,buffer,5216(5216/0/1)) read err: Input/output error
file_pread(13,1,buffer,5217(5217/0/1)) read err: Input/output error
file_pread(13,16,buffer,5224(5224/0/1)) read err: Input/output error
file_pread(13,1,buffer,5225(5225/0/1)) read err: Input/output error
file_pread(13,16,buffer,5232(5232/0/1)) read err: Input/output error
file_pread(13,1,buffer,5233(5233/0/1)) read err: Input/output error
file_pread(13,16,buffer,5240(5240/0/1)) read err: Input/output error
file_pread(13,1,buffer,5241(5241/0/1)) read err: Input/output error
file_pread(13,16,buffer,5248(5248/0/1)) read err: Input/output error
This is only a very small sample of the input/output errors that I have logged.
Question about recovery
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
Re: Question about recovery
Hi, I'm new to the forum but I would suggest to not do anything apart from the quick search because:
- you haven't deleted or repartitioned the drive so there is nothing to be found with the deep scan which cannot be found with quick one;
- one or both disks on the raid have bad sectors I assume. If the sectors are occurring because of drives head scratching the disk, the further scans will add new scratches;
- unless you had backed up the drive geometry with some tool there is no way to restore the partition information and recover any data.
I advise you to accept the loss and format each of the raid disks separately and see which of them has bad sectors and use the good one for other purposes.
- you haven't deleted or repartitioned the drive so there is nothing to be found with the deep scan which cannot be found with quick one;
- one or both disks on the raid have bad sectors I assume. If the sectors are occurring because of drives head scratching the disk, the further scans will add new scratches;
- unless you had backed up the drive geometry with some tool there is no way to restore the partition information and recover any data.
I advise you to accept the loss and format each of the raid disks separately and see which of them has bad sectors and use the good one for other purposes.