I have an external drive I haven't accessed recently (a year ago? Perhaps longer? Certainly within the last three years). This is a bare 3.0 TB Western Digital drive (HDD/platters) I put into a Wavlink USB 3.0 HDD Docking station. The drive spins up and seems OK (no clicking or other sounds like the arm is having trouble accessing blocks). I get a message from macOS that this drive is unreadable. Looking at it from within Disk Utility I see the name of the drive, its size and that it is a CoreStorage Logical Volume • Mac OS Extended (Encrypted). I have accessed it in the past from my MacBook but thought perhaps since I have upgraded it to Sequoia that the newer OS doesn't read the older formatting. I have an older iMac running macOS Ventura 13.7.1 which I thought would have no problem reading it if the issue is Sequoia. The iMac did recognize it is an encrypted volume and accepted the password to decrypt the volume. But again I get the message the drive is unreadable and won't mount. Has this drive become corrupted due to non-use? Or has the older formatting scheme of plastered drives become obsolete with the macOS? I used to do drive recovery decades ago but my skills are outdated and I don't even know what recovery software is currently used (anyone remember when Norton worked on a Mac?)

Yesterday, I have tried to delete an Ubuntu partition. Since, my Mac (13", MBPro mid-2014) doesn't boot. Now, I boot on Mac OS copy with an USB. i follow different subject of this forum (like this : https://apple.stackexchange.com/questions/239759/partition-type-suddenly-ffffffff-ffff-ffff-ffff-ffffffffffff-drive-unmountable) , and my volume partition change from **FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF** to **48465300-0000-11AA-AA11-00306543ECAC**. But I still can't boot to it... Thank you very much !

I have an external hard drive that is partitioned as a single encrypted HFS+ volume. Here's what's going on: The volume won't mount, Disk Utility won't repair it. diskutil cs list says: However: diskutil coreStorage unlockVolume 042F9672-CEEC-47D3-8749-4D4F5A52B6CE -stdinpassphrase returns 042F9672-CEEC-47D3-8749-4D4F5A52B6CE is already unlocked and is attached as disk5 and diskutil mount disk5 returns disk5 is a CoreStorage Logical Volume which failed to mount Other things i tried: diskutil cs decryptVolume 042F9672-CEEC-47D3-8749-4D4F5A52B6CE Which returned The Core Storage Logical Volume UUID is 042F9672-CEEC-47D3-8749-4D4F5A52B6CE Started CoreStorage operation on disk5 Cairo Scheduling decryption of Core Storage Logical Volume Core Storage LV UUID: 042F9672-CEEC-47D3-8749-4D4F5A52B6CE Finished CoreStorage operation on disk5 Cairo But now my diskutil cs list looks like this and it has for an hour. I'm lost, i'm stuck, i'd need help.

I bought a new external hard drive for my Mac. What is the best file system in 2021 to format the external hard drive? I would like to encrypt the hard drive and I only use it with Macs so I don't need Windows compatibility. I used to format external drives with encrypted APFS but I heard it's not the best file system for spinning hard drives, only for SSDs. Has anyone experience with this? Pros and cons? Should I use APFS or HFS+ for external hard drives? Thank you!

How can i unlock a Partition that has been created and **encrypted** using Apples **Disk Utility** on a **linux machine**? There are 2 formats one can encrypt Volumes with **Disk Utility** : - CoreStorage encrypted Volume - apfs encrypted Container I'm interested in both methods, if there are such.

I bought a new iMac (Retina 4K, 21.5-inch, 2017, with macOS High Sierra 10.13.5) and used Boot Camp to install Windows 10 on it. The Boot Camp drivers seem to have been installed successfully, and most things seem to work, but I am unable to access the Mac partition from Windows. According to [what I have read](https://www.howtogeek.com/189250/how-to-share-files-between-mac-os-x-and-windows-with-boot-camp/) , the Boot Camp drivers are supposed to have a read-only driver for HFS+, but "Macintosh HD" does not show up for me. I've read that [FileVault could be the problem](https://apple.stackexchange.com/questions/213241/read-only-hfs-on-windows-10-with-boot-camp-driver-question) , but I double-checked, and FileVault is not enabled. Then I read that the problem might be because of something called [Core Storage](https://apple.stackexchange.com/questions/167874/why-i-can-not-see-mac-partition-under-windows-installed-with-bootcamp) . So I tried to follow [these instructions](https://apple.stackexchange.com/questions/167868/cant-make-more-than-two-partitions) to revert the partition. However, that only works if Revertible is Yes, and in my case, it is No.

logical volume groups (1 found)
|
+-- Logical Volume Group 9C641579-4351-491E-923A-B2DA1CF80C12
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         724916166656 B (724.9 GB)
    Free Space:   81920 B (81.9 KB)
    |
    +- Logical Volume Family 9619CA26-4D92-43F6-AC54-3E10E7F774A0
        ----------------------------------------------------------
        Encryption Type:         None
        |
        +-> Logical Volume CF6F0197-EDB6-4DC3-B3C4-C22A3DC99D2C
            ---------------------------------------------------
            Disk:                  disk2
            Status:                Online
            Size (Total):          724000440320 B (724.0 GB)
            Revertible:            No
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
            LVG Type:              Fusion, Sparse

How can I access the Mac partition from Windows? ---- **Additional information:** Here is the result of running diskutil info /:

Device Identifier:        disk2
   Device Node:              /dev/disk2
   Whole:                    Yes
   Part of Whole:            disk2
   Device / Media Name:      APPLE HDD HTS541010A9E632

   Volume Name:              Macintosh HD
   Mounted:                  Yes
   Mount Point:              /

   Content (IOContent):      Apple_HFS
   File System Personality:  Journaled HFS+
   Type (Bundle):            hfs
   Name (User Visible):      Mac OS Extended (Journaled)
   Journal:                  Journal size 81920 KB at offset 0x183df000
   Owners:                   Enabled

   OS Can Be Installed:      Yes
   Booter Disk:              disk0s3
   Recovery Disk:            disk0s3
   Media Type:               Generic
   Protocol:                 PCI-Express
   SMART Status:             Not Supported
   Volume UUID:              F7E21D0B-FE27-3F1E-AF88-6B86912A95F6
   Disk / Partition UUID:    CF6F0197-EDB6-4DC3-B3C4-C22A3DC99D2C

   Disk Size:                724.0 GB (724000440320 Bytes) (exactly 1414063360 512-Byte-Units)
   Device Block Size:        4096 Bytes

   Volume Total Space:       724.0 GB (724000440320 Bytes) (exactly 1414063360 512-Byte-Units)
   Volume Used Space:        29.6 GB (29556273152 Bytes) (exactly 57727096 512-Byte-Units) (4.1%)
   Volume Free Space:        694.4 GB (694444167168 Bytes) (exactly 1356336264 512-Byte-Units) (95.9%)
   Allocation Block Size:    4096 Bytes

   Read-Only Media:          No
   Read-Only Volume:         No

   Device Location:          Internal
   Removable Media:          Fixed

   Solid State:              Yes
   Virtual:                  Yes
   Hardware AES Support:     No

   This disk is a Core Storage Logical Volume (LV).  Core Storage Information:
   LV UUID:                  CF6F0197-EDB6-4DC3-B3C4-C22A3DC99D2C
   LVF UUID:                 9619CA26-4D92-43F6-AC54-3E10E7F774A0
   LVG UUID:                 9C641579-4351-491E-923A-B2DA1CF80C12
   PV UUID (disk):           123FF2CC-8363-4551-AEF2-535FAABDA521 (disk1s2)
   PV UUID (disk):           52D21296-80AE-4BC8-BA5F-583E65C62B42 (disk0s2)
   Fusion Drive:             Yes
   Encrypted:                No

And here are a couple of screenshots from Disk Utility: Additionally, here is the Windows version:

I've hit a bit of an odd issue with my TimeMachine/external storage backup solution. Do note that I set it up while Apple was changing filesystem management systems (CoreStorage vs APFS vs OS/Data split), and it's debatable whether I used something sensible. ## The setup It's an external enclosure that contains 4x4TB disks (/dev/disk[2-5]), which are built in two 4TB RAID mirrors striped together (/dev/disk6), and a final CoreStorage volume on top (/dev/disk7), which hosts my TM backup and Photos library (see the diskutil output down below). Accesses using Finder work fine, though the bandwidth sometimes tanks hard and everything slows down randomly, so in retrospect I'd say that a stacked AppleRAID/CoreStorage monster isn't a recommended configuration. ## The problem The issue I have is that the volume is utterly inaccessible to anything command-line related. Here are permissions on the hidden /Volumes directory (or /System/Volumes/Data/Volumes, as I just discovered there's now a 2nd set of symlinks but they give out the same results):

$ ls -l /Volumes
total 0
drwxr-xr-x     6 root     wheel   192B Oct 28 15:18 ./
drwxr-xr-x    20 root     wheel   640B Mar 26  2022 ../
lrwxr-xr-x     1 root     wheel     1B Oct 18 17:10 Macintosh HD@ -> /
drwxrwxr-x    21 tiennou  staff   782B Oct 28 15:18 Shack/

$ ls /Volumes/Shack
ls: .: Operation not permitted

In other words, I cannot modify anything on it, cd autocompletion doesn't work, mkdir, cp and touch report the same permission error. I can move around directories by looking at names using Finder, and I've used [FSMonitor](https://fsmonitor.com/) to watch what accesses the Finder was doing and using the same path (that's where I got the /System/Volumes/Data/Volumes directory). Yesterday I rsync-ed stuff there in a directory I made using Finder for a couple hours, and after stopping it and checking around, that directory is still empty from Finder's perspective, so all that data was somehow sent to /dev/null? I didn't check disk usage before starting the copy, so I have no way to know if anything made it on the drive. ## The question I'm at a loss now. My TM backup looks okay (both backing up and restoring work), Photos sync works too, and Disk Utility reported no issue whatsoever with the /dev/disk7 drive. I'd even agree with someone telling me that's the cursedest setup they've ever seen and I should start over, but I'd really like to save me the hassle of copying 2TB to start over since there's a TM backup involved. Looking back, if it was possible to ditch AppleRAID entirely and put that whole stack of drive under CS that might have been less convoluted, but it's unclear if CS handles any kind of RAIDy things. If anyone has any insight, advice, or diagnostics to run, that would be helpful! ---------- ### Technical details

$ diskutil list

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk2
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk2s1
   2:                 Apple_RAID ⁨⁩                        4.0 TB     disk2s2
   3:                 Apple_Boot ⁨Boot OS X⁩               134.2 MB   disk2s3

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk3
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk3s1
   2:                 Apple_RAID ⁨⁩                        4.0 TB     disk3s2
   3:                 Apple_Boot ⁨Boot OS X⁩               134.2 MB   disk3s3

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk4
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk4s1
   2:                 Apple_RAID ⁨⁩                        4.0 TB     disk4s2
   3:                 Apple_Boot ⁨Boot OS X⁩               134.2 MB   disk4s3

/dev/disk5 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk5
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk5s1
   2:                 Apple_RAID ⁨⁩                        4.0 TB     disk5s2
   3:                 Apple_Boot ⁨Boot OS X⁩               134.2 MB   disk5s3

/dev/disk6 (external, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:          Apple_CoreStorage                        +8.0 TB     disk6

/dev/disk7 (external, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS ⁨Shack⁩                   +8.0 TB     disk7
                                 Logical Volume on disk6
                                 0956590F-5173-4AD3-B8A9-459A95D4ADDC
                                 Unlocked Encrypted

----------

$ diskutil ar list
AppleRAID sets (3 found)
===============================================================================
Name:                 lagrange-mirror-1
Unique ID:            37E6D0F0-6A8E-4EBF-8C8E-B76D8FD9B2A7
Type:                 Mirror
Status:               Online
Size:                 4.0 TB (4000443039744 Bytes)
Rebuild:              manual
Device Node:          -
-------------------------------------------------------------------------------
#  DevNode   UUID                                  Status     Size
-------------------------------------------------------------------------------
0  disk2s2   66A56A8A-2368-4D18-8629-146C788F47FE  Online     4000443039744
1  disk3s2   D188DACC-FC30-4326-864D-A9E78E9A2190  Online     4000443039744
===============================================================================
===============================================================================
Name:                 lagrange-raid
Unique ID:            1BD3A301-EA5B-46CC-806A-8BCCD7ADA450
Type:                 Stripe
Status:               Online
Size:                 8.0 TB (8000886013952 Bytes)
Rebuild:              manual
Device Node:          disk6
-------------------------------------------------------------------------------
#  DevNode   UUID                                  Status     Size
-------------------------------------------------------------------------------
0  -none-    37E6D0F0-6A8E-4EBF-8C8E-B76D8FD9B2A7  Online     4000443006976
1  -none-    DDC6E853-7F0F-4EB8-981B-AFBA900674AE  Online     4000443006976
===============================================================================
===============================================================================
Name:                 lagrange-mirror-2
Unique ID:            DDC6E853-7F0F-4EB8-981B-AFBA900674AE
Type:                 Mirror
Status:               Online
Size:                 4.0 TB (4000443039744 Bytes)
Rebuild:              manual
Device Node:          -
-------------------------------------------------------------------------------
#  DevNode   UUID                                  Status     Size
-------------------------------------------------------------------------------
0  disk4s2   F6ED3C8E-DFB1-4EAE-AFF2-48C2B62794FF  Online     4000443039744
1  disk5s2   2835A8EC-916C-4C26-96DF-C8334E06D40E  Online     4000443039744
===============================================================================

----------

$ diskutil cs list
CoreStorage logical volume groups (2 found)
|
+-- Logical Volume Group 4BDE5FCB-C0A8-46DC-B05D-C55A6C47E8AD
|   =========================================================
|   Name:         lagrange
|   Status:       Online
|   Size:         8000886013952 B (8.0 TB)
|   Free Space:   533688320 B (533.7 MB)
|   |
|   +- Logical Volume Family E35DD92B-913B-433E-8D1B-8087F646D3BF
|       ----------------------------------------------------------
|       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 0956590F-5173-4AD3-B8A9-459A95D4ADDC
|           ---------------------------------------------------
|           Disk:                  disk7
|           Status:                Online
|           Size (Total):          8000000000000 B (8.0 TB)
|           Revertible:            No
|           LV Name:               Shack
|           Volume Name:           Shack
|           Content Hint:          Apple_HFS
|
[snip]

I have a 14 TB external drive containing a single 14 TB HFS+ encrypted partition (besides EFI). I cannot resize this partition to add a new one. When I tried using either Disk Utility or

, it says > You can’t perform this resize unless it has a booter (target partition is probably too small) Essentially I am having the same issue as described in this question: https://apple.stackexchange.com/questions/315514/cant-resize-partition-you-cant-perform-this-resize-unless-it-has-a-booter However, the answer to that question does not work for my scenario because _there is no unallocated space after the single partition_ and I cannot manually add the booter using

or

because of that. My question is, - is there other ways to shrink this partition, besides moving everything out and reformatting it. Or, - how do I add in the required booter partition (so that I can resize normally using Disk Utility)? Note that this is a Core Storage volume because it is encrypted. - I had the idea of forcibly creating a new GPT table where there is enough space for the booter, but I haven't done that because I don't know how that would affect the existing partition. - I also tried using diskutil cs resizeVolume, which will resize the inner Logical Volume, and then I could add another Logical Volume after it. The problem is that these two volumes will then share the same encryption key AFAIK, which is not desirable. --- FYI, here are all the things that have happened that put me in this situation: - This is a brand new 14 TB hard drive. I originally formatted it into two partitions: one 10TB and one 4TB. Both were HFS+ journaled encrypted (so they were Core Storage volumes). - Later, I attempted to resize them into 12TB/2TB using Disk Utility, **which failed miserably.** - After this, the second 4TB partition could not be found, and the first one could not be mounted. This was reported by

cs info

about the first partition (originally 10TB):

|
    +-- Logical Volume Group 69E42F2B-A2E4-41EC-93A9-4D62C0C9082B
    |   =========================================================
    |   Name:         -none-
    |   Status:       Initializing
    |   Size:         0 B (0 B)
    |   Free Space:   -none-
    |   |
    |   +-< Physical Volume 4BBFE85D-06C3-4285-98D9-D6D30E3E4031
    |       ----------------------------------------------------
    |       Index:    0
    |       Disk:     disk2s2
    |       Status:   Failed
    |       Size:     14000175669248 B (14.0 TB)

- However, I managed to completely recover the first partition (filesystem intact and

passed), by **destroying and recreating the GPT table, in which the first partition occupies the entire disk** — that is, the end of the partition is now right before the secondary GPT. Now the GPT looks like this:

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  27344355255      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
    27344764895           32         Sec GPT table
    27344764927            1         Sec GPT header

- _And now I cannot resize the 14TB partition._

My MacBook Pro worked all normal when all of a sudden it went black. It tried to reboot itself but immediately produced a kernel panic. From then on I was never able to boot again. I could only enter my password (not for logging in to Mac OS, but for booting) and then the kernel panic would happen each time. The error log was only visible for a few seconds and then it rebooted itself again. I was able to take a photograph of the kernel error. I have no idea what actually happened, so I wonder if anyone of you can make sense of the error message or identify the reason why the system failed? The only thing that gives me a hint is the line about Core Storage Driver. In fact, I set up a HDD and SSD as a FusionDrive as explained in this article . I did this in november and used the MacBook every day since. Never had a problem until yesterday. Luckily, I had a fresh backup and have been able to restore everything in the meantime. I checked both the SSD and HDD drive with disk utility for errors but everything seems fine. Any idea what actually caused the error?

I can't figure out how to correct this at this point. I’m hoping someone here can point me in the correct direction. I have posted my terminal outputs below for diskUtil list and diskUtil cs list. @MacMini ~ % 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 Macintosh HD - Data 58.4 GB disk2s1 2: APFS Volume Preboot 83.2 MB disk2s2 3: APFS Volume Recovery 528.8 MB disk2s3 4: APFS Volume VM 3.2 GB disk2s4 5: APFS Volume Macintosh HD 11.0 GB disk2s5 /dev/disk3 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *8.0 TB disk3 1: EFI EFI 209.7 MB disk3s1 2: Apple_HFS Adult Entertainment 2.0 TB disk3s2 3: Apple_HFS Room4Activities 6.0 TB disk3s3 @MacMini ~ % diskUtil cs list No CoreStorage logical volume groups found @MacMini ~ %

I'd like to free up space on my mac's internal HD. I currently run with no external HDs. Seems like one option is to selectively move one or more apps (that I don't use very much), along with their associated libraries, from internal HD to external HD EHD. For the sake of the goals/criteria below, let's say (a) I'm not moving any /Users/*, and (b) EHD is an external SSD connected via USB-2. For any such low-use app App which is currently wholly-contained on my internal HD, I'd like to know how to move it to EHD such that: * if EHD is mounted/available, then startup or access times for App are not a primary concern (slow is ok) * I'm in control of EHD's mounting/availability (so if EHD isn't mounted, it means that I don't care about App's availability) * __key goals__: * keep macOS on internal HD * don't move /Users/* * regardless of whether or not EHD is mounted, any operations NOT associated with App (or its libraries) should have same functionality and performance as they currently do. I've looked at some old-ish SO questions ([Photos.App/Mail.App](https://apple.stackexchange.com/questions/351524/best-practices-to-move-macos-mail-app-storage-to-an-external-drive) , [IBooks.App](https://apple.stackexchange.com/questions/130207/moving-ibooks-library-to-an-external-drive)) which seem pretty similar to what I'm asking, but I'm looking for more general how-to/best-practice recommendations/gotcha's. I reckon that a naïve approach would be to just drag App.app from /Applications/App.app to EHD/wherever/, but I'm hoping for something less naïve. For what it's worth, my first target for App is XCode -- seems to take up alot of disk space, and I don't use it much, but would like freedom to power it up (over possibly painfully-slow USB) when necessary.

I broke an installation of Deep Freeze on a Macbook by upgrading it to El Capitan. I'd like to get Deep Freeze to work again, but "This version of Deep Freeze cannot be installed on a Mac that has CoreStorage volume". There are many guides to reverting a CoreStorage volume on the internet, but the steps aren't working for me. I open terminal and type "diskutil cs list" and get the list of volumes on the Macbook, the revertible area tells me "Yes (no decryption required)". When I type "diskutil cs revert [logical volume UUID]" I get the error "The given UUID is not a valid CoreStorage Logical Volume UUID. I erased the hard drive and installed El Capitan fresh making sure to uncheck FileVault when I was setting it up, but I'm still getting the same error. Is there another method for disabling CoreStorage on Macbooks that I'm not aware of? Appreciate any help regarding this.

After creating a "DIY Fusion Drive" using the methods below in 10.8, I'm now wondering how to add a RecoveryHD partition to the internal drive. Here's what I did to create a Logical Volume Group across two physical volumes (128G SSD/750GHD) (make a clone / backup of all your data first) diskutil list (take note of the disk## of the two drives. In my case: disk0/disk1) diskutil corestorage create fusion_volume_group disk0 disk1 diskutil corestorage list (take note of the Logical Volume Group UUID) diskutil corestorage createVolume jhfs+ FusionHD 749g restore the clone onto the FusionHD This worked great, but now my RecoveryHD is gone. I'd like to add it back (it's on the external drive I cloned from my original HD) Here's what the partition layout looks like right now: $ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *120.0 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_CoreStorage 119.7 GB disk0s2 3: Apple_Boot Boot OS X 134.2 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *750.2 GB disk1 1: EFI 209.7 MB disk1s1 2: Apple_CoreStorage 749.3 GB disk1s2 3: Apple_Boot Boot OS X 650.0 MB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS FusionHD *744.5 GB disk2 Does anyone know the diskUtil commands to add the recovery HD? Ideally after the fact, which is where I'm at now?

I have an 3TB external HDD with 2 partitions, one of them is 1TB dedicated to time machine (encrypted). It works perfectly, but whenever I unmount the partitions (by using right click, Eject via finder, which offers the option to "Eject All" partitions of this drive). When I plug the drive back in, the non-encrypted non-time-machine partition mounts fine automatically, but not the (encrypted) time machine one. Trying to mount via the Disk Utility app yield the following error: > com.apple.DiskManagement.disenter error -119930868.) Trying to mount via Terminal by running $> diskutil coreStorage unlockVolume GUID first to unlock the drive, then mounting that partition via $> diskutil mount GUID does not work either. Sometimes $> diskutil list will just hand indefinitely, and when this happens even shutting down does not work (I guess macOS is waiting for something). The only workaround I have is too reboot the mac; so that makes me think that it is not an issue with my drive. Note: The disk is not plugged in directly, but through a thunberbolt3 dock (Caldigit TS3+).

I'm new to Time Machine. I just this week got an external hard disk and am starting to use it. My Time Machine backups were spending a significant amount of time in the encryption phase. Upon reading this: https://www.howtogeek.com/305540/how-to-encrypt-your-macs-time-machine-backup/ I thought a better option would be to format the disk as Mac OS Extended (Journaled, Encrypted) instead of the corresponding unencrypted format. If I understand things right I could then do decrypted backups via Time Machine instead of encrypted backups, leaving the encryption up to the OS's writing to the disk via the encrypted file system format. It seems, judging from the question and answers here, that what I'm doing should be reasonable: https://apple.stackexchange.com/q/94930/233542 So I erased my external drive which only had a few days backups anyway and reformatted it as Mac OS Extended (Journaled, Encrypted). But when I added the disk via Time Machine, selected to not encrypt it, and entered my encryption password, I get a message saying this: This Core Storage logical volume is already decrypting. Wait, what? It's decrypting? Why does it need to decrypt anything? The disk is formatted, empty, and ready to fill with data, right? I suppose it doesn't know how full or empty the disk is because the entire disk is encrypted? It has been running, decrypting, for quite a few hours and diskutil cs list shows it as only 12% done: $ diskutil cs list CoreStorage logical volume groups (1 found) | +-- Logical Volume Group XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ========================================================= Name: Status: Online Size: 2000021315584 B (2.0 TB) Free Space: 9392128 B (9.4 MB) | +- Logical Volume Family XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ---------------------------------------------------------- Encryption Type: AES-XTS Encryption Status: Unlocked Conversion Status: Converting (backward) Reversion State: Decrypting High Level Queries: Not Fully Secure | Has Visible Users | Has Volume Key | +-> Logical Volume XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX --------------------------------------------------- Disk: disk3 Status: Online Size (Total): 1999659597824 B (2.0 TB) Conversion Progress: 12% Revertible: No LV Name: WDExternalDrive Volume Name: WDExternalDrive Content Hint: Apple_HFS Note, in particular: Reversion State: Decrypting and: Conversion Progress: 12% Can someone explain to me what is going on? I'm concerned I'm doing something wrong. When it says that it is decrypting, is it decrypting the freshly encrypted drive so that my snapshots will be stored plaintext on the drive? That's clearly not what I want. ----- **Update** After waiting all weekend, the status now shows that the disk conversion process is completed: $ diskutil cs list CoreStorage logical volume groups (1 found) | +-- Logical Volume Group XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ========================================================= Name: WDExternalDrive Status: Online Size: 2000021315584 B (2.0 TB) Free Space: 9392128 B (9.4 MB) | +- Logical Volume Family XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ---------------------------------------------------------- Encryption Type: None | +-> Logical Volume XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX --------------------------------------------------- Disk: disk3 Status: Online Size (Total): 1999659597824 B (2.0 TB) Conversion Progress: Complete Revertible: No LV Name: WDExternalDrive Volume Name: WDExternalDrive Content Hint: Apple_HFS But now Time Machine won't let me use the disk because the volume is not encrypted. Indeed, Disk Utility shows that the format is no longer encrypted: So it looks like I did something wrong, which was my concern that led me to make the post in the first place. Oh well, it was just machine time. Is what I'm doing misguided? Did I miss a step somewhere or take a wrong turn? My question still remains: can someone tell me what is wrong with my process? I want to use the filesystem encyrypted format to backup my machine without Time Machine needing to encrypt the disk as a post process operation. Is this possible?

I get the following error and cannot start Bootcamp after accidentally deleting the EFI-partition of my main drive. >This disk doesn’t contain an EFI system partition. >If you want to start up your computer with this disk or include it in a RAID set, back up your data and partition this disk. Here is my diskutil list result : /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: Apple_HFS 209.7 MB disk0s1 2: Apple_CoreStorage 499.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macbook Pro *498.9 GB disk1 Logical Volume on disk0s2 A6AC962B-74A5-42E8-B84D-B5A7A6325432 Unlocked Encrypted /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: CD_partition_scheme *154.1 MB disk3 1: Apple_partition_scheme 134.2 MB disk3s0 2: Apple_partition_map 1.0 KB disk3s0s1 3: Apple_HFS BOLT! 4G E5372s 8.5 MB disk3s0s2 And here is my sudo gpt -r show disk0 result : start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6 40 409600 1 GPT part - 48465300-0000-11AA-AA11-00306543ECAC 409640 975093952 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC 975503592 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC 976773128 7 976773135 32 Sec GPT table 976773167 1 Sec GPT header The currently installed OS is Yosemite. How do I fix that error?

I wanted to create a partition on my iMac for Windows to be able to play Windows games. I have used Disk Utility to create a 20GB partition on my 1,12TB Fusion drive. This caused a problem on my system. The partition was not created, but my main Macintosh HD drive has all of a sudden 1,09 instead of the 1,12TB available. It seems that my ghost partition has been created, but it is unfindable. When I try to create a new partition I get a direct error telling me that my coreStorage volume has a wrong size, so i'm not able to create a partition. I have searched the web and found some terminal scripts to resize the size of my HD, but this did not work. I have done the following steps: Check the real size of my drive and partitions through terminal *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_CoreStorage Macintosh HD 121.0 GB disk0s2 3: Apple_Boot Boot OS X 134.2 MB disk0s3 /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_CoreStorage Macintosh HD 999.3 GB disk1s2 3: Apple_Boot Recovery HD 650.0 MB disk1s3 /dev/disk2 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh HD +1.1 TB disk2 Logical Volume on disk0s2, disk1s2 4DC798D4-AF57-4F51-A5D2-4B33DE10B887 Unlocked Encrypted Fusion Drive Check more information about coreStorage through *diskutil corestorage list* CoreStorage logical volume groups (1 found) | +-- Logical Volume Group BF423173-90A8-41A7-8DE7-57D77312FCFC ========================================================= Name: Macintosh HD Status: Online Size: 1120333516800 B (1.1 TB) Free Space: 19350335488 B (19.4 GB) | +- Logical Volume Family FE8B314E-1766-4D4A-BCD1-B5ECC9AAF9AD ---------------------------------------------------------- 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 4DC798D4-AF57-4F51-A5D2-4B33DE10B887 --------------------------------------------------- Disk: disk2 Status: Online Size (Total): 1092475813888 B (1.1 TB) Revertible: No LV Name: Macintosh HD Volume Name: Macintosh HD Content Hint: Apple_HFS LVG Type: Fusion, Sparse Try to resize the volume of my drive through *diskutil coreStorage resizeVolume 4DC798D4-AF57-4F51-A5D2-4B33DE10B887 1120333516800b* diskutil coreStorage resizeVolume 4DC798D4-AF57-4F51-A5D2-4B33DE10B887 1120333516800b The Core Storage Logical Volume UUID is 4DC798D4-AF57-4F51-A5D2-4B33DE10B887 Started CoreStorage operation Error: -69674: The provided Core Storage logical volume has an incorrect size; you should run whole-disk repair I have check the drives with "First aid" in Disk utility and everything came back fine, so I think it is only a storage amount issue. Does anyone know how to solve this? and make sure I can restore the full amount of storage on my HD in order to create a new windows partition? Thanks!! System: macOS High Sierra 10.13.6 ~ 21.5" iMac Late 2012 ~ 2.7 GHz Intel Core i5

I bought a new SSD with 750 GB and made two partitions: 600 GB and 150 GB. The smaller one was thought to be a Bootcamp partition one day, but to date it was just another unused partition. When I needed more space, I decided to merge these two partitions. The partition was created with Mavericks, the merge was done with Yosemite. I opened Disk Utility and the "minus" button. Disk Utility told me both partitions would be merged then. However it miserably failed. My main hard disc suddenly had errors which couldn't be repaired and even two of my other external hard discs could not be mounted any longer. I eventually restored the hard disc from Time Machine, which worked well. My second partition is now listed as free: Unfortunately I can't resize the 600 GB partition nor can I create a new partition using the free space. Diskutil reveils the following: ~ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *750.2 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 599.6 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh HD *599.3 GB disk1 Logical Volume on disk0s2 XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX Unencrypted Also diskutil brought up this: ~ diskutil cs list CoreStorage logical volume groups (1 found) | +-- Logical Volume Group 9D2BA4BA-xxxx-xxxx-xxxx-xxxxxxxxxxxx ========================================================= Name: Macintosh HD Status: Online Size: 599640592384 B (599.6 GB) Free Space: 6111232 B (6.1 MB) | +- Logical Volume Family 2FA7892F-xxxx-xxxx-xxxx-xxxxxxxxxxxx ---------------------------------------------------------- Encryption Status: Unlocked Encryption Type: None Conversion Status: NoConversion Conversion Direction: -none- Has Encrypted Extents: No Fully Secure: No Passphrase Required: No | +-> Logical Volume 7BF42B7B-xxxx-xxxx-xxxx-xxxxxxxxxxxx --------------------------------------------------- Disk: disk1 Status: Online Size (Total): 599282155520 B (599.3 GB) Conversion Progress: -none- Revertible: No LV Name: Macintosh HD Volume Name: Macintosh HD Content Hint: Apple_HFS I have tried this: * https://apple.stackexchange.com/questions/148473/reclaim-delete-freespace-partition-after-yosemite-removal * fsck -fy (The volume Macintosh HD appears to be OK.) but it wouldn't help. It said I couldn't recover because it wasn't created in a way it would support (sorry for missing the exact message). I then have learned that Apple_CoreStorage might indicate my disk is encrypted, which might explain why I can't resize it. It doesn't explain why I can't create a new partition to me. What are my options to make my hard disk available in a single partition with size 750 GB?

I'm setting up Time Machine backups on a new external hard disk. I chose to first encrypt the disk via Disk Utility: But I also see these options: **Is there any difference** between an "Encrypted" format via Disk Utility and selecting "Encrypt backups" in the Time Machine preferences? What happens if I do both? Or if I encrypt with Disk Utility, but then *don't* select "Encrypt backups"?

My Disk Utility is showing me some Weird Stuff. My current startup partition is showing as 155 GB, with (I was shocked to discover) 344 GB of unpartitioned free space: I can try to resize the first partition by removing the "Free space" section, then hit "Apply", but then I get this error: Actually, if I try this a few times, I get variously different errors. Sometimes it even says it *succeeds*, but the partition size doesn't seem to have changed. When I retry this same sequence after booting from my recovery partition, basically the same result happens, except that now I have *two* "Free space" partitions, both showing 344 GB, in addition to the 155 GB startup partition. What's going on here, and how can I take advantage of my full 500 GB disk? Or do I not actually *have* a 500 GB disk?? Here's the Disk Utility info for the physical disk - notice that it says it's 500 GB, but the 155 GB partition takes up the whole blue bar: I'm using High Sierra 10.13.6, on a Late 2011 MacBook Pro 13".