I did try the gpt command which found no primary or secondary headers: sudo gpt recover /dev/disk1
#WXHEXEDITOR READ ONLY CANNOT SAVE HOW TO#
I googled how to check the last sector for GUID partition table and didn't find much help. I am hoping that just by changing the directory from MBR back to the original GUID the original partitioning and files and directories will be restored. Of course my ultimate question: Is there a way to reformat my drive to the original GUID format with 1.5TB partitions without losing all the data? Gdisk terminal text: GPT fdisk (gdisk) version 1.0.0 I did some reading and downloaded gdisk but haven't made any changes with it yet.
Read-Only Volume: Not applicable (no file system)
#WXHEXEDITOR READ ONLY CANNOT SAVE FREE#
Volume Free Space: Not applicable (no file system) Volume Name: Not applicable (no file system)Ĭontent (IOContent): FDisk_partition_scheme I think that somehow the directory format was corrupted and changed from 'GUID_partition_scheme' to 'Fdisk_partition_scheme' rendering the drive unreadable. I'm sure that I formatted the drive to 'GUID_partition_scheme' and the fact that I used it without problems on my Mac for a long time should confirm that. I have never used bootcamp or parallels or similar programs. I think this is the problem as I have never used windows and would not have formatted the hard drive to this format. I used disk utility from the terminal and see that the entire drive is listed as 'Fdisk_partition_scheme'. That didn't help.ĭisk Utility can see the disk but not partitions and the options to verify the disk are grayed out. I used it fine for months and then one day it didn't work.īefore I did any diagnostics on it I tried it in a different enclosure. The other was all of my shared media like video and music. The backup was done by Carbon Copy Cloner and was tested and verified a few times to make sure it worked. One was a bootable backup of a 1TB drive. I formatted it with two partitions, both 1.5TB. It is a Western Digital 3TB Red WD30EFRX. I have a 3TB hard drive that has an unusual problem. I am on OS X 10.9.5 with a late 2013 iMac.
0 kommentar(er)
