Unable to encrypt the Core Storage logical volume

What's going on here?
dmd@lumen ~ $ diskutil cs encryptVolume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
New passphrase for existing volume:
Confirm new passphrase:
Started CoreStorage operation on disk3 megafauna
Scheduling encryption of Core Storage Logical Volume
Error: -69694: Unable to encrypt the Core Storage logical volume
Underlying error: -536870212: Unknown error: -536870212
Here is the relevant volume information:
    +-> Logical Volume Family D556AA79-22D7-49A4-8ADD-8028F0646060
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
            Disk:               disk3
            Status:             Online
            Size (Total):       1149639159808 B (1.1 TB)
            Size (Converted):   -none-
            Revertible:         No
            LV Name:            megafauna
            Volume Name:        megafauna
            Content Hint:       Apple_HFS

Huh. Well, maybe that's why.
It was certainly happy enough to let me MAKE a LVG with multiple LVFs. Do you mean it just doesn't support encryption on a LVG with multiple LVFs?
+-- Logical Volume Group 736244AD-CDF2-4846-9343-2E2A4D487434
    =========================================================
    Name:         seagate1.5TDiskLVG
    Status:       Online
    Size:         1499957936128 B (1.5 TB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume E3B2A090-0BD7-433B-BDEA-7B19174FBAB1
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s2
    |   Status:   Online
    |   Size:     1499957936128 B (1.5 TB)
    |
    +-> Logical Volume Family 55E5E43A-8EC9-4760-8F42-1B4AF17F3184
    |   ----------------------------------------------------------
    |   Encryption Status:       Unlocked
    |   Encryption Type:         AES-XTS
    |   Conversion Status:       Converting
    |   Conversion Direction:    forward
    |   Has Encrypted Extents:   Yes
    |   Fully Secure:            No
    |   Passphrase Required:     Yes
    |   |
    |   +-> Logical Volume E0C47F65-A93B-4C33-B915-F33760A75716
    |       ---------------------------------------------------
    |       Disk:               disk4
    |       Status:             Online
    |       Size (Total):       350000001024 B (350.0 GB)
    |       Size (Converted):   211705397248 B (211.7 GB)
    |       Revertible:         No
    |       LV Name:            bonzai
    |       Volume Name:        bonzai
    |       Content Hint:       Apple_HFS
    |
    +-> Logical Volume Family D556AA79-22D7-49A4-8ADD-8028F0646060
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
            Disk:               disk3
            Status:             Online
            Size (Total):       1149639159808 B (1.1 TB)
            Size (Converted):   -none-
            Revertible:         No
            LV Name:            megafauna
            Volume Name:        megafauna
            Content Hint:       Apple_HFS

Similar Messages

Unable to delete the core storage logical volume

So I get the grey loading bar on the apple logo screen on bootup that get's to the end and then my iMac turns off. This happens everytime. I went into disk utility (CMD-R) and tried to format the partition and get the error message: Unable to delete the core storage logical volume - I should also mention that the OS X partition is greyed out and is marked as having 0GB free (which is false) and I can't select that partition to do a fresh install of OS X on.
I should mention that on my HDD I have a OS X partition and a bootcamp partitiion and this is the second time I have this issue. How can I fix my OS X partition without having reinstall bootcamp as I have 1TB of stuff on it.
Any ideas?

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Yosemite install fails: "not enough free space in the Core Storage Logical Volume Group for this operation"

This is on a Mac Mini, running Mavericks, with a fusion drive (1TB/128GB), and 85GB free space.
Any ideas?

I too experienced the Low Disk space event… I hit the restart button and the install started again… I thought I got caught in a loop.
On the third time seeing the crawl bar for the Yosemite install I hit the Power Button and force killed the whole process.
Upon rebooting I saw horizontal black and white bars across the screen and VERY Slow everything.
Boot, Icon Bounce, Application Launch, Keyboard response… etc.
I was able to get to the Desktop and then I re-installed Yosemite. Dragging a window was laggy, and jerky…
On the third install of Yosemite things improved some, almost but not quite as fast as Mavericks … Some improvement but copy/writes remained very slow.
I now notice that some Applications such as “Clean My Mac” fail to launch and am still finding out if all are functional.
I have a home rolled Fusion Drive.
Currently I am considering a Clean Yosemite install and a TM restore.
Console and Activity Monitor report callservicesd and Chromehelper among others not responding…
I am on hold for the last ten minutes to Apple Support... They must be VERY busy today...

Volume encrypt and erase failed; unable to delete core storage logical volume

I was attempting to slowly migrate [MI-***] from early 2013 MBPRO to New iMac 5K w/Ceiling Level components.
Kept going through LONG process and then told me it couldn't create [MBPRO HD Home Username] "Jim" on volume or whatever. NO FileVault enabling/ still skittish from White iMac Encrypting Nightmare days... I don't even know -- I guess it's encrypted on Airport, but not on MBPRO.
Moved over Applications from outside User account fine; anything inside any User account NOT FINE.
Hooked up Thunderbolt cable between two macs and restarted MBPRO in T mode... displaying the lightning BOLT on screen that moves around to reduce Burn-in.
Was able to go onto desktop and use windows to drag n drop 190G of movies over to iMac... wondering how I was going to get all right settings over form FCP...
Bottom Line: I only have 16G left on MBPRO and need to MOVE video editing to be exclusive on 3T Fusion on Maxed out iMac 5K.
> Have concluded through whole process that I just want to clone the MBPRO and then delete most of the Larger Videos from MBPRO to recover some of my 760G SSD back.
So, I grabbed my 2T Airport Extreme and Hooked up the Cat5 LAN port to Cat5 input on back of NEW iMac; Now my MBPRO doesn't have to be locked up for days, because i can use TimeMachine backup to restore or clone the two macs... i hope.
Went into recovery mode and selected sub-Macintosh HD and attempted to erase; Result time after time after time: "Volume Encrypt and Erase failed." Reason: "Unable to delete the Core Storage logical volume." It dismounts it and I have to restart computer to get it back on. Funny thing is I don't have to use R anymore... which by the way, Command+R appears to be same as just plain old R when restarting... why is that?
This has become a "since Christmas" runaround session for me and I am sick of it.
Please help. I would've called Apple Care [and I did last night while driving... just to get advice on direction. I'm usually a pretty savvy PowerUser but this is driving me crazy.] but have to get things done for a meeting tomorrow. Can work on it after hours if someone can advise today on this post.
Thx,
Jim

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Error: -69774: Couldn't bring the new Core Storage Logical Volume online

