I had some files on an old thumb-drive, and recently I was going through and discovered that all/most of the files were no longer readable by any of my macs. I seam to remember having similar problems like this while back, and finding an apparent link to my choice of format, so I ran diskutil list in terminal: /dev/disk3 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *134.2 GB disk3 1: EFI EFI 209.7 MB disk3s1 2: Apple_HFS my-old-files 133.9 GB disk3s2 And I tried ls -l total 3858320 -rw-r--r--@ 1 kipbits staff 3430100 Nov 21 2016 2015-12-24.pdf drwxr-xr-x 8 kipbits staff 272 Sep 26 2016 2016-sep-14-files -rw-r--r-- 1 kipbits staff 25642888 May 18 2015 myold.mp4 -rw-r--r--@ 1 kipbits staff 884 Jul 31 20:20 someold.txt -rw-r--r--@ 1 kipbits staff 1320157184 Sep 21 2016 someold.iso drwxr-xr-x 4 kipbits staff 136 Sep 27 16:23 anotherdir -rw-r--r--@ 1 kipbits staff 626214959 Nov 5 2016 someold.mp4 drwxr-xr-x 14 kipbits staff 476 Nov 2 2016 sept2016files I think this looks normal? The problem is, I'm not able to open any of my files. I get the following errors: pdf: **The file “some-old.pdf” could not be opened.** It may be damaged or use a file format that Preview doesn’t recognize. txt: 800 byte files are blank rtf: **The document “some-old.rtf” could not be opened.** mp4: **QuickTime Player can't open "some-old.mp4".** To see if additional software is available that will enable QuickTime Player to open the movie, click Tell Me More. dmg, iso: will mount but did not test further pkg: **The operation couldn’t be completed. (com.apple.installer.pagecontroller error -1.)** Couldn't open "some-old.pkg" I found a thread on apple saying "*The partition map type doesn't really make any difference for non bootable volumes*", although i don't get any of these problems when using Master Boot Record & ExFAT. None of the files are more than a couple years old, so i don't think there should be any compatibility issues, and none of the files were corrupted when I copied them to the drive. I have had this same problem with other drives, and they were perfectly usable after reformatting, although this involved erasing files. My question is: **Is there a way to recover my files?** The file-sizes still display that the files are there. Is there a way to save these files and make them readable? ...Also, if it makes any difference, I am using El Capitan(for dev purposes) > **Update------------------------------------------------------------------------------------------------(04/Oct/2017)** I did a hexdump for some of the files in question. my output was something like this: 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000370 00 00 00 00 0000374 what does this mean? do you think a recovery app could even help me here? here are some threads that are perhaps related: ...Also could this possibly be related to SIP? I first noticed this problem around when i first upgraded to El Capitan. Or perhaps there is something else going on? I have recently been experimenting with windows and various forms of linux, and have been moving files around with thumb drives. Perhaps I plugged one in to the wrong computer and corrupted all the files? Whatever the cause, I'm wondering if the files might still be recoverable? Is hexdump a good way to diagnose recoverability? **Would buying a recover app just be a waste of $100?**

After recently having some issues with an 8TB Seagate drive, I bought a new replacement to backup, and realised I have this dock sitting here with dual bays that can clone a disk far faster than any software copy I can do with my meagre USB 3 connections. So I've tried this clone function only a couple of times and realised when I try and mount one of the cloned volumes it couldn't show both to compare files, so on research I realise the byte for byte copy cloned the unique code for the volume and the system can't handle having two of the same connected. So after searching for some time and not getting any clear answers I've come here for some expert advice. It took at least 12 hours to copy the drive, I really don't want to start again using Carbon Copy Cloner or SuperDuper as I suspect it will take 3 days through software. Is there any way of changing the unique code, is it safe to do so?

Running a Mac Pro 2013 with macOS Catalina. Looking to change the GUID type from FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF to 7C3457EF-0000-11AA-AA11-00306543ECAC. I've been browsing through various previous posts about this issue but have not found the solution that I need yet or anyone having the same problem. After running the diskutil umountDisk disk0 and gpt remove -i 2 disk0 commands, I went to add the disk back using this command gpt add -i 2 -b 409640 -s 768896136 -t 53746F72-6167-11AA-AA11-00306543ECAC disk0 and got this error message gpt add: unable to open device 'disk0': Resource busy. I've noticed as well that after running gpt -r show disk0, index 2 has switched from FFF... to MBR part 218 and disk0s2 is no longer listed when calling diskutil list. I can't seem to figure out where to go from here. Here is what I have done so far

-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF               393.7 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                56.1 GB    disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                         *1.3 GB    disk1
   1:        Apple_partition_map                         30.7 KB    disk1s1
   2:                  Apple_HFS OS X Base System        1.3 GB     disk1s2
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk3
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk4
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk5
/dev/disk6
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk6
/dev/disk7
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *6.3   MB  disk7
/dev/disk8
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *2.1   MB  disk8
/dev/disk9
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *1.0   MB  disk9
/dev/disk10
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk10
/dev/disk11
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk11
/dev/disk12
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *1.0   MB  disk12
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  768896136      2  GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
  769305776   98292560         
  867598336  109506560      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  977104896        131         
  977105027         32         Sec GPT table
  977105029          1         Sec GPT header
