Today, as I intended to perform my regular Time Machine backup, I got welcomed by a very scary message when I connected my external hard disk to my MacBook.
The disk you inserted you inserted was not readable by this computer.
Now, I take pride in having never ever lost any data on my Macs since 1998, so I was concerned this might be the end of my record…
In Disk Utility the drive device was listed, but no volume could be mounted due to a corrupted partition map. Don’t ask me how it got corrupted in the first place. I would guess the disk did not like being unplugged without using the eject command…
Anyway, salvation can come at no cost by using the Terminal in Mac OS X (assuming you have administrative rights):
- Connect your external disk
- Start terminal and use the 3 commands in bold red below (make sure to change the disk number to match your setup based on the first command)
- If the last command was successful, disconnect and reconnect your disk, which should now be OK
IronMan:~ nbalkota$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS IronMan 249.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *1.0 TB disk1 1: 0xEE 1.0 TB disk1s1 IronMan:~ nbalkota$ sudo gpt recover /dev/disk1 WARNING: Improper use of the sudo command could lead to data loss or the deletion of important system files. Please double-check your typing when using sudo. Type "man sudo" for more information. To proceed, enter your password, or type Ctrl-C to abort. Password: gpt recover: /dev/disk1: recovered primary GPT table from secondary gpt recover: /dev/disk1: recovered primary GPT header from secondary IronMan:~ nbalkota$ diskutil eject /dev/disk1 Disk /dev/disk1 ejected
An alternative to the second command (gpt) would be diskutil repairDisk /dev/disk1
Note than the manpage for gpt does not cover the recover option whereas the manpage for diskutil does cover the repairDisk option.
Cloudy Aide-Mémoire 
Dec 19, 2016 @ 10:52:33
Hello all. I see this thread has been going on for some years and it’s saved a lot of people. I’m hoping you can help me as yesterday I was happily working on an edit and today when I turned the computer on I got the dreaded window that everyone in this thread knows. So I followed the instructions and I got this as a final message…
diskutil repairDisk
Usage: diskutil repairDisk MountPoint|DiskIdentifier|DeviceNode
Repair the required layout and components of the partition map of a whole disk.
Ownership of the affected disk is required.
Any help would be hugely appreciated!
Thanks
Dec 19, 2016 @ 13:03:43
Hi, you got the “usage” message so the command you entered was incomplete. Did you list the partitions first to know which device path your disk is at?
Dec 27, 2016 @ 03:07:26
Just wanted to give a shoutout to the author for providing a great fix here. I had spent hours trying to recover an encrypted USB drive normally used on a mac which was rendered unusable when a windows machine accidentally rewrote its partition table.
After many hours of research and trial and error, running diskutil eject /dev/disk1 followed by diskutil repairDisk /dev/disk1 repaired the partition table and brought the USB drive back to life immediately.
Thanks again!
Dec 29, 2016 @ 22:12:16
Thank you! I was really stuck. This process didn’t completely solve my problem until after I ran repairDisk again afterwards! Thanks again!
Dec 29, 2016 @ 23:13:46
I got an “Input/output error” on both commands.
Jan 27, 2017 @ 23:28:41
Thank you! Saved a disk with client data on it!!!! You rock!
Jan 28, 2017 @ 16:38:03
Saved another one! Most concise solution I found. Thanks!
Feb 13, 2017 @ 16:46:49
Had the same problem and worked through your steps…
Steps went fine till eject…after that however trying the last step which was the repairdisk, it display
“Repairing the partition map might erase disk2s1, proceed? (y/N)”
Since there is data on the drive i couldnt afford to hit the N. What do you advise me to do?
Pls. help…. this forum has been a life savior so far and i have reached the best stage possible so far so i guess just another step or two should complete the process…
Thanks in advance 🙂
Feb 15, 2017 @ 15:46:42
Guys, I was having that MBR problem.
I tried everything, including diskwarrior, terminal, disk utility and tons of other things. The only thing that solved my problem was: instaling active file recovery on my windows and recovering all the files from my HD to the PC.
It took hours and hours to get it complete, but for those that are desperate like I was, it works.
Feb 16, 2017 @ 06:31:21
Hello all
As previously mentioned in my comment, since there is data on the drive, in the below step in terminal;
“diskutil repairDisk /dev/disk2
Repairing the partition map might erase disk2s1, proceed? (y/N)”
will my data be erased?? What do you advise me to do?
Thanks for your help in advance…
Feb 16, 2017 @ 08:11:28
Shaheen, your data could be erased. There is always a risk of data deletion, but you would not be in this situation if you had a backup of your data…
Why are you trying the alternative command?
Did the gpt recover fail before?
Anyway, if you take no risk you would still not get any data back…
Before you proceed, could you confirm what type of disk needs fixing?
USB pen drive? External hard disk?
Do you know how it was formatted?
Feb 16, 2017 @ 14:43:56
Hi just to show the current situation, this is the display on terminal after typing “diskutil list”:
Shaheens-MacBook-Pro:~ Shaheen$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 447.7 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Apple_HFS Paradise 51.6 GB disk0s4
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Macintosh HD +447.3 GB disk1
Logical Volume on disk0s2
0472579A-5338-4355-BB82-15299C7A9307
Unlocked Encrypted
/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme +19.8 MB disk2
1: Apple_partition_map 32.3 KB disk2s1
2: Apple_HFS Flash Player 19.7 MB disk2s2
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk4
1: EFI 209.7 MB disk4s1
2: Apple_CoreStorage naShaSeries2 2.0 TB disk4s2
3: Apple_Boot Boot OS X 134.2 MB disk4s3
Shaheens-MacBook-Pro:~ Shaheen$ diskutil repairDisk /dev/disk4
Repairing the partition map might erase disk4s1, proceed? (y/N)
the hard disk is a 2TB WB External Hard drive, formatted using mac ox extended journal
Pls. advise..
Feb 16, 2017 @ 16:56:34
I would advise to run gpt recover first and run diskutil repairDisk only if gpt recover fails.
Feb 17, 2017 @ 05:45:08
Hi
Tried the original steps and the hard disk didn’t pick up
Then tried repairDisk; however the result that displayed was as below:
Last login: Fri Feb 17 09:41:23 on ttys000
Shaheens-MacBook-Pro:~ Shaheen$ diskutil repairDisk /dev/disk2
Repairing the partition map might erase disk2s1, proceed? (y/N) y
Started partition map repair on disk2
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk2s3
Repairing file system
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Boot OS X appears to be OK
File system check exit code is 0
Updating boot support partitions for the volume as required
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk2s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
disk2s2: Scan for Metadata Volume
Logical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44144: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44143: cksum mismatch
No valid commit checkpoint found
Storage system check exit code is 1
Repairing storage system
Checking volume
disk2s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
disk2s2: Scan for Metadata Volume
Logical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44144: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44143: cksum mismatch
No valid commit checkpoint found
The volume 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 was found corrupt and can not be repaired
Storage system check exit code is 1
Repairing storage system
The volume disk2s2+disk0s2 cannot be repaired when it is in use
Checking volume
disk2s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
disk0s2: Scan for Disk Labels
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
Incomplete or inconsistent CoreStorage Physical Volume set
Storage system check exit code is 1
Problems were encountered during repair of the partition map
Error: -69716: Storage system verify or repair failed
Underlying error: 1: Operation not permitted
What would you advise to do forward?
Feb 17, 2017 @ 08:07:12
Could you paste the output from command “sudo gpt recover /dev/diskN” where N must be the correct number for your disk. The sudo prefix is critical: you can only run these commands as administrator.
Feb 17, 2017 @ 16:26:26
After i type the sudo command, it asks for password and then back to entry point as shown below:
Shaheens-MacBook-Pro:~ Shaheen$ sudo gpt recover /dev/disk2
Password:
Shaheens-MacBook-Pro:~ Shaheen$
Feb 17, 2017 @ 16:34:29
OK so you hard drive is fixed then.
I am struggling to understand what problem you actually have.
Is your drive visible in Finder?
Is your drive visible in Disk Utility?
If you run command
ls -l /Volumes
What do you get?
Feb 17, 2017 @ 17:07:45
Hi
The problem i am facing is as below, based on your quieries:
1. the hard drive is not visible in Finder
2. Under the disk utility,
On the left side, under External it displays WD Elements 25A2 Media
Nothing below which i believe means that the hard drive is not mounted…
On the right side, it shows as if the disk is unformatted
3. On running the command “ls -l /Volumes” the following is displayed:
Shaheens-MacBook-Pro:~ Shaheen$ ls -l /Volumes
total 8
lrwxr-xr-x 1 root wheel 1 Feb 17 09:18 Macintosh HD -> /
d———+ 13 Shaheen admin 510 Feb 15 18:55 Paradise
Shaheens-MacBook-Pro:~ Shaheen$
Feb 17, 2017 @ 17:20:24
OK thanks
So your issue is not the same as covered by this post. Your partition table is printed OK from the diskutil list command.
Could you confirm if your external drive Volume is called Paradise?
If it is, then it seems its POSIX permissions are corrupted and preventing you to access/read it…
I suggest you try this command to fix it:
sudo diskutil repairDisk /dev/diskN
where N is the relevant number from diskutil list command.
Good luck.
Feb 18, 2017 @ 11:39:36
Hi,
In light of your above reference, the name of the external disk is “naShaSeries2”
This following is the output on each command:
Shaheens-MacBook-Pro:~ Shaheen$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 447.7 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Apple_HFS Paradise 51.6 GB disk0s4
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Macintosh HD +447.3 GB disk1
Logical Volume on disk0s2
0472579A-5338-4355-BB82-15299C7A9307
Unlocked Encrypted
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_CoreStorage naShaSeries2 2.0 TB disk4s2
3: Apple_Boot Boot OS X 134.2 MB disk4s3
Shaheens-MacBook-Pro:~ Shaheen$ sudo diskutil repairDisk /dev/disk4
Password:
Repairing the partition map might erase disk4s1, proceed? (y/N) y
Started partition map repair on disk4
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk4s3
Repairing file system
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Boot OS X appears to be OK
File system check exit code is 0
Updating boot support partitions for the volume as required
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk4s2: Scan for Volume Headers
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
disk4s2: Scan for Metadata Volume
Logical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44144: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44143: cksum mismatch
No valid commit checkpoint found
The volume 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 was found corrupt and needs to be repaired
Storage system check exit code is 1
Repairing storage system
Checking volume
disk4s2: Scan for Volume Headers
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
disk4s2: Scan for Metadata Volume
Logical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44144: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 44143: cksum mismatch
No valid commit checkpoint found
The volume 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 was found corrupt and can not be repaired
Storage system check exit code is 1
Repairing storage system
The volume disk4s2+disk0s2 cannot be repaired when it is in use
Checking volume
disk4s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
disk0s2: Scan for Disk Labels
Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 on 1 device
Incomplete or inconsistent CoreStorage Physical Volume set
Storage system check exit code is 1
Problems were encountered during repair of the partition map
Error: -69716: Storage system verify or repair failed
Underlying error: 1: Operation not permitted
The hard disk still does not come into view in Finder
Feb 18, 2017 @ 16:35:54
OK
The good: your partion map appears valid, so your partitions are visible and your volume seems to be a bootable system.
The bad: your file system is somehow corrupted, so you cannot access your data.
I think this is a problem that a software like Disk Warrior could fix.
Like I said, your issue is different to the one covered in this post.
Good luck
Feb 18, 2017 @ 19:57:13
Hi, i tried DiskWarrior and when i chose the drive it shows “This is an offline, unavailable Core Storage disk.” Any suggestions?
Feb 18, 2017 @ 20:24:47
Not familiar with Core Storage logical volume, but will try to help anyway…
What is the output from this command?
diskutil cs list
Feb 18, 2017 @ 20:47:10
The below is the output:
Shaheens-MacBook-Pro:~ Shaheen$ diskutil cs list
CoreStorage logical volume groups (2 found)
|
+– Logical Volume Group 10B18774-8AD4-4D9A-972A-96E0EF5FAA48
| =========================================================
| Name: Macintosh HD
| Status: Online
| Size: 447653191680 B (447.7 GB)
| Free Space: 10723328 B (10.7 MB)
| |
| +- Logical Volume Family 0493B51D-C2B1-4720-B524-76DBB8A1BB6A
| ———————————————————-
| Encryption Type: AES-XTS
| Encryption Status: Unlocked
| Conversion Status: Complete
| High Level Queries: Fully Secure
| | Passphrase Required
| | Accepts New Users
| | Has Visible Users
| | Has Volume Key
| |
| +-> Logical Volume 0472579A-5338-4355-BB82-15299C7A9307
| —————————————————
| Disk: disk1
| Status: Online
| Size (Total): 447290146816 B (447.3 GB)
| Revertible: Yes (unlock and decryption required)
| Revert Status: Reboot required
| LV Name: Macintosh HD
| Volume Name: Macintosh HD
| Content Hint: Apple_HFS
|
+– Logical Volume Group 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6
=========================================================
Name: naShaSeries2
Status: Offline
Size: 0 B (0 B)
Free Space: -none-
|
+-< Physical Volume ABD79F60-70D9-4AB0-94CD-E2448C15EE2C
—————————————————-
Index: 0
Disk: disk2s2
Status: Checking
Size: 2000021315584 B (2.0 TB)
Feb 19, 2017 @ 00:22:02
What version of Mac OS are installed on Macintosh HD and naShaSeries2?
Did you enable FileVault encryption on both?
Feb 19, 2017 @ 05:53:10
Hi i use the macOS Sierra. naShaSeries2 is the external hard drive. If i remember right, i haven’t enabled FileVault encryption. I had enabled password for the external hard drive when i formatted the drive as mac os extended journal.
Feb 19, 2017 @ 08:22:38
OK thanks.
Do you use FileVault on your internal drive, Macintosh HD?
What does your external drive contain?
Was your external drive bootable of used for TimeMachine?
Did you use Disk Utility on macOS Sierra to format your external drive?
Feb 19, 2017 @ 08:38:18
Hi,
I have not used filevault on the internal drive.
The external drive contains scans of my important office and payment documentations and photo backups. It was not used for time machine.
Also, i had used disk utility on macOS Sierra to format the external drive.
Feb 19, 2017 @ 08:54:07
Thanks for the information. Your internal partition of 450 GB is encrypted on Macintosh HD. Hence I assumed Filevault because it was a CoreStorage logical volume.
Did you format your internal drive with password as well.
By the way, formatting with password implies encryption.
Feb 19, 2017 @ 13:05:53
If i remember right, the laptop came with the operating system, and i had just setup a password for logging in. Cant figure a way to go on 😦
Feb 19, 2017 @ 13:11:47
Did you update your laptop to Sierra from Yosemite, El Capitan or an earlier version of Mac OS?
We just need to find a safe way to bring your external CoreStorage volume back online.
Feb 19, 2017 @ 14:54:27
The external hard drive was just formatted just recently maybe 3 weeks earlier, at the time the os was macOS Sierra. The OS was originally the version before the Yosemite
Feb 20, 2017 @ 10:42:26
At the time of formatting the external hard drive, the os was macOS Sierra. The macOS on the system when purchased was originally the Maverick oS.
Feb 20, 2017 @ 10:43:36
From the original purchase of the oS, i have updated it to the latest version.
Feb 20, 2017 @ 16:37:39
I just read some articles and believe this is something pretty disturbing…
let me brief u on the original situation when this issue came about…
The macOS extended journaled encrypted hard drive was taken by a colleague and connected to a security camera device to copy some .dav files which i believe would have been a device more windows based….the disk initially didn’t show but the next time he connected, he was able to export the files onto the drive. He mentioned that he had not pressed format or anything similar?
When the hard disk was connected to the mac system after this, it didn’t appear…it had asked to initialize which i pressed! Now after reading the articles i get a feeling that the data has been erased?? Is this the case?
Feb 21, 2017 @ 00:57:58
This is very confusing. I am not aware of any Windows software capable of writing to a CoreStorage HFS+ partition. Particularly if you formatted it with a password: encrypted.
If you pressed initialize then your data would have been erased.
Based on your diskutil cs list output your CS LV is gone. I wonder what would happen if you tried to create a new one…
Command:
diskutil cs createVolume 9C3CA1F3-4691-4F7D-AC02-35FBCF180BC6 jhfs+ testLV 100%
Otherwise you will need specialist data recovery software and lots of patience to get your data back.
Mar 01, 2017 @ 21:33:02
Can u help me with my 64GB SD Card:
Marcos-MBP:~ marcomarques$ sudo gpt recover /dev/disk2
Password:
gpt recover: /dev/disk2: no primary or secondary GPT headers, can’t recover
Marcos-MBP:~ marcomarques$ diskutil repairDisk /dev/disk2
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition map,
you can hereby try to repair it enough to be recognized as a map; another
“diskutil repairDisk /dev/disk2” might then be necessary for further repairs
Proceed? (y/N) y
Error repairing map: MediaKit reports bad partition or no map found (-5324)
Mar 01, 2017 @ 22:56:50
A SD card is most likely to be formatted as FAT32. This post is specific to the GPT format only.
Mar 28, 2017 @ 13:02:16
I have an external WD drive and I’m getting below error when i do the “sudo gpt recover”
gpt recover: /dev/disk2: no primary or secondary GPT headers, can’t recover
what do i do next?…
please help..
Mar 28, 2017 @ 21:19:28
Regina,
Are you sure /dev/disk2 is correct?
Are you sure your external WD drive was formatted for Mac using a GUID Partition Table?
Mar 29, 2017 @ 12:16:26
this is what i get with diskutil list:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Reg 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Reg +498.9 GB disk1
Logical Volume on disk0s2
949D8C27-D90C-4731-B6FE-59031267F405
Unlocked Encrypted
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: *1.0 TB disk2
i’m not sure though if my WD was formatted using GUID partition table… what can i do at this stage?
Mar 29, 2017 @ 23:00:28
Afraid you will have to rely on a data recovery software since the get command did not work with your /dev/disk2
Mar 30, 2017 @ 12:24:23
I’ve tried Disk Warrior but it’s unable to access the drive too…
Apr 28, 2017 @ 19:43:19
Hi I’m some trouble accessing my both of my drives and keep seeing the disk you have inserted is not readable by this computer as well. they seemed to have both become corrupted at the same time and I would like some help in fixing it.
Last login: Fri Apr 28 15:27:45 on ttys000
Silkes-MacBook-Pro:~ Silke$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 499.4 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD +499.1 GB disk1
Logical Volume on disk0s2
2F982C51-CC8E-4BB3-86E0-1FC632E3680D
Unencrypted
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk2
1: Windows_NTFS 1.0 TB disk2s1
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.1 GB disk3
1: DOS_FAT_32 8.1 GB disk3s1
Silkes-MacBook-Pro:~ Silke$ sudo gpt recover /dev/disk2
Password:
gpt recover: /dev/disk2: error: device contains a MBR
Silkes-MacBook-Pro:~ Silke$ diskutil eject /dev/disk2
Disk /dev/disk2 ejected
Silkes-MacBook-Pro:~ Silke$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 499.4 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD +499.1 GB disk1
Logical Volume on disk0s2
2F982C51-CC8E-4BB3-86E0-1FC632E3680D
Unencrypted
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk2
1: Windows_NTFS 1.0 TB disk2s1
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.1 GB disk3
1: DOS_FAT_32 8.1 GB disk3s1
Silkes-MacBook-Pro:~ Silke$ diskutil repairDisk /dev/disk2
Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
Silkes-MacBook-Pro:~ Silke$
Apr 28, 2017 @ 20:42:39
Hi Silke, unfortunately your external disks were Windows NTFS and DOS/FAT32 formatted. This post is only applicable to Mac GPT formatted disks. Have you tried connecting your disks on a Windows PC?
Apr 30, 2017 @ 03:13:48
No I have not. I initially was reading the devices on my mac so I was unaware. Can you instruct me on what I should be doing on the pc to fix it?
Apr 30, 2017 @ 09:23:28
I was just asking if you ever tried to connect your devices on a PC. I don’t know what you should be doing, sorry.
May 25, 2017 @ 15:41:06
The alternative method worked like a charm for me. On the drive was the only backup of my latest film project files so you’ve literally saved my life!!! I will never be able to thank you enough!!
May 25, 2017 @ 21:41:04
You are welcome! Very happy for you.
May 31, 2017 @ 21:40:14
Thank you! This worked for me, only solution I found. Was also my time machine drive.
Jun 10, 2017 @ 13:34:12
I need help. My drive suddenly stopped working and is experiencing the same issues described here. It was plugged into a ‘Voyager Q’ bay. It happened to two drives in a row plugged into the that bay. I’m on a Mac and I don’t understand the terminal commands! Can you help me via Skype? I’d gladly pay you.
Jun 12, 2017 @ 06:49:41
Have a go at the Terminal. The commands can do no harm.
Jun 11, 2017 @ 12:15:33
I tried running the recovery command and this is what I got after putting in my password: gpt recover: unable to open device ‘/dev/disk2s2’: Resource busy
‘Resource busy” is what I get when I try to verify disk in disk utility as well. First aid fails and the disk remains unmounted. Any suggestions?
Jun 11, 2017 @ 12:17:01
also if I try the alternate command I get this: Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
Jun 12, 2017 @ 06:50:24
Do you know how your disk was formatted?
Jun 14, 2017 @ 06:14:06
Also you need to run the recovery command on the whole disk (/dev/disk2) not just a partition (/dev/disk2s2).
Jun 12, 2017 @ 06:36:42
Hope you can help!
Ran the commands and this is what I got….
iMac:~ salgray$ sudo gpt recover /dev/disk7
Password:
jgpt recover: /dev/disk7: error: device contains a MBR
iMac:~ salgray$ sudo gpt recover /dev/disk7
gpt recover: /dev/disk7: error: device contains a MBR
iMac:~ salgray$ diskutil repairDisk /dev/disk7
Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
iMac:~ salgray$
Being relatively non-technical this is a little scary!
Suggestions from here?
Many thanks
Jun 12, 2017 @ 06:48:04
If you see MBR then your disk was PC formatted, not Mac. Hence, this post cannot help you, sorry.
Jun 13, 2017 @ 23:33:01
Mmm… I have been using this disk as backup on my iMac for photos for around 6 months with no issues. Accessing it daily from Lightroom. – been working fine. I have tried plugging into a PC since the error message with no luck. So rather confused that suggesting it is Windows formatted now? Can you suggest a thread that might work to solve issues on the drive? Many thanks
Jun 14, 2017 @ 06:08:45
Please show the output from the list command to see the partition scheme for your disks and their size.
Not sure if lightroom would mandate the disk to be Mac formatted even on a Mac. If your disk was use for Time Machine then definitely it would have been Mac formatted.
Jun 14, 2017 @ 06:24:08
I was able to access the files from Finder on Mac (as well as Lightroom) – so this would lead me to think it was formatted for Mac? I will try the recovery command for the whole disk now
Jun 14, 2017 @ 06:36:40
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 999.3 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *2.0 TB disk1
1: Apple_HFS 1.9 TB disk1s1
2: DOS_FAT_32 100.0 GB disk1s2
Also tried recover on whole disk. same error messages
Jun 14, 2017 @ 06:47:28
Your disk is seen with a MBR (fdisk) partition scheme. It is odd to see 2 partitions: one 1.9 TB Mac and one 0.1 TB PC.
Do you recall finder showing 2 partitions when you connected your disk before?
Jun 14, 2017 @ 07:00:40
No – had not noticed 2 partitions
Jun 14, 2017 @ 06:50:53
If you find technical help, then this thread could help:
http://www.insanelymac.com/forum/topic/231025-i-lost-my-guid-paritition-label-to-fdisk/
This requires physical access to your Mac in order to boot on a Linux live rescue CD.
Jun 13, 2017 @ 18:59:09
Last login: Tue Jun 13 19:49:53 on ttys000
Anishas-MacBook-Pro:~ A$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Macintosh HD 250.1 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD +249.8 GB disk1
Logical Volume on disk0s2
F6E53514-E00E-445A-BF2E-60918D0A6351
Unencrypted
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk3
1: 0xEE 1.0 TB disk3s1
Anishas-MacBook-Pro:~ A$ sudo gpt recover /dev/disk3
Password:
gpt recover: /dev/disk3: no primary or secondary GPT headers, can’t recover
Anishas-MacBook-Pro:~ A$
This is what i get when I type into terminal. Any help is appreciated!
I have a WD external hard drive
Jun 13, 2017 @ 21:08:21
Your WD disk is seen with a FDisk partition scheme whereas this post is about GPT only.
See if the solution from this thread can help you.
Feb 12, 2018 @ 16:56:19
WOW! THANK YOU!
As usual, Apple forums were useless for this.
I was planning a hardware refresh for a customer, and when connecting her drive using target disk mode, i got the “drive is unreadable” message.
It just showed as an unformatted drive using diskutil list, and on DiskDrill saw that the partitions were intact, but it being encrypted, i could not access the data. DiskWarrior was useless, it greyed out all options when selecting this drive.
This post saved me a LOT of headaches today!
THANKS AGAIN!!
Mar 10, 2018 @ 18:58:46
So i’ve been trying to figure this out for a bit now and its still causing me issues. I’ve been using an external Seagate HD and now its stopped mounting. Tried to run all the fixes and haven’t seem to have any luck. Also trying to understand why in my diskutil list its represented twice. both disk2 and disk3 are the same drive.
jlysxn-3:~ JaysenChase$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 250.1 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS JSNWLF *249.8 GB disk1
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_CoreStorage 2.0 TB disk2s2
3: Apple_Boot Boot OS X 134.2 MB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFSX DRIVE *2.0 TB disk3
would really appreciate any feedback or help on this
Mar 10, 2018 @ 21:37:27
After googling HFSX appears to be the case-sensitive version of HFS. Your disk 3 is the logical volume corresponding to your CoreStorage partition on disk2.
What is your issue exactly?
Apr 23, 2018 @ 21:41:11
I am seeking some help.
I did something stupid…lol
I removed a disk from my iMac, put it in a case and use it on my powerbook as a USB drive, and worked.
Then I renamed that USB disk with another name (name was Macintosh HD) and now it doesn’t work (info still on disk)
Is there a way to name an Apple_HFS? I think that would solve the issue but disk (disk4s2) cannot be mounted.
Thanks!
Apr 23, 2018 @ 22:57:18
Renaming a disk is possible and should no cause any issues. What do you mean by it doesn’t work? Cannot boot on USB disk or Finder no longer shows disk content?
Apr 23, 2018 @ 23:03:36
My powerbook works ok. It is just that I added a Usb disk that used to be another’s iMac disk. I didn´t format it or anything. Just plugged it and worked until I renamed that usb name from Macintosh HD (because it belong to another iMac and it was strange having 2 disks with the same name) to another thing.
Using Disk utility it shows the disk as if it was formatted and is grayed out (can not rename it) and when using Diskutil list it will show that the disk has no Apple_HFS name… that’s why I think that if I name it, it may work. (wishful thinking?) Thanks for your time
Apr 25, 2018 @ 09:52:22
Afraid this is a different issue to the one covered by this post. Could you share the output from diskutil list command for your USB drive?
Apr 26, 2018 @ 06:14:53
Thank you! I worked on it and the disk was damaged. That’s why I couldn’t work on it. Have a great week and thx!
Apr 26, 2018 @ 06:33:19
Sorry about and for not being able to help you better.
Apr 26, 2018 @ 15:17:42
Maybe on my next disk issue? 🙂 thx!
Jun 11, 2018 @ 10:55:39
I need advice, please help this happens everytime. disconnected my external harddrive without ejecting it by accident
Repairing the partition map might erase disk2s1, proceed? (y/N) y
Started partition map repair on disk2
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Problems were encountered during repair of the partition map
Error: -69697: Partition map repair failed while adjusting structures to fit current whole disk size
Underlying error: 5: Input/output error
Jul 12, 2018 @ 04:14:56
i had a working mountain lion but after i boot i got a kernel panic saying can’t load kernel kexts etc.. and after that the drive converted itself from a GUID_partition_scheme to : /dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk0
1: 0xEE 1.0 TB disk0s1
how can i fix this ? can i restore it ? i want my data ! i have a backup for the system only but i have a second partition that i did not make a backup for ! i hope someone can help me !! and i need to mention that i use a hackintosh !!
Jul 12, 2018 @ 05:17:19
Have you tried these commands as per the post?
sudo gpt recover /dev/disk0
or
diskutil repairDisk /dev/disk0
Having a hackintosh should make no difference in this instance: this is not a hardware related issue.
Sep 30, 2018 @ 04:24:30
I need help. My usb when plugged in goes into this when I check the diskutil list
Idk what to do it seems like there is no partition scheme what so ever
/dev/disk1 (external, physical) :
#: TYPE NAME SIZE IDENTIFIER
0: 8.1 GB. disk1
That’s it can anyone tell me what’s wrong with my USB.
Sep 30, 2018 @ 06:45:53
A USB key drive is unlikely to have been formatted as GPT, most likely MBR. Unfortunately, I have no easy fix for MBR, but there should be data recovery software that could help.
As of now, your USB would need formatting to be visible in Finder, but this will lead to data loss.
Nov 20, 2018 @ 18:44:05
Hi There, i have an issue with a corrupted external hard drive and followed your directions above to repair or recover but keep on getting an input/output error message
Nov 21, 2018 @ 09:53:14
I/O error could be due to many things (hardware failure?). This post only covers a fix for a very specific issue.
Dec 06, 2019 @ 15:32:21
> diskutil verifyVolume disk2
Started file system verification on disk2 Ricardo Webbens
Verifying storage system
Checking volume
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group C68590D6-5073-4FF9-9F62-B7176767E98E spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 80 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify EA11F5D6-2D54-454A-910C-FF5090D8F179
Load and verify 68E19A29-BA6F-4A70-A184-12697981CCC2
Load and verify Freespace Summary
Unable to bootstrap transaction group 1911585: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify EA11F5D6-2D54-454A-910C-FF5090D8F179
Load and verify 68E19A29-BA6F-4A70-A184-12697981CCC2
Load and verify Freespace Summary
Unable to bootstrap transaction group 1911584: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 7 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify EA11F5D6-2D54-454A-910C-FF5090D8F179
Load and verify 68E19A29-BA6F-4A70-A184-12697981CCC2
Load and verify Freespace Summary
Unable to bootstrap transaction group 1911575: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 5 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify EA11F5D6-2D54-454A-910C-FF5090D8F179
Load and verify 68E19A29-BA6F-4A70-A184-12697981CCC2
Load and verify Freespace Summary
Unable to bootstrap transaction group 1911569: invalid field value
No valid commit checkpoint found
The volume C68590D6-5073-4FF9-9F62-B7176767E98E was found corrupt and needs to be repaired
Storage system check exit code is 1
Error: -69716: Storage system verify or repair failed
Underlying error: 1: Operation not permitted
“”
I have a Fusiondrive and this is my results , i cant repair disk2 , i have tried all the methods described above and i still got the same erros.
“”
dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage fusion 351.0 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Apple_HFS Sistema 647.7 GB disk0s4
5: Apple_Boot Recovery HD 650.0 MB disk0s5
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage fusion 239.7 GB disk1s2
3: Apple_Boot Boot OS X 134.2 MB disk1s3
/dev/disk2 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Ricardo Webbens +584.2 GB disk2
Logical Volume on disk0s2, disk1s2
68E19A29-BA6F-4A70-A184-12697981CCC2
Unencrypted Fusion Drive
“”
This is my diskutil list and the problem is on disk2
Any help would be much appreciated .
Thanks
Dec 07, 2019 @ 12:03:40
Hi Ricardo, the methods in my post are intended to repair the GUID table. In your case, I guess the issue is different and more filesystem related.
Since you got an “Operation not permitted” maybe you need to repeat the diskutil command but with “sudo” since repairing a volume requires admin privileges.
Good luck.
Dec 25, 2019 @ 16:39:55
@nbalkota Hats off to you dude, i see you have helped tons of people above.
Dec 25, 2019 @ 16:43:26
My problem is similar, or may be slightly different.
My mistake: I ejected my 2 TB external Transcend hard drive right when it was working.
The next time i plugged in the hard drive, it was ‘UNINITIALIZED’.
I have tried A LOT of stuff up and down but no clue!
HELP!! 😦
Dec 25, 2019 @ 17:13:34
Here’s what happens when i have followed your given procedure:
Mys-MacBook-Pro:~ AliEhtisham$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 250.8 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme – +250.8 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 231.7 GB disk1s1
2: APFS Volume Preboot 21.2 MB disk1s2
3: APFS Volume Recovery 519.0 MB disk1s3
4: APFS Volume VM 2.1 GB disk1s4
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: *0 B disk2
Mys-MacBook-Pro:~ AliEhtisham$ sudo gpt recover /dev/disk2
gpt recover: unable to open device ‘/dev/disk2’: Operation not supported by device
Mys-MacBook-Pro:~ AliEhtisham$ diskutil repairdisk /dev/disk2
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition map,
you can hereby try to repair it enough to be recognized as a map; another
“diskutil repairDisk /dev/disk2” might then be necessary for further repairs
Proceed? (y/N) y
Error repairing map: Invalid argument (22)
Dec 25, 2019 @ 20:09:54
Is your Transcend 2TB external disk a HDD or an SSD? Which connection does it use: USB, FireWire or Thunderbolt?
Dec 25, 2019 @ 20:16:14
One more thing…. Do you remember how your Transcend drive was formatted? APFS, HFS+, NTFS?
Dec 27, 2019 @ 10:18:56
It’s an HDD which has a USB connection.
It was formatted MacOS Journaled.
May 11, 2021 @ 15:53:05
hello, I’m having trouble with an external drive. This is the log:
8
/dev/disk5 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *1.0 TB disk5
1: Apple_partition_map 32.3 KB disk5s1
2: Apple_HFS Seagate 1.0 TB disk5s3
On sudo gpt -r show /dev/disk5
and also on, sudo gpt recover /dev/disk5
I get this error:
gpt recover: unable to open device ‘/dev/disk5’: Resource busy
With diskutil repairDisk /dev/disk5
I get this:
Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
finally on diskutil unmountDisk /dev/disk5
I get this:
Unmount of disk5 failed: at least one volume could not be unmounted
Unmount was dissented by PID 0 (kernel_task)
Do you have an idea what this could be? I need to save data from this drive. Thanks!
May 13, 2021 @ 22:30:09
Is your external drive connected via USB, FireWire or Thunderbold?
It does not seem to have a GPT, so it is old and formatted in HFS (as opposed to HFS+)?
Jun 14, 2021 @ 14:20:15
Hi there,
I’m also facing the problem that my external SSD won’t get mounted in Finder but is showing up in Disk Utility, greyed out tho. Hitting the “activate” button won’t do a thing. I’ve been coping a larger amount of data from one external SSD to another one. Suddenly the transfer stopped and an error message appeared. From this moment on I never saw my SSD mounting in Finder anymore.
This is what I get in terminal (Its about the external disk “BackupSD”):
MacBook-Pro-4:~ matt2$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 500.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme – +500.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 410.3 GB disk1s1
2: APFS Volume Preboot 45.4 MB disk1s2
3: APFS Volume Recovery 510.7 MB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *1.0 TB disk2
1: Apple_HFS BackupSD 1.0 TB disk2s1
_________________________________________________
MacBook-Pro-4:~ matt2$ sudo gpt recover /dev/disk2
Password:
gpt recover: /dev/disk2: error: device contains a MBR
_________________________________________________
MacBook-Pro-4:~ matt2$ diskutil repairDisk /dev/disk2
Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
–> So I know this post is not about MBR but do you still know what could help?
Tomorrow I will try to connect it to a windows pc but its still weird that it just noch shows up since the drive is actually not damage, right?
Thanks for any help in advanced!
Best Matt
Nov 15, 2021 @ 07:03:34
Feb 12, 2022 @ 11:40:08
Hey Guys,
I’ve got Catalina 10.15.7 running on my 2013 iMac fusion drive. Unfortunately the fusion drive got corrupted (crashed) and I had to reinstall the OS. When I tried to access my Time Machine backup, I got a problem and that drive was unreadable (similar to the OP). I have since cloned the drive and am trying to restore the cloned drive. I ran through all the steps and got the volume repaired, but it’s not mounting at all.
I think there still is data corruption on disk3s2 as that should be the Time Machine volume. The original HD was 2TB and the cloned HD is 5 TB so I don’t think the new HD is showing the actual data. Please see below and let me know if there is any other troubleshooting which may help recover the lost Time Machine data
barrett@barretts-imac ~ % diskutil repairDisk /dev/disk3
Repairing the partition map might erase disk3s1, proceed? (y/N) y
Started partition map repair on disk3
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Repairing the EFI system partition’s file system
Repairing file system
Volume is already unmounted
Performing fsck_msdos -y /dev/rdisk3s1
** /dev/rdisk3s1
Invalid BS_jmpBoot in boot block: 000000
File system check exit code is 8
Restoring the original state found as unmounted
Creating a new EFI system partition
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
The partition map has been repaired
Finished partition map repair on disk3
barrett@barretts-imac ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 121.1 GB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 1000.0 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme – +1.1 TB disk2
Physical Stores disk0s2, disk1s2
1: APFS Volume 2013 iMac – Data 241.8 GB disk2s1
2: APFS Volume Preboot 38.7 MB disk2s2
3: APFS Volume Recovery 525.9 MB disk2s3
4: APFS Volume VM 2.1 GB disk2s4
5: APFS Volume 2013 iMac 11.2 GB disk2s5
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *5.0 TB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_APFS 5.0 TB disk3s2
Feb 13, 2022 @ 20:25:06
I wonder if you should have formatted your clone in HFS+. I think Catalina does not support APFS formatted Time Machine disks, only HFS+. APFS Time Machine support started from Big Sur.
Feb 16, 2022 @ 07:35:37
Hmm. Ok, what do you recommend? The issue is that the original Time Machine HD is showing FDisk_partition_scheme. This is why, after cloning to a new HD, I converted using the repair/restore commands. It’s weird that I’m running Catalina on my iMac and the Terminal would convert to APFS if it’s not supported by the OS.
Mar 11, 2022 @ 13:42:12
Do you suggest I re-clone from the original corrupted time machine back into the FDisk_partition_scheme then try to convert to HFS+? How might I go about that?