Hi,
I have a filevault encrypted drive (750GB).
I first noticed a problem when it prompted my for the FileVault passphrase (which I had stored in my keychain) and entering the correct passphrase resulted in the typical "error" response (the sideways "bouncing" entry field) asking me for the passphrase again.
So I get a list of the corestorage to get the UUID of the encrypted volume:
>diskutil corestorage list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group ********-****-****-****-************
    =========================================================
    Name:         750GB APPLE HDD
    Status:       Online
    Size:         749812400128 B (749.8 GB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume ********-****-****-****-************
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s2
    |   Status:   Online
    |   Size:     749812400128 B (749.8 GB)
    |
    +-> Logical Volume Family ********-****-****-****-************
        Encryption Status:       Locked
        Encryption Type:         AES-XTS
        Conversion Status:       Complete
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            Yes
        Passphrase Required:     Yes
        |
        +-> Logical Volume ********-****-****-****-************
            Disk:                  -none-
            Status:                Locked
            Size (Total):          749493624832 B (749.5 GB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               750GB APPLE HDD
            Content Hint:          Apple_HFS
Using command line I get the following response:
>diskutil corestorage unlockvolume UUID -stdinpassphrase
{UUID being the one of the last Logical Volume named "750GB APPLE HDD"}
Passphrase:
Started CoreStorage operation
Logical Volume successfully unlocked
Error: -69774: Couldn't bring the new Core Storage Logical Volume online
next I try:
>diskutil corestorage revert UUID -stdinpassphrase
Passphrase:
Started CoreStorage operation on disk3
Error: -69741: The target disk isn't eligible for reversion because it wasn't created by conversion or it is not part of a simple setup of exactly one logical and one physical volume
and then:
>diskutil corestorage unlockvolume UUID -stdinpassphrase
Passphrase:
Error beginning CoreStorage Logical Volume unlock: The target Core Storage volume is not locked (-69748)
looking at the kernel log I see the following interesting entries:
08.12.13 15:32:47,000 kernel[0]: CoreStorage: fsck_cs has finished for group "UUID" with status 0x00
08.12.13 15:32:47,000 kernel[0]: CoreStorageFamily::unlockVEKs() failed to unwrap the vek, status = e00002bc
08.12.13 15:33:10,000 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "750GB APPLE HDD" (UUID), pv UUID-of-Physical-Volume, near LV byte offset = 0.
08.12.13 15:34:51,000 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002d9 detected for LVG "750GB APPLE HDD" (UUID), pv UUID-of-Physical-Volume, near LV byte offset = 0.
BTW: after a while I also hear a single clicking sound (head jumping back on drive) so I am not sure if it might be a physical disk failure.
Any ideas anyone?

Also, I've tried Terminal command: diskutil corestorage revert UUID -stdinpassphrase which returned "Error: -69854: A disk with a mount point is required"
Also, I've tried Terminal command: diskutil corestorage changeVolumePassword UUID -newpassphrase which returned "Error beginning CoreStorage Logical Volume unlock: The target Core Storage volume is not encrypted (-69755)"

-69774: Couldn't bring the new Core Storage Logical Volume online.....What Now?

Hey,
I'll start from the begining.
I have a 1TB that was running Mavericks, which I decided to perform Firevault 2. Anyway my hard drive crashed and now I have Mavericks running on a different 250 gig hard drive and have been trying to decrypt my original 1tb harddrive through terminal.
So I originally did the "diskutil corestorage unlockVolume UUID -stdinpassphrase thing and it said that it could not mount it but I notice that it was converting. So after 6 hours the converting stopped and now it says that decyrption is no longer neccessary and that it needs to be reverted. So I am try to revert it with terminal and it tells me that it is unable to find mount point. So ive been trying to mount the disk and comes up with the above error -69774: Couldn't bring the new Core Storage Logical Volume online. So does anybody have any suggestions??
-Thank you

To anybody that read this and has the same sort of problem:
I just recovered my stuff using stellar pheonix Mac Data Recovery, even after I coundnt mount it on my other mac machine. Great software.

FileVault Failed: Unable to create a new Core Storage logical volume group.

So when I try to enable FileVault on my Retina MBP, I go through all the steps and hit restart.
The program then hangs for about 30 seconds and gives me the above error.
It never restarts and never turns on FileVault.
Any ideas?

Triple-click anywhere in the line below to select it:
diskutil list; echo; diskutil cs list
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste (command-V) into the Terminal window.
Post any lines of output that appear below what you entered — the text, please, not a screenshot.

Partition failed: A problem occurred while resizing Core Storage physical volume structures

Hi everybody,
I have just installed Yosemite on my iMac and everything works right.
iMac 27" late 2012
3,4 Ghz intel core i7
32 GB 1600 Mhz DDR3
3TB Fusion drive.
Now I need to create a bootable partition to install a copy of Mavericks because some FCPX plugins do not work on Yosemite.
To create a new partition I use Disc Utility, but each time I try to create it the mac show me this error:
partition failed A problem occurred while resizing Core Storage physical volume structures
Why?
What can I do?
P.S. FCPX does not work on a virtual machine, so I have to install it on a new partition
Thanks

Ditto here.
Same problem - I have a Apple_Corestorage partition that can't be unlocked.
You have to do this command to free up the Corestorage partition
diskutil coreStorage delete logicalGroupUUID
In your case, it'll be:
diskutil coreStorage delete E2CDC5FC-DA6E-4F43-B524-8925ABB23883

Hi I'm getting Lightoom error when trying to edit in Nik Software "Lightroom was unable to prepare the selected file at /Volumes/Portable C/Kite Skating nikon/_DHT9654.NEF for editing. It will not be opened.

Lightroom was unable to prepare the selected file at
/Volumes/Portable C/Kite Skating nikon/_DHT9654.NEF for editing.
It will not be opened.
what does this mean? can anyone help?

Yes it is on a portable drive yet I have already worked with it and exported it as a jpg. The problem arises whenever I try to edit in the plug-ins from Nik software...this just happened recently as it never happened before...for years?

Unable to delete the files from CSV volumes on HyperV Cluster

Hello There,
I have a HyperV failover cluster with CSV Volumes recently i moved some of the VMs to another cluster.
VMs are moved but i still have the VM files on the CSV volumes which are occupying the disk space i tried to delete the VHD files / VM folders which are moved but it doesn't delete the files, please suggest.
This file when i browse it from a server and delete the file it disappears but when i revisit the folder i find the files still on the disk, i did try to delete the files directly
from the server through command line as it is running server core.
Regards,
Maqsood
Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

HyperV is good about not allowing you to delete files while they are still in use. You can try to reboot host, make sure all parts if your VM moved to the new location. If that VHD is associated with a VM on any host you will not be able to delete
it. Delete the VM's that may have links to it. Not knowing you configuration could it be a parent disk? Be carful because if you can't delete it it's likely in use, I've see VHD merge after you delete a VM too preventing you from deleting the files.
You may just want to wait a day or so and see if it free's up. If it is doing a merge reboot will pause and restart it so you won't be able to remove until the merge is done, once you delete a VM and a merge starts there is no way to tell if it's merging,
watch the size and timestamp of the VHD is it changing if it is something is using it.

Critical error 3.0 :unable to start the core engine, The application cannot continue.

Mentre usavo sony vegas pro 11 lo schermo del PC è diventato nero e poi e tornato normale ed è venuta la scritta driver grafico ripristinato e poi il PC si è riavviato e ora mi da lo schermo nero e si vede solo il puntatore del mouse per favore potete aiutarmi.
Mi è già successo a gennaio che poi ho formattato il PC e rimesso tutto ed è tornato normale ma non posso sempre formattare il PC .

Ho un PC compaq presario cq60- 300sl

Core storage is unable to begin volume reversion

Hello there.
I have an external hard drive, and in finder I right clikced it to encrypt it.
Now I am trying to decrpyt it by opening it up in finder and its gives me Core Storage is unable to begin volume reversion error or sometimes : Unable to decrypt the Core Storage logical volume
I tried decrypting it in finder, in disk utlities, I tried earsing the hd completly, and multiple restarts on my computer.
My hd is pretty much useless at this point. I cannot view my content stored on that drive, copy or paste anything on and to that drive. It takes a long time for the content to load into the drive also before I can see it.
Does anyone have a solution for this?

I also have the same issue. In my case the system hangs during normal login, and stays there forever in about 40% of login progress. I am not able to access any file, or do anthing in the Mac Book pro.
I have Yosemite 10.10.2 installed.
I went into safemode and tried to turn off filevault, in attempts of fixing the hang. But I get "Core Storage is unable to begin volume reversion". Anyone any ideas on how to fix this and turn off filevault successfully?

Can't remove Core Storage from hard drive

I wanted to erase a backup drive and start over again but somehow it's gotten converted to "Core Storage" I'm told.
I managed to erase the drive by first listing the Core Storage devices, using the following command in the OSX Terminal:
diskutil cs list
Then erasing the drive:
diskutil cs delete "Backup2"
This made everything look OK in Disk Utility, because now the drive appears as having a volume in addition to the drive icon, and there are also 4 tabs available (First Aid, Erase, Partition, RAID, Restore), but if I erase the drive something strange happens: it says "Switching disk1s1 to Core Storage", and after that the two drive icons in Disk Utility get the same name (all my other drives show an icon with the drive brand/model while the second icon shows the volume name). And the main drive icon only has 2 options now: First Aid and Partition. The volume icon has 3 options in DIsk Utility: First Aid, Erase, Restore.
The obvious thing to do at this stage is select "Erase", but this only results in the volume icon changing its name separately from the drive itself.
I've also tried booting with my OSX 10.6 installation DVD and erasing the drive from there, but the result is the same when I try to erase it once again. Seems like my OSX has somehow decided that this specific drive must be a Core Storage device regardless of what I've done to the actual drive itself.
What do I need to do in order to make the drive "normal" again? I'm using OSX 10.9.5.

Kappy: thanks, but I have to explain that I'm not in the process of upgrading from OSX 10.6 Snow Leopard (I grabbed the OSX 10.6 installation DVD because it allows me to boot from another media than the computer's boot drive -Mavericks doesn't come on a DVD of course and I haven't taken the time to figure out how to install it on a USB thumb drive).
I actually did a clean install (backup everything, reformat the drive, install OSX from scratch) of OSX 10.9 Mavericks recently, and the reason for reformatting the problematic drive in the first place was to do a completely new backup since I don't want to risk keeping keep bits of 10.6 mixed in there with 10.9.
I somehow messed up the drive which made it Core Storage and now it refuses to act as a normal drive.
My Mac consists of several drives where the abovementioned drive acts as a bootable backup.
Keg55: Thanks for your suggestions but I'm still running into the same issue as before: after doing the terminal commands my drive seems fine, but when I open Disk Utility (DU) and format ("erase") the drive gets converted back into Core Storage. I erase it in order to test if things have really gotten back to normal or if the Core Storage thingy still sticks with my system somehow (which it does). I'd never even heard of Core Storage until now (and still don't understand what it really is as most of the documentation I've found is highly technical), but could it be that OSX 10.9 Mavericks is supposed to do this while 10.6 Snow Leopard isn't (hence what Kappy is saying in the last part of the reply above about Yosemite creating Core Storage volumes automatically? Is this what applies here, or have I misunderstood?
OK, let me explain what happens step by step... The goal of course is to format the drive so as to act as a normal "Mac OS extended (journaled)" drive (as I said I don't even know what Core Storage is and don't know why I would be wanting this), so here goes....
1) At the first stage I have the drive freshly deleted using the diskutil cs delete LVG_UUID command (diskutil cs delete "volume_group_name" appears to be doing the same thing), so it's just like my other drives as far as I can see in DU (showing the drive brand/model and a partition icon underneath as seen in the screenshot below).
2) Now I want to verify if my drive has really become "normal" again or if it acts up once more by becoming a Core Storage drive again.
I click on the drive's (not its partition) icon in DU, select the "Erase" tab and finally press the erase button.
3) After pressing the erase button, messages pop up at the bottom part of DU very quickly. Luckily I can do screenshots faster than I can read, so here's what I've captured DU telling me. First it's converting the drive to Core Storage:
4) next it switching the drive to Core storage:
5) and finally it's formatting the file system for logical volume (whatever that means):
and as you can see in the top left corner the drive now only shows a single icon (unlike every time I've formatted a drive in the past it shows the drive and a partition icon, where the drive icon is followed by the drive's brand/model name).
So what's going on here and why can't I get my drive back to normal when erasing it?