-bash-3.2# diskutil unmountDisk disk0
Unmount of all volumes on disk0 was successful
-bash-3.2# gpt remove -i 2 disk0
gpt remove: disk0: Suspicious MBR at sector 0
disk0s2 removed
-bash-3.2# gpt add -i 2 -b 409640 -s 768896136 -t 7C3457EF-0000-11AA-AA11-00306543ECAC  disk0
gpt add: unable to open device disk0: Resource busy
-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data BOOTCAMP                56.1 GB    disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                         *1.3 GB    disk1
   1:        Apple_partition_map                         30.7 KB    disk1s1
   2:                  Apple_HFS OS X Base System        1.3 GB     disk1s2
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk3
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk4
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk5
/dev/disk6
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk6
/dev/disk7
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *6.3   MB  disk7
/dev/disk8
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *2.1   MB  disk8
/dev/disk9
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *1.0   MB  disk9
/dev/disk10
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk10
/dev/disk11
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *524.3 KB  disk11
/dev/disk12
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled                *1.0   MB  disk12
-bash-3.2# gpt -r show disk0
gpt show: disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  768896136      2  MBR part 218
  769305776   98292560         
  867598336  109506560      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  977104896        131         
  977105027         32         Sec GPT table
  977105029          1         Sec GPT header

Not sure where to go from this point and appreciate any help with getting this solved

I want to "raw copy" with dd the critical GPT (~ Guid Partition Scheme) bytes of my computer's main hard drive, to an arbitrary file. I tried to do the equivalent MBR/Unix/Linux in my Mac (with sudo of course), but didn't work: "Operation not permitted". > ("In UNIX and GNU/Linux you can use dd command to backup your MBR > from a console": > > dd if=/dev/xxx of=mbr.backup bs=512 count=1 ) My try on my Mac (even with sudo): % sudo dd if=/dev/disk0 of=mbr.backup bs=512 count=1 Password: dd: /dev/disk0: Operation not permitted % sudo dd if=/dev/disk1 of=mbr.backup bs=512 count=1 dd: /dev/disk1: Operation not permitted My system devs (diskutil list): /dev/disk0 (internal, physical): #: 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⁩ 24.4 GB disk1s1 2: APFS Snapshot ⁨com.apple.os.update-...⁩ 24.4 GB disk1s1s1 3: APFS Volume ⁨Macintosh HD - Data⁩ 374.7 GB disk1s2 4: APFS Volume ⁨Preboot⁩ 2.7 GB disk1s3 5: APFS Volume ⁨Recovery⁩ 1.1 GB disk1s4 6: APFS Volume ⁨VM⁩ 24.6 KB disk1s5

In an attempt to recover a different external drive altogether, my drive "Libraries" was compromised. Just for it being connected at the same time. I'll be sure to disconnect drives I'm not working on in the future. Since the incident, I didn't touch this drive at all except for looking to see what's recoverable. I haven't done anything else except a few terminal commands below to hopefully get help. I'm hoping this is simple and I can just rebuild the GPT and the drive will magically appear again. Does anyone know what to do? I'm clueless, scared and a complete noob.

shogunhz@CyXs-MacBook-Pro ~ % diskutil verifyDisk disk4                        
Unable to verify this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
shogunhz@CyXs-MacBook-Pro ~ % diskutil list disk2
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *5.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                 Apple_APFS Container disk4         5.0 TB     disk2s2
shogunhz@CyXs-MacBook-Pro ~ % diskutil list disk4      
/dev/disk4 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +5.0 TB     disk4
                                 Physical Store disk2s2
   1:                APFS Volume Libraries               2.3 TB     disk4s1
shogunhz@CyXs-MacBook-Pro ~ % sudo gpt -r show disk4
Password:
       start        size  index  contents
           0  1220883190         
shogunhz@CyXs-MacBook-Pro ~ % diskutil verifyDisk disk4
Unable to verify this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
shogunhz@CyXs-MacBook-Pro ~ % sudo dd if=/dev/disk2 count=1 bs=512 | hexdump -Cv 
Password:
1+0 records in
1+0 records out
512 bytes transferred in 0.020153 secs (25406 bytes/sec)
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000100  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000150  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000160  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000170  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000190  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 fe  |................|
000001c0  ff ff ee fe ff ff 01 00  00 00 fe ff ff ff 00 00  |................|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200
shogunhz@CyXs-MacBook-Pro ~ % sudo gpt -r show /dev/disk4
       start        size  index  contents
           0  1220883190

