Timeline for How to fix GUID hard drive corrupted to MBR
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2017 at 16:38 | history | protected | CommunityBot | ||
| Sep 27, 2016 at 12:03 | history | edited | klanomath | CC BY-SA 3.0 |
edited title
|
| Aug 29, 2015 at 14:21 | history | tweeted | twitter.com/#!/askdifferent/status/637631091885654016 | ||
| Aug 29, 2015 at 6:22 | vote | accept | junkelly | ||
| Aug 29, 2015 at 1:56 | history | edited | junkelly | CC BY-SA 3.0 |
cleaned up images and supplied requested information
|
| Aug 27, 2015 at 3:27 | history | edited | junkelly | CC BY-SA 3.0 |
deleted 1 character in body
|
| Aug 27, 2015 at 3:17 | history | edited | junkelly | CC BY-SA 3.0 |
added requested information
|
| Aug 27, 2015 at 3:10 | history | edited | junkelly | CC BY-SA 3.0 |
added requested information
|
| Aug 26, 2015 at 14:48 | answer | added | klanomath | timeline score: 10 | |
| Aug 26, 2015 at 6:08 | comment | added | David Anderson |
If you want, you could try dumping the header in hexadecimal format. The command is sudo dd if=/dev/disk1 count=1 skip=8 | xxd. You could post the output. The description of what you should see is given here. Most people can not interpret hex output so I would not expect you to. Anyway, it is what I would have done next. If also would not hurt to add the output from sudo fdisk /dev/disk1.
|
|
| Aug 26, 2015 at 5:25 | history | edited | junkelly | CC BY-SA 3.0 |
added gpt recover information
|
| Aug 26, 2015 at 4:17 | comment | added | David Anderson |
You can google this: The MBR table has a 2.2 TB limit on the disk size it can handle. This works on the assumption the sector (block) size is 512 bytes. You have a Advance Format drive. This probably means your sector (block) size may be 4096 bytes. Actually your posted output from distutil shows this. This would allow the MBR table to handle larger disks, but any third party tool you use to examine the disk may not be able to handle Advance Format disks. Many tools are hard coded for 512 byte sector (block) sizes. They can incorrectly read such disks.
|
|
| Aug 26, 2015 at 3:30 | comment | added | junkelly | How do I do so? I have mainly been using Disk Utility and started exploring gpt fdisk. I also have Data Rescue 3 which hasn't been helpful. | |
| Aug 26, 2015 at 2:59 | comment | added | David Anderson | The first thing I would do would be to see if the Backup of the GPT table exists at the end of the disk. | |
| Aug 26, 2015 at 2:25 | review | First posts | |||
| Aug 26, 2015 at 7:27 | |||||
| Aug 26, 2015 at 2:21 | history | asked | junkelly | CC BY-SA 3.0 |