Yosemite "problem resizing Core Storage" upgrade error?

Not a great amount of luck upgrading from Mavericks to Yosemite here.
Download and start install, restart, see the progress bar, then the install screen with "about 18 minutes remaining". It moves along, and then boom...
OS X could not be installed on your computer
A problem occurred while resizing Core Storage physical volume structures.
Quit the installer to restart your computer and try again.
Restarting several times, as well as returning to Mavericks and trying again has so far failed. Live Chat suggestions of verifying and repairing disks and trying in Safe Mode also unsuccessful.
3TB Fusion Drive has over 450GB free space, just the single "iMac" partition within the Macintosh HD.
Any help greatly appreciated! Otherwise looks like it's a wait to see if a fix appears...
iMac 27-inch, Late 2012
3TB Fusion Drive
3.4GHz Intel Core i7
16GB Memory

http://de.wikipedia.org/wiki/Fusion_Drive
Fusion Drive is a technology developed by Apple Computer Engineering, with a SSD and a mechanical hard drive be connected to a logical drive. [1]
Description and function [Edit]
Fusion Drive called Apple a technique in which an SSD and a mechanical hard disk are transparently connected to a logical drive. The user sees the combination as a single drive. [2] With Fusion Drive is also in large storage volume can be benefited at a moderate price of the speed of the SSD.
Fusion Drive connects not only two physical drives into one logical, but still used in addition to a technology that tiering is called. When tiering, in German as "staggering", data on frequently accessed, the fastest drive (SSD here) saved, the other to the slower, here on the mechanical drive. What data is stored where, the operating system decides on the basis of a thorough analysis of the data access itself and can not be influenced by the user. Optionally coated the operating system in the background to data. The operating system itself is always on the SSD. [3] [4] tiering is used in mainframe computers for some time, with Fusion Drive this technology now comes for the first time in a personal computer for use.
Fusion Drive must not be confused with conventional hybrid drives. While in the latter case the SSD part only serves as a data buffer and all data is ultimately always stored on the mechanical disk in Fusion Drive SSD is a full-fledged part of the logical drive (except a small part of 4 GB [3], which also serves as a buffer).
Fusion Drive is since November 2012 integrated with all new Macs with SSD and mechanical hard drive. [5] The first corresponding Macs were equipped with a 128 GB SSD and a 1 TB or 3 TB of mechanical hard disk. [6] Currently (April 2013 ), Apple provides no utility available with which Fusion Drive install on older Macs could. But this can be done via the terminal, this requirement is OS X 10.8 Lion Mountain. [7]

HT2434 Logical Volume - should show (locked) in sys. profile?

I recently confirmed the GUID partition scheme- did a wipe, a re-install. I have to enter a disk password, then the passord for the account.
Logical Volume:
Revertible:          No
Encrypted:          Yes
Encryption Type:          AES-XTS
Locked:          No   [ is this right? ]
LV UUID: ----
Still showing the old (original?)
Logical Volume Group:
Name:          7TH COMPANY
Size:          119.17 GB (119,174,365,184 bytes)
Free Space:          Zero KB
LVG UUID: -----
Hope that my SSD is working properly - that as well as the DISK UTILITY ? Although, I am not a expert user either!!

It's not clear what the problem is. "Locked: No" means that the volume encryption key is cached in memory.

Unable to encrypt the Core Storage logical volume

Similar Messages

Maybe you are looking for