I have a Macbook Pro with retina, Yosemite and 500GB hard drive. I tried to install Windows using Bootcamp and accidentally deleted a partition, now my Mac cannot boot anymore. This is the output from sudo gpt -r show disk0 gpt show: disk0: Suspicious MBR at sector 0 start size index contents 0 1 MBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6 40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640 776617328 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 777026968 1269760 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC 778296728 616 778297344 198807552 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC 977104896 131 977105027 32 Sec GPT table 977105059 1 Sec GPT header I only need to make the second partition at index 2 and type FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF to be bootable again. This partition has FileVault 2 enabled. But right now, I have no clue on what to do. P/S: I Followed the instruction from @klanomath Boot from a external hard drive with full Yosemite system but at the last command to change the partition type sudo gpt add -b 409640 -s 776617328 -i 2 -t 53746F72-6167-11AA-AA11-00306543ECAC /dev/disk0 It got this error: gpt add: /dev/disk0: Suspicious MBR at sector 0 gpt add: /dev/disk0: error: no space available on device This is the output from sudo gpt -r show /dev/disk0 gpt show: /dev/disk0: Suspicious MBR at sector 0 start size index contents 0 1 MBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6 40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640 776617328 2 MBR part 218 777026968 1269760 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC 778296728 616 778297344 198807552 4 MBR part 175 977104896 131 977105027 32 Sec GPT table 977105059 1 Sec GPT header **Progress:** I have executed command sudo gpt destroy /dev/disk0 But when I tried to add the first partition back using this command sudo gpt add -b 40 -s 409600 -i 1 -t C12A7328-F81F-11D2-BA4B-00A0C93EC93B /dev/disk0 I got this error straight away gpt add: /dev/disk0: Suspicious MBR at sector 0 gpt add: /dev/disk0: error: no primary GPT header; run create or recover Now the command sudo gpt -r show /dev/disk0 gives me this gpt show: /dev/disk0: Suspicious MBR at sector 0 start size index contents 0 1 MBR 1 409639 409640 776617328 2 MBR part 218 777026968 1269760 3 MBR part 175 778296728 616 778297344 198807552 4 MBR part 175 977104896 164 **Progress 2:** I executed sudo gpt create /dev/disk0 and got this error: gpt create: /dev/disk0: Suspicious MBR at sector 0 gpt create: /dev/disk0: error: device contains a MBR and I executed this command sudo fdisk -i -a hfs /dev/disk0 to write new MBR and executed sudo gpt create /dev/disk0 again but got the same error gpt create: /dev/disk0: error: device contains a MBR Now sudo gpt -r show /dev/disk0 gives me this start size index contents 0 1 MBR 1 62 63 977104997 1 MBR part 175 **Progress 3 and final :D** Firstly a big thank to @klanomath, without the help, I couldn't go this far. I executed this command sudo gpt create -fp /dev/disk0 And this command sudo gpt recover /dev/disk0 to get the secondary GPT header After that, I executed sudo gdisk /dev/disk0 and the disk is mounted and functions properly

It has been 3 days, I was trying to recover it but now I am out of options. I've tried installing Kali Linux on my Mac as a dual boot with a Linux partition of 20.5 GB inside my 500GB SSD and 1GB of swap Linux but after the first boot everything vanished and a black screen with a question mark came. So I searched websites and found @klanomath's answers about fixing the partition table and I messed it up, please help. 1. Maybe I fixed GPT row maybe as shown in pictures through @klanomath's answers. 2. Fdisk isn't fixing up, nothing is showing up there. 3. No core storage volume found within diskutil cs list 4. Not able to repair disk via command, unrecognised file system. Please help, it's the only last data I have of my life. Sorry for my English.

I have a PowerMac G5 PPC running Tiger and an old, white, Santa Rosa MacBook running Leopard. If I create cloned disc images of these OS drives, will I be able to run them in VMWare Fusion/Parallels/etc. on a modern Intel Mac? If I were to create bootable clones of these drives, would these need to be formatted as APM on FireWire drives that would only be accessible from the G5 &/or SR MacBook as opposed to bootable clones formatted as GUID on USB drives accessible from any modern Mac? Is there any reason I would want to clone the drives via Target Disk Mode, hooked up to an Intel Mac, as opposed to cloning them directly from their own interfaces or from an Intel Mac with access to them via ethernet LAN? Thank you

I am trying to resize the partition disk0s2 in my Mac. My diskutil list shows:

/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 disk1         60.6 GB    disk0s2
   3:       Microsoft Basic Data                         209.7 MB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +60.6 GB    disk1
                                 Physical Store disk0s2
   1:                APFS Volume macOs - Data            46.4 GB    disk1s1
   2:                APFS Volume Preboot                 82.6 MB    disk1s2
   3:                APFS Volume Recovery                525.8 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
   5:                APFS Volume macOs                   11.1 GB    disk1s5

and my diskutil apfs list:

APFS Container (1 found)
|
+-- Container disk1 8C3CDC58-CC44-4C3D-AD28-F03925313A0F
    ====================================================
    APFS Container Reference:     disk1
    Size (Capacity Ceiling):      60561534976 B (60.6 GB)
    Capacity In Use By Volumes:   59352715264 B (59.4 GB) (98.0% used)
    Capacity Not Allocated:       1208819712 B (1.2 GB) (2.0% free)
    |
    +- Volume disk1s1 31BAEA1D-A9A7-4FB8-9715-799815340E26
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s1 (Data)
    |   Name:                      macOs - Data (Case-insensitive)
    |   Mount Point:               /System/Volumes/Data
    |   Capacity Consumed:         46438572032 B (46.4 GB)
    |   FileVault:                 No
    |
    +-> Volume disk1s2 E195C9A9-5014-466D-BF1F-BC0CD64F5A5F
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s2 (Preboot)
    |   Name:                      Preboot (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         82649088 B (82.6 MB)
    |   FileVault:                 No
    |
    +-> Volume disk1s3 48CA81D5-5C73-41B3-8880-3A9C6BB1D33F
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s3 (Recovery)
    |   Name:                      Recovery (Case-insensitive)
    |   Mount Point:               /Volumes/Recovery
    |   Capacity Consumed:         525787136 B (525.8 MB)
    |   FileVault:                 No
    |
    +-> Volume disk1s4 F651611C-EC8C-440A-897B-C27CA5BDB0D5
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s4 (VM)
    |   Name:                      VM (Case-insensitive)
    |   Mount Point:               /private/var/vm
    |   Capacity Consumed:         1074814976 B (1.1 GB)
    |   FileVault:                 No
    |
    +-> Volume disk1s5 97B73362-8020-4C32-A659-652EAAF8893D
        ---------------------------------------------------
        APFS Volume Disk (Role):   disk1s5 (System)
        Name:                      macOs (Case-insensitive)
        Mount Point:               /
        Capacity Consumed:         11110051840 B (11.1 GB)
        FileVault:                 No

However, when I try to resize my container disk0s2 by:

diskutil ap resizeContainer disk0s2 0

I get:

Started APFS operation
Aligning grow delta to 29.438.464.000 bytes and targeting a new physical store size of 89.999.998.976 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 60.561.534.976 bytes
Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the beginning of another partition or beyond the end of partition map usable space

I have about 60GB free in my disk0, but it is not even being showed up in my Disk Utility: How can I add this 60Gb free on my disk0s2??

I have a Mac that is running Mojave, and yesterday I was trying to repartition the disk so I could get more space on my Windows partition for bootcamp. In the process, the Windows folder only appeared for me to boot up. So I decided to install gdisk. In the process, I specified h for hybrid recovery command and used 2, 3, 4 for GPT partition numbers. When it asked to specify a hex code, I used ac for partition 2, 07 for partition 3, and 07 for partition 4. I then told it to set the bootable flag for partition 3. It then asked me if I wanted to change partition 4 to EE so I said yes. I have data on partition 2 I would like to recover, if that is still possible. Now, I cannot boot into either Mac or Windows. And the ability to use gdisk has disappeared. Thanks for your help.

I was copying data from an old ds112 Synology hard drive to a new install on a ds112 due to board failure of the other one. I have the old drive in a caddy and was successfully copying data when I had a power failure. When trying to restart the copying I get the following errors when using extFS for Mac: Error while iterating over blocks in inode 6356: input/output error Either the superblock or the partition is likely to be corrupt I have these errors in Terminal: Unable to verify this whole disk: A Guid Partition Table (GPT) partitioning scheme is required (-697773) I don't have a clue what I am doing. I'm trying not to destroy the data. MacM:~ root# sudo diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *320.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 319.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *124.2 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Microsoft Basic Data ex128gb 123.9 GB disk1s2 /dev/disk2 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *2.0 TB disk2 1: Linux 2.6 GB disk2s1 2: Linux_Swap 2.1 GB disk2s2 3: Linux 2.0 TB disk2s3 **Some details about the disk** MacM:~ root# sudo diskutil info disk2 Device Identifier: disk2 Device Node: /dev/disk2 Whole: Yes Part of Whole: disk2 Device / Media Name: UITRA1 Volume Name: Not applicable (no file system) Mounted: Not applicable (no file system) File System: None Content (IOContent): FDisk_partition_scheme OS Can Be Installed: No Media Type: Generic Protocol: USB SMART Status: Not Supported Disk Size: 2.0 TB (2000398934016 Bytes) (exactly 3907029168 512-Byte-Units) Device Block Size: 512 Bytes Read-Only Media: No Read-Only Volume: Not applicable (no file system) Device Location: External Removable Media: Fixed Virtual: No MacM:~ root# sudo diskutil repairDisk disk2 Unable to repair this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773) MacM:~ root# sudo gpt show disk2 start size index contents 0 1 MBR 1 255 256 4980480 1 MBR part 131 4980736 4194304 2 MBR part 130 9175040 262144 9437184 3897586881 3 MBR part 131 3907024065 5103 UPDATE: extFS for mac is software by paragon. i have the software on my mac trying to recover software from a nas file server, the power went during a successful copy when i had the old nas drive in a caddy plugged into my new nas file server. when i tried to restart, the new nas drive would not recognise the usb caddy and kept throwing an i/o error. plugged back into my mac to use the extFS software and now i am getting the above errors just to reiterate i have no idea what i am doing. i am not technical. all i know it was working, my new nas box was recognising the usb drive and i was copying the data across. The extFS software could read the drive. power cut = nothing is able to read the drive - errors stated above.

I tried to enlarge the bootcamp windows 10 partition by 17gb. I went to disk utility on my mac, resized the mac's partition to smaller leaving 17-18gb of free space, then booted up the windows in bootcamp mode, started easyus partition master. I saw the 17-18gb partition (the only one of that size), wiped it and tried to merge it with the windows partition. EasyUs informed me that the system needs to restart to make these changes. The restart failed 2 times (windows crashed) and finally booted successfully the third time. The partition hasn't change the size. I tried to boot into my macOS to see what is the current structure but it doesn't appear among the bootable Operating Systems after restarting and hiting alt. My question is similar to this one but I don't seem to have a HFS recovery volume visible. I tried to fix it with gdisk but since I can't find the Recovery HD volume I can't set its GUID nor its properties. The partitions in EasyUS- the largest one is the MacOS 353,9 gb: What do I need to do in order to get my beloved macOS back? I have a backup but it's not that recent and I'd love to get this back. From what I understand I will have to change GUID types and attribute value but on what partitions? I suppose the partition of 492 mb might be the missing Mac recovery partition but is surprisingly formatted in NTFS... I attach below the details of macOS 353gb partition. There is an info - there's no volume associated with this partition - seems to be a problem.

I had a very freak electrical accident with my iMac 5K a few weeks ago. One of my external drives (my backup drive) shorted out and would no longer mount. I decided to buy an 3.5" enclosure as I figured it was just the power supply that died. Now, when connected I get a "This drive could not be read…" I've run numerous terminal commands and some third party software, and as far as I can tell, the data is all intact, but but it looks like the drive configuration and headers are messed up. I see errors such as: "Check the harddisk size: HD jumper settings, BIOS detection..." "…no primary or secondary GPT headers, can't recover…" "…unrecognized file system (-69846)…" --- I'm talking out of my butt here, but it seems like the drive headers(?) could be reset correctly and the partition would magically show up. Here's the results of several scans. The drive in question is disk2, and disk2s1 appears to be the partition in question:

> diskutil list

/dev/disk2 (external, physical):
   #:         TYPE NAME                    SIZE          IDENTIFIER
   0:         FDisk_partition_scheme      *4.0 TB        disk2
   1:         0xEE                         500.1 GB      disk2s1

> sudo gpt show disk2

       start             size        index  contents
           0                1         PMBR
           1       7813971632

> testdisk > analyze >

Disk /dev/rdisk2 - 4000 GB / 3725 GiB - 7813971633 sectors
Current partition structure:
     Partition                  Start        End    Size in sectors

Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.

Data Rescue returns what looks like a clean filesystem on its scan:

I started having this issue when I tried to swap my sshd for an ssd. My caddy was broken so I tired booting into bootcamp to run disk cloning software. (Seagate backup time machine disk failed on me. I should have bought a new one on during the sales) Windows 8 ran the disk startup utility which allowed me to boot. However, once I restarted I could no longer boot into osx and I got the dreaded all f partition type. I followed a few posts on here and was able to get my partitions visible. Bootcamp is visible with no issues but my osx partition is still unmountable. Have reinstalled OSX on the new ssd and have mounted the old drive in a drive caddy. I'd really appreciate some support on this. Thanks Iridium

I tried to create an NTFS partition on an HFS+ formatted Mac external hard drive, from within Windows. This hosed the GUID table. In order to try to recover the files, I had to turn off journaling, and that required a Mac. One of the employees at my local Free Geek chapter lent me his Macbook during an Open Help Night last month, and I managed to disable journaling, but in the process, ended up wiping the whole partition table! I currently don't have access to a Mac. I would have reformatted the external drive and started from scratch, but I literally don't have enough disk space in my house (only 250GB on my HDD, and there's more than 300GB stored on the external drive) to relocate the data while I wipe it. I ordered a 5TB external drive online, but it won't be here until Tuesday. In the meantime, is it possible to rebuild the GUID partition table in Windows or Linux, or am I screwed? The TestDisk log (executed on an Ubuntu live CD), if it helps:

Wed Jan 15 15:51:21 2020  
Command line: TestDisk 
  
TestDisk 7.0, Data Recovery Utility, April 2015  
Christophe GRENIER 
http://www.cgsecurity.org 
OS: Linux, kernel 5.0.0-13-generic (#14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019) x86_64
Compiler: GCC 8.2
ext2fs lib: 1.44.6, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.1
/dev/sda: LBA, HPA, LBA48, DCO support  
/dev/sda: size       488397168 sectors  
/dev/sda: user_max   488397168 sectors  
/dev/sda: native_max 488397168 sectors  
/dev/sda: dco        488397168 sectors  
Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512
/dev/sr0 is not an ATA disk  
Hard disk list
Disk /dev/sda - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - WDC WD2500JS-40TGB0, S/N:WD-WCANY1877189, FW:20.06C04  
Disk /dev/sdb - 5000 GB / 4657 GiB - CHS 76000 255 63, sector size=4096 - Seagate Backup+  Desk, FW:0342
Disk /dev/sr0 - 4700 MB / 4482 MiB - 2295104 sectors, sector size=2048 - TSSTcorp DVD+/-RW SN-208BB, S/N:R8KK6GJC6001T1, FW:D300  
  
Partition table type (auto): Intel
Disk /dev/sdb - 5000 GB / 4657 GiB - Seagate Backup+  Desk  
Partition table type: Mac  
  
Analyse Disk /dev/sdb - 5000 GB / 4657 GiB - CHS 76000 255 63  
Current partition structure:
Bad MAC partition, invalid block0 signature
read_part_mac: bad DPME signature
  
search_part()
Disk /dev/sdb - 5000 GB / 4657 GiB - CHS 76000 255 63  
NTFS at 0/32/33
filesystem size           1220940597
sectors_per_cluster       1
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   1
clusters_per_index_record 1
     Unknown                     2048 1220942644 1220940597 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 5000 GB / 4657 GiB
Partition not added.
  
HFSX magic value at 3/47/51
  
HFSX magic value at 3/47/51
part_size 1220858666
     HFS                        51206 1220909871 1220858666  
     HFSX blocksize=4096 + Backup, 5000 GB / 4657 GiB
  
Results
   P HFS                        51206 1220909871 1220858666  
     HFSX blocksize=4096 + Backup, 5000 GB / 4657 GiB
  
Hint for advanced users. dmsetup may be used if you prefer to avoid to rewrite the partition table for the moment:
echo "0 9766869328 linear /dev/sdb 409648" | dmsetup create test0  
  
interface_write()
   P HFS                        51206 1220909871 1220858666
Function write_part_mac not implemented
Partition table type (auto): Intel
Disk /dev/sdb - 5000 GB / 4657 GiB - Seagate Backup+  Desk
Partition table type: EFI GPT
  
Analyse Disk /dev/sdb - 5000 GB / 4657 GiB - CHS 76000 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=1220942644 (expected 1220942644)
hdr_lba_start=6
hdr_lba_end=1220942639
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
hdr_size=92
hdr_lba_self=1220942644
hdr_lba_alt=1 (expected 1)
hdr_lba_start=6
hdr_lba_end=1220942639
hdr_lba_table=1220942640
hdr_entries=128
hdr_entsz=128
Trying alternate GPT
Current partition structure:
Trying alternate GPT
  
search_part()
Disk /dev/sdb - 5000 GB / 4657 GiB - CHS 76000 255 63
NTFS at 0/32/33
filesystem size           1220940597
sectors_per_cluster       1
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   1
clusters_per_index_record 1

     MS Data                     2048 1220942644 1220940597 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 5000 GB / 4657 GiB
  
Results
   P MS Data                     2048 1220942644 1220940597 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 5000 GB / 4657 GiB
  
Hint for advanced users. dmsetup may be used if you prefer to avoid to rewrite the partition table for the moment:`  
echo "0 9767524776 linear /dev/sdb 16384" | dmsetup create test0`  
  
interface_write()
 P MS Data                     2048 1220942644 1220940597 [Seagate Backup Plus Drive]
simulate write!
  
TestDisk exited normally.

I upgraded internal kSSD on my mac (MBP-2013) via Carbon Copy Cloner. OSX loads fine, but for some reason I cannot boot into Windows that I have installed on external USB in MBR mode. Prior to changing the internal SSD the USB in MBR was booting fine. My I do need to have Windows installed via BIOS/MBR to use external GPU. I tried installing via Virtualbox and via unebootin , but have the same result - when I restart MBP to continue Windows installation I see a cursor for a second and then the screen goes blank. Not black as if it was turned off but blank - the display is clearly working but there is nothing being displayed. My latest steps: 1. Format USB as MBR/Fat32 2. Get to final stages of Windows 10 Installer in Virtualbox 3. Reboot hold ALT -> pick Windows 4. Blank screen What can I do to get Windows installation to continue in MBR mode? A note - if I format USB as GUID I can install and boot from USB windows just fine.

I have an old WD MyBook Ext Drive and I couldn't access the greyed out sub-partition in DiskUtility. I was trying to fix it with various Terminal commands relating to GPT and somehow I managed to mess up the partition table. This is what I get from $ diskutil list: /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk1 And this is what I get from: $ sudo gpt show disk1 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 976773101 976773135 32 Sec GPT table 976773167 1 Sec GPT header I know the data is on there but I think the table needs to be rebuilt, but have zero clue to get there..... Can anyone give me pointers as to how to do this? It's a 500gb WD drive. EDIT: Another user pointed out that I posted about this disk a year ago but never got a resolution. Here is the additional info from that disk BEFORE I managed to mess with it and delete the partition table: /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: Apple_partition_scheme *500.1 GB disk2 1: Apple_partition_map 32.3 KB disk2s1 2: Apple_HFS General DATA 500.0 GB disk2s3 Also from that that other thread prior ot me messing with it: $ diskutil info /dev/disk1 Device Identifier: disk1 Device Node: /dev/disk1 Whole: Yes Part of Whole: disk1 Device / Media Name: WD Volume Name: Not applicable (no file system) Mounted: Not applicable (no file system) File System: None Content (IOContent): GUID_partition_scheme OS Can Be Installed: No Media Type: Generic Protocol: FireWire SMART Status: Not Supported Disk Size: 500.1 GB (500107862016 Bytes) (exactly 976773168 512-Byte-Units) Device Block Size: 512 Bytes Here is the result TODAY of the command from @klanomath $ sudo dd if=/dev/disk1 skip=409640 bs=512 count=3 | hexdump 3+0 records in 3+0 records out 1536 bytes transferred in 0.510661 secs (3008 bytes/sec) 0000000 00 63 00 74 00 73 00 2e 00 6e 00 69 00 62 00 06 0000010 00 24 ba 6b 00 00 00 04 00 00 00 24 ba 69 00 0b 0000020 00 52 00 65 00 6d 00 6f 00 76 00 65 00 2e 00 74 0000030 00 69 00 66 00 66 00 06 00 24 ba 6c 00 00 00 04 0000040 00 00 00 24 b5 71 00 11 00 49 00 6e 00 66 00 6f 0000050 00 50 00 6c 00 69 00 73 00 74 00 2e 00 73 00 74 0000060 00 72 00 69 00 6e 00 67 00 73 00 06 00 24 ba 6d 0000070 00 00 00 03 00 00 00 24 b5 71 00 0e 00 49 00 6e 0000080 00 66 00 6f 00 57 00 69 00 6e 00 64 00 6f 00 77 0000090 00 2e 00 6e 00 69 00 62 00 26 00 24 ba 6d 00 10 00000a0 00 6b 00 65 00 79 00 65 00 64 00 6f 00 62 00 6a 00000b0 00 65 00 63 00 74 00 73 00 2e 00 6e 00 69 00 62 00000c0 00 02 00 0e 00 00 00 00 00 24 ba 6e c5 af fc b0 00000d0 c5 af fc b0 ce fa 08 d7 ce fa 08 d7 00 00 00 00 00000e0 00 00 00 00 00 00 00 50 00 00 81 b4 00 00 00 01 00000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15 f2 0000120 00 00 00 00 00 00 00 02 02 84 6f 36 00 00 00 02 0000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 00001b0 00 00 00 00 00 00 00 00 00 06 00 24 ba 6e 00 00 00001c0 00 04 00 00 00 24 ba 6d 00 10 00 6b 00 65 00 79 00001d0 00 65 00 64 00 6f 00 62 00 6a 00 65 00 63 00 74 00001e0 00 73 00 2e 00 6e 00 69 00 62 00 06 00 24 ba 6f 00001f0 00 00 00 04 00 00 00 24 b5 71 00 23 00 69 00 50 0000200 00 61 00 64 00 20 00 61 00 6e 00 64 00 20 00 69 0000210 00 50 00 68 00 6f 00 6e 00 65 00 34 00 2e 00 63 0000220 00 6f 00 6d 00 70 00 72 00 65 00 73 00 73 00 6f 0000230 00 72 00 54 00 65 00 6d 00 70 00 6c 00 61 00 74 0000240 00 65 00 06 00 24 ba 70 00 00 00 03 00 00 00 24 0000250 b5 71 00 0b 00 4a 00 6f 00 62 00 54 00 69 00 6c 0000260 00 65 00 2e 00 6e 00 69 00 62 00 26 00 24 ba 70 0000270 00 10 00 6b 00 65 00 79 00 65 00 64 00 6f 00 62 0000280 00 6a 00 65 00 63 00 74 00 73 00 2e 00 6e 00 69 0000290 00 62 00 02 00 0e 00 00 00 00 00 24 ba 71 c6 0b 00002a0 20 90 c6 0b 20 90 ce fa 08 d7 ce fa 08 d7 00 00 00002b0 00 00 00 00 00 00 00 00 00 50 00 00 81 b4 00 00 00002c0 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00002d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 00002f0 50 e2 00 00 00 00 00 00 00 06 02 84 6f 3a 00 00 0000300 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000310 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000380 00 00 00 00 00 00 00 00 00 00 00 06 00 24 ba 71 0000390 00 00 00 04 00 00 00 24 ba 70 00 10 00 6b 00 65 00003a0 00 79 00 65 00 64 00 6f 00 62 00 6a 00 65 00 63 00003b0 00 74 00 73 00 2e 00 6e 00 69 00 62 00 06 00 24 00003c0 ba 72 00 00 00 03 00 00 00 24 b5 71 00 07 00 4c 00003d0 00 61 00 79 00 6f 00 75 00 74 00 73 00 40 00 24 00003e0 ba 72 00 1d 00 43 00 6f 00 6d 00 70 00 72 00 65 00003f0 00 73 00 73 00 6f 00 72 00 2e 00 73 00 61 00 76 0000400 00 65 00 64 00 2e 00 6d 00 6f 00 64 00 75 00 6c 0000410 00 65 00 4c 00 61 00 79 00 6f 00 75 00 74 00 02 0000420 00 0e 00 00 00 00 00 24 ba 73 c2 25 0f 72 c2 25 0000430 0f 72 ce fa 08 d7 ce fa 08 d7 00 00 00 00 00 00 0000440 00 00 00 00 00 50 00 00 81 b4 00 00 00 01 00 00 0000450 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000470 00 00 00 00 00 00 00 00 00 00 00 00 18 c7 00 00 0000480 00 00 00 00 00 02 02 84 6f 40 00 00 00 02 00 00 0000490 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000510 00 00 00 00 00 00 00 06 00 24 ba 73 00 00 00 04 0000520 00 00 00 24 ba 72 00 1d 00 43 00 6f 00 6d 00 70 0000530 00 72 00 65 00 73 00 73 00 6f 00 72 00 2e 00 73 0000540 00 61 00 76 00 65 00 64 00 2e 00 6d 00 6f 00 64 0000550 00 75 00 6c 00 65 00 4c 00 61 00 79 00 6f 00 75 0000560 00 74 00 06 00 24 ba 74 00 00 00 04 00 00 00 24 0000570 b5 71 00 13 00 4c 00 6f 00 63 00 61 00 6c 00 69 0000580 00 7a 00 61 00 62 00 6c 00 65 00 2e 00 73 00 74 0000590 00 72 00 69 00 6e 00 67 00 73 00 06 00 24 ba 75 00005a0 00 00 00 03 00 00 00 24 b5 71 00 0c 00 4d 00 61 00005b0 00 69 00 6e 00 4d 00 65 00 6e 00 75 00 2e 00 6e 00005c0 00 69 00 62 00 26 00 24 ba 75 00 10 00 6b 00 65 00005d0 00 79 00 65 00 64 00 6f 00 62 00 6a 00 65 00 63 00005e0 00 74 00 73 00 2e 00 6e 00 69 00 62 00 02 00 0e 00005f0 00 00 00 00 00 24 ba 76 c6 0a f7 a1 c6 0a f7 a1 0000600 Any help SUPER appreciated.

Setup Macbook Pro retina 13 A1502, SSD 128Gb Running Yosemite, but currently doing the update for high sierra. Problem: Question marked folder appear after I left it for 2 days, battery run out (left it on sleep I think with minimal battery). It showed me a black screen I turned off&on again and folder with question marked appeared. I tried to reinstall using recovery tools, doesn't even show a selectable disk. Tried to Verify and Repair, nothing. I created a bootable external OS X, from which I'm asking this, and I partitioned the SSD into 1. Curious thing: OS X was in a different partition from the ssd. Another curious thing is that the sdd disappears after I try something. At some point I think it was in the hardware diagnose I found a error that pointed that EFI was broken. I ran sudo gpt -r show disk0s2 and this showed start size index contents 0 236568496 EDIT: The disks images I have (the Apple SSD long name) disk0s2 (External disk long name) disk1 (renamed by me trying to follow a solution) Disk2 OS X Base System The result of the disk verifying tool "The Partition Map needs to be repaired because there is a problem with the EFI system partition's file system" The Hardware diagnostic result Reference code vdh002 Running gdisk sudo gdisk /dev/disk0s2 GPT fdisk (gdisk) version 1.0.4 Partition table scan: MBR: not present BSD: not present APM: not present I tried the answers provided to similar questions [here](https://superuser.com/questions/1122951/primary-gpt-is-missing-and-filevault-volume-too) , [here](https://discussions.apple.com/thread/7056781?tstart=0) , and [here](https://apple.stackexchange.com/questions/221114/how-to-fix-broken-gpt-guid-and-unmountable-no-type-volumes) . None of them resolved my problem. I guess I need to rebuild the EFI? What do I need to do?

I have an expanding network and while I have the long term goal of eventually implementing Active Directory hosted on a QNAP NAS. However, in the meantime I have the issue of where my MacOS machines have one set of UIDs for the 2 or 3 users I use while my Linux machine have another. I learned that in Mojave you need to use dscl to change attributes like UID but I am not sure how I can set the UID scheme for new users to make the new Unix and MacOS accounts more easily line up going forward. While I envision Active Directory making this moot once its in place, I presume I must get my LANs UIDs and GUIDs under control first. Aside from doing all of this manually by using tools like find and chown manually, are there tools for migrating to AD where normalizing UIDs for the same users across different hosts can be better automated and a reliable process with less risk of breakage? If not, I am pretty sure I know what I need to do and it will be gritting my teeth, but at least I know what it's going to take. If you have any suggestions that might make this easier and less dangerous please share your thoughts! For instance, I presume that no user should have it's UID changed while logged in, yes? Anwyay I welcome all thoughts and ideas!

I have an external hard drive with two partitions, each one formatted as "OS X Extended (Journaled, Encrypted)". The second partition mounts and asks for a password, but the first one does not. The hard drive is 1TB, the first partition is 895GB and the second partition is 104GB. This is the output from diskutil list /dev/disk2 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_CoreStorage 895.1 GB disk2s2 3: Apple_CoreStorage Extra 104.7 GB disk2s3 4: Apple_Boot Boot OS X 134.2 MB disk2s4 /dev/disk3 (external, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFSX Extra +104.4 GB disk3 Logical Volume on disk2s3 888F03E6-B0A4-4E12-BA48-1DD1D1C3ED48 Unlocked Encrypted This is the output from sudo gpt -r show disk2 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6 40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640 1748305920 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC 1748715560 2008 1748717568 204539864 3 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC 1953257432 262144 4 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC 1953519576 7 1953519583 32 Sec GPT table 1953519615 1 Sec GPT header This is the output from sudo gpt -r show disk2s2. (The partition which won't mount). start size index contents 0 1748305920 This is the output from sudo gpt -r show disk2s3. (The partition which mounts). start size index contents 0 204539864 This is the output from sudo fsck_cs -y disk2s2. (The partition which won't mount). Executing fsck_cs (version 517.50.1) ** Checking volume ** disk2s2: Scan for Volume Headers Invalid Volume Header @ 0: unsupported format Invalid Volume Header @ 895132630528: invalid field value ** disk2s2 did not complete formatting as a CoreStorage volume [Edit 1] Here is the output from diskutil cs list CoreStorage logical volume groups (2 found) +-- Logical Volume Group F99A19A9-A491-475F-8271-3601E6624322 | ========================================================= | Name: MAINOS | Status: Online | Size: 209200443392 B (209.2 GB) | Free Space: 4681728 B (4.7 MB) | | | +- Logical Volume Family 41D930F7-7256-47C2-A660-B217DF788D79 | ---------------------------------------------------------- | 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 7B8D4144-0957-4D2F-9B7B-6FF545C56555 | --------------------------------------------------- | Disk: disk1 | Status: Online | Size (Total): 208843440128 B (208.8 GB) | Revertible: Yes (unlock and decryption required) | LV Name: MAINOS | Volume Name: MAINOS | Content Hint: Apple_HFS | +-- Logical Volume Group C909C3EC-B2C7-4E5A-B5EF-A9D18E3CA594 ========================================================= Name: Extra Status: Online Size: 104724410368 B (104.7 GB) Free Space: 1024000 B (1.0 MB) | +- Logical Volume Family BC19D010-6E0C-49F6-A6A7-92FF7DA5A972 ---------------------------------------------------------- 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 888F03E6-B0A4-4E12-BA48-1DD1D1C3ED48 --------------------------------------------------- Disk: disk3 Status: Online Size (Total): 104371060736 B (104.4 GB) Revertible: No LV Name: Extra Volume Name: Extra Content Hint: Apple_HFSX I believe the partition header is broken, but I'm unsure. It sounds similar to issues posted here and here . I don't know how to go about fixing this and getting that first partition to mount.