Mavericks FileVault 2 Issue - Logical Volume Disappeared

I have a drive out of a damaged, late 2011 MacBook Pro that was FV2 encrypted.  I have the password and key and used them to decrypt the drive to recover data.  This was done from Disk Utility and appeared to be successful until I rebooted.  This was done firewire connected to my 2011 MacBook Pro running Mavericks.  The end result is the drive appearing in RED/inaccessible in disk utility and in the running "diskutil cs list" shows the Logical Volume Group "offline" and the Physical Volume "online".  Oddly the Logical Volume itself is gone.  Below is some output from some diskutil commands:
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         499.2 GB   disk1s2
   3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group FD6BEF04-E4EB-48F1-9E4C-5911245D0273
    =========================================================
    Name:         Macintosh HD
    Status:       Offline
    Size:         499248103424 B (499.2 GB)
    Free Space:   498929328128 B (498.9 GB)
    |
    +-< Physical Volume 2BDA1A0F-4404-43F1-B183-D4DB23FBF669
        Index:    0
        Disk:     disk1s2
        Status:   Online
        Size:     499248103424 B (499.2 GB)
Any ideas or guidance on recovering data from this drive would be greatly appreciated.
Thank you

I'm having a similar problem with FireVault and a USB drive. I formatted and encrypted a USB drive using Disk Utility. I set the password and saved it on my home computer's keychain. Now I'm having problems with FV recognizing the password on other computers.
This morning I mounted the drive and entered the PW with no problem on a computer. I ejected the disk and later remounted it on the same computer. When I was prompted to enter the password, FV paused and grayed out for about 30 sec then rejected the password. If I do the same thing and enter any other password, it is rejected immediately. Not sure what is going on. I've tried it on several computers and it does the same thing with the password.
I can probably reset the password on my home computer, but worried this will be an ongoing issue. Any advice? Has anyone else encountered this?
thanks
Adam

Similar Messages

  • Harddisk appears as logical volume in maverick

    Hi
    After Cloning my OSX Maverick to another Mac (MacPro 2009) I see most of my hard disks, also absolutely new ones (fresh from the package) as logical volumes in the disk utility. I am not so free to partition them as I want for instance.
    I tried the terminal procedure which Linc Davis recommended in another post (sudo diskutil cs ...), it worked, but after a restart I had my hard disks again only visible as logical in disk utility.
    Puh!
    Thanks for Your help
    David

    This is what you do to change "New Volume" back to "Mary's iPod". When "New Volume" is connected to your computer, double click on it. The cursor should appears, you should be able to backspace on your keyboard, erase "New Volume" and type in "Mary's iPod" and then press "Enter".

  • Disk Utility formats Hard Drives as Logical Volume Group

    I just replaced a hard drive which had died in my Mac Pro which has OS X 10.9.5. To format the new 3TB hard drive I went to Disk Utility. I used "Erase" in its fastest form and the drive was formatted with the Type: Logical Volume Group.
    I remember this was a problem a few years ago when I first put hard drives in this computer. I think it was considered a bug in the Disk Utility in OS X 10.8 that it would automatically format drives greater than 2 TB as Logical Volume Group. The solution for me was to restart the computer with my OS X 10.6 disk and use the Disk Utility in that to reformat the drive. I never really understood why Logical Volume Group was a problem but I just obeyed what the wise ones of the Internet had to say.
    So, now I am wondering if I should reformat my new Hard Drive as GUID using my OS X 10.6 optical disk again? If it was a bug in the Disk Utility of OS X 10.8 then why is it not fixed in the Disk Utility of OS X 10.9? Is there an actual problem with having disks format formatted as Logical Volume Group? Is this now just Apple's way of doing things?
    Thank you.

    keg55 wrote:
    You could do your reformat using your 10.6 DVD. That's a decision that's up to you.
    Not every bug in a previous OS gets fixed in a new OS.
    I don't believe CoreStorage (Logical Volume Group) causes any sort of issues. Whenever one encrypts their Macintosh HD, the format is converted to CoreStorage. Fusion Drives are using CoreStorage and now Yosemite converts portables (laptops) to CoreStorage during the install process. As far as Yosemite is concerned, Apple seems to have gone the route of CoreStorage for portables. Even during the Setup on a portable, FileVault is offered with the default of YES being checked. So, if a customer isn't paying attention and continues with the install, they could encrypt their drive without knowing to uncheck the default checkbox.
    Thank you for your reply.
    I have decided to reformat my new hard drive using my 10.6 disk. I like being able to split it up into more than one volume if need be.
    I understand that not every bug in a previous OS gets fixed, but this strikes me as being really a very large bug, so I think it would be good if Apple addressed it.
    It is useful to know about Yosemite's behaviour. When I upgrade to Yosemite I will be a bit more prepared. In fact my MacBook Pro has FileVault on with Mavericks so Yosemite won't change anything there.

  • 3TB Fusion & logical volume group

    I'm in the process of fully reinstalling Mavericks - erasing my internal drive and paring my system way down, to resolve some long lingering issues.
    Disk Utility shows the recovery partition as separate (I've booted from it) - but when I went to erase the default Macintosh HD partition I was unable to repartition it as a single partition - it was grayed out - and the TYPE was/is logical volume group - where I was expecting to see GUID.   All I could do at that point was ERASE... which I did - so it remains a logical volume group -
    I'm unsure if, because of the Fusion drive, this is how they come from Apple - or the previous owner messed with it and trouble could loom wth this setup.
    It's a Late 2012 iMac with stock 3TB Fusion Drive.
    I'm in the process of reinstalling Mavericks from the Recovery (Internet recovery I'm guessing since it's taking 2 hours).  I'm not near an Apple Store unfortunately though do have extended 3 year warranty.
    Is it OK to leave the main Macintosh HD as "logical volume group"?????

    Yes. That's the technical name for what Apple marketing refers to as a "Fusion Drive." Don't change it.

  • OSX Yosemite Logical Volume Group - FIX!

    Hey guys,
    For anyone wondering or concerned about why, when entering Disk Utility, the SSD name has been changed and you now see Macintosh HD and Macintosh HD below. The one above is listed as a Logical Volume Group with an "online" status while the one below that is your physical HDD (so normal as with previous OS's.
    I must note that I do not have any recovery partition when holding option when booting (after installing straight onto Mavericks, nor when making my own bootable copy).
    However, I did find a way to fix the Hard Drive name issue and revert it back to original format (I did find this fix online, and it has worked for me).
    I included pictures below as well.
    First one shows original Yosemite SSD name change (from Apple SSD to Macintosh HD with 18.9MB available)
    Second shows your normal HHD name unchanged.
    Go to Terminal and enter the following:
    diskutil cs list
    then you will see a bunch of volumes jump up
    enter: diskutil cs revert "UUID"
    under "UUID", enter the the Logical Volume code number without brackets.
    Do not copy and paste it from terminal into your new terminal line. Write it out.
    Hit enter and it will ask to reboot your Mac.
    Once, rebooted, your old SSD/HDD name with reappear as in Mavericks.
    My entire terminal line is shown in the picture attached.
    Either way (SSD name changed or reverted) did not changed how the system performed. Everything is running as it should.
    Final result shown in last picture!
    Hopefully this is just a bug that Apple will fix.
    Please ignore the DiskMaker drive (I was making a bootable copy on my external!!)

    Thanks for the tip. I see its a common trouble. But i stuck a problem that cannot be solved with this method cause i dont have revertable logic volume.
    SO i cannot install system now. There's  no visible disk any more.

  • Logical Volume Group.

    My 1TB SSD main drive on my MBP Retina volume has changed to Logical Volume Group and the Partition is named Logical Partition.  Now it works fine but was wondering why it has changed from Mac OS Extended (Journaled).  If I want to partition the drive, it is grayed out with no options.  I'm not pleased that I can't control my own drive.  Any answers?

    FileVault is not activated, although it was at one point.  I deleted the partition and...
    I believe that may have caused the problem when I attempted to load the operating system on a new partition from the drive.  I deleted it and thought I reformatted it to Mac OS Extended, but I had major issues because it was locked at one point.  Just recently, I restored to a TM backup which should have formatted the drive correctly but this is what I ended up with.  Like I said, the option is grayed out now.
    Gary

  • Error message when installing Yosemite OS: this core storage operation is not allowed on a sparse logical volume group

    I was updating my Macbook Air (i7, 4mb RAM, 256 gb) to Yosemite OS when the process was interrupted. After retry, my computer is showing the following message: "this core storage operation is not allowed on a sparse logical volume group". I tried to restart several times, but the problem goes on with error. It would be my computer damaged?

    If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
    In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
    Then, from the menu bar, select
              File ▹ Turn Off Encryption
    Enter the password again.
    You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
    If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
              Mac OS Extended (Journaled)
    from the Format menu.
    You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
    Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

  • 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.

  • Failed to revert logical volume group while merging partition

    Hi All,
    Previously, on my macbook pro, I partitioned my disk for win7 for my dual operation system and only left 120 GB for OS, now I want to delete win7 and return disk space to OS. Currently my OS is yosemite.
    I have already deleted disk space for win7 and merged it back to disk0s3. And, I had a problem to merge disk0s2 with disk0s3.
    I was told it is because I need to revet my Logical Volume Group. I am blocked at reverting it.
    This is my disk info:
    rescomp-14-251133:~ rico$ diskutil list; diskutil  cs list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage                         119.3 GB   disk0s2
       3:                  Apple_HFS Recovery HD             380.6 GB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *119.0 GB   disk1
                                     Logical Volume on disk0s2
                                     CC457129-6FE9-41A0-B0D2-F547F21A7555
                                     Unencrypted
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group F454017F-C531-43BA-B270-E2058E05BFF4
        =========================================================
        Name:         Macintosh HD
        Status:       Online
        Size:         119290187776 B (119.3 GB)
        Free Space:   4096 B (4.1 KB)
        |
        +-< Physical Volume AC7A2748-0DA1-49D6-B50C-30348838760E
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     119290187776 B (119.3 GB)
        |
        +-> Logical Volume Family 4B7E6277-69BC-475A-BBB7-7A94D6434D9E
            Encryption Status:       Unlocked
            Encryption Type:         AES-XTS
            Conversion Status:       Converting
            Conversion Direction:    -none-
            Has Encrypted Extents:   Yes
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume CC457129-6FE9-41A0-B0D2-F547F21A7555
                Disk:                  disk1
                Status:                Online
                Size (Total):          118954639360 B (119.0 GB)
                Conversion Progress:   -none-
                Revertible:            Yes (unlock and decryption required)
                LV Name:               Macintosh HD
                Volume Name:           Macintosh HD
                Content Hint:          Apple_HFS
    when I type unlock:
    rescomp-14-251133:~ rico$ diskutil corestorage unlockVolume CC457129-6FE9-41A0-B0D2-F547F21A7555 -stdinpassphrase
    CC457129-6FE9-41A0-B0D2-F547F21A7555 is already unlocked and is attached as disk1
    It is already unlocked
    then, I tried revert it
    rescomp-14-251133:~ rico$ diskutil coreStorage revert CC457129-6FE9-41A0-B0D2-F547F21A7555
    Passphrase:
    Started CoreStorage operation on disk1 Macintosh HD
    Error: -69750: Unable to modify a FileVault context
    Does anyone how I can revert it, then merge disk0s2 and disk0s3

    Here is another try via the command line:
    dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
    Started CoreStorage operation
    Checking file system
    Performing live verification
    Checking Journaled HFS Plus volume
    Checking extents overflow file
    Checking catalog file
    Incorrect block count for file 2012.12.11.asl
    (It should be 390 instead of 195)
    Checking multi-linked files
    Checking catalog hierarchy
    Checking extended attributes file
    Checking volume bitmap
    Checking volume information
    Invalid volume free block count
    (It should be 21713521 instead of 21713716)
    The volume MAC OS X was found corrupt and needs to be repaired
    Error: -69845: File system verify or repair failed

  • How Will Yosemite Logical Volume Group Affect Two-Partition Drive?

    After installing Yosemite, my Macintosh HD became a Logical Volume Group. Now, in Disk Utility, both the Drive and the Volume have the same name — Macintosh HD. I want to use one of two partitions on an extra internal drive in my Mac Pro (Mid 2010) as a bootable clone of my Yosemite startup drive, using SuperDuper!. When cloning is complete, will my spare drive become a Logical Volume Group with a renamed drive? Will that effect the other partition, which is a bootable Mavericks clone?

    Thanks for the tip. I see its a common trouble. But i stuck a problem that cannot be solved with this method cause i dont have revertable logic volume.
    SO i cannot install system now. There's  no visible disk any more.

  • 10g ASM on Logical Volumes vs. Raw devices and SAN Virtualization

    We are looking at setting up our standards for Oracle 10g non-rac systems. We are looking at the value of Oracle ASM in our environment.
    As per the official Oracle documentation, raw devices are preferred to using Logical Volumes when using ASM.
    From here: http://download.oracle.com/docs/cd/B19306_01/server.102/b15658/appa_aix.htm#sthr
    ef723
    "Note: Do not add logical volumes to Automatic Storage Management disk groups. Automatic Storage Management works best when you add raw disk devices to disk groups. If you are using Automatic Storage Management, then do not use LVM for striping. Automatic Storage Management implements striping and mirroring."
    Also, as per Metalink note 452924.1:
    "10) Avoid using a Logical Volume Manager (LVM) because an LVM would be redundant."
    The issue is: if we use raw disk devices presented to ASM, the disks don't show up as used in the unix/AIX system tools (i.e. smit, lspv, etc.). Hence, when looking for raw devices on the system to add to filesystems/volume groups/etc., it's highly possible that a UNIX admin will grab a raw device that is already in use by Oracle ASM.
    Additionally, we are using a an IBM DS8300 SAN with IBM SAN Volume Controller (SVC) in front of it. Hence, we already have storage virtualization and I/O balancing at the SAN/hardware level.
    I'm looking for a little clarification to the following questions, as my understanding of their responses seem to confict:
    QUESTION #1: Can anyone clarify/provide additional detail as to why Logical volumes are not preferred when using Oracle ASM? Does the argument still hold in a SAN Virtualized environment?
    QUESTION #2: Does virtualization at the software level (ASM) make sense in our environment? As we already have I/O balancing provided at the hardware level via our SVC, what do we gain by adding yet another level of I/O balancing at the ASM level? Or as in the
    arguments the Oracle documentation makes against using Lvm, is this an unnecessary redundant striping (double-striped or in our case triple-striped/plaid)?
    QUESTION #3: So does SAN Virtualization conflict or compliment the virtualization provided by ASM?

    After more research/discussions/SR's, I've come to the following conclusion.
    Basically, in an intelligent storage environment (i.e. SVC), you're not getting a 100% bang for the buck by using ASM. Which is the cat's meow in a commodity hardware/unintelligent storage environment.
    Using ASM in a SVC environment potentially wastes CPU cycles having ASM balance i/o that is already balanced on the backend (sure if you shuffle a deck of cards that are already shuffled you're not doing any harm, but if they're already shuffled - then why are you shuffling them again??).
    That being said, there may still be some value for using ASM from the standpoint of storage management for multiple instances on a server. For example, one could better minimize space wastage by being able to share a "pool" of storage between mulitiple instances, rather than having to manage space on an instance-by-instance (or filesystem by filesystem) level.
    Also, in the case of having a unfriendly OS where one is unable to dynamically grow a filesystem (i.e. database outage required), there would be a definite benefit provided by ASM in being able to dynamically allocate disks to the "pool". Of course, with most higher-end end systems, dynamic filesystem growth is pretty much a given.
    In the case of RAC, regardless of the backend, ASM with raw is a no-brainer.
    In the case of a standalone instance, it's a judgement call. My vote in the case of intelligent storage where one could dynamically grow filesystems, would be to keep ASM out of the picture.
    Your vote may be different....just make sure you're putting in a solution to a problem and not a solution that's looking for a problem(s).
    And there's the whole culture of IT thing as well (i.e. do your storage guys know what you're doing and vice versa).....which can destroy any technological solution, regardless of how great it is.

  • SE3511 - recovering logical volumes

    Hi ,
    I have a SE3511 array with one controller array and a JBOD both are fully populated with 400GB disks. There is one each logical drives(RAID5) configured on both controller array and JBOD. Each logical drives were divided into two logical volumes of equal size. SO I had 4 logical volumes total. After doing a physical move of the array to different location, I had some problems witht the array. When I checked the configuration, i could see all the logical volumes are disappeared, but still the logical drives are there. Unfortunately I didn't take a configuration backp of the styorage. But I know the size of the logical volumes.
    Can any body help how to recover the lost logical volumes or create the logical volumes without losing data.
    Thanks
    Babu

    Found the following:-
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ls.htm#sthref1308
    Oracle® Data Guard Concepts and Administration
    10g Release 2 (10.2)
    Part Number B14239-04
    Managing A Logical Standby Database -- 9.5.4
    Indicates that the Logical Standby can recover through an OPEN RESETLOGS if its running in flashback database mode.
    Not sure what the impact of this is on non-guarded components - could be that if it flashes the logical back too that it loses all the non-guarded components

  • Logical Volumes Not Creating w lvcreate? Install??

    After following the arch raid guide i have gotten all tge way down to creating logical volumes and i get  this
    lvcreate -L 20G VolGroupArray -n lvroot
    /dev/VolGroupArray/lvroot: not found: device not cleared
      Aborting. Failed to wipe start of new LV.
      device-mapper: remove ioctl on  failed: Device or resource busy
    here is vgdisplay
    -- Volume group ---
      VG Name               VolGroupArray
      System ID             
      Format                lvm2
      Metadata Areas        1
      Metadata Sequence No  17
      VG Access             read/write
      VG Status             resizable
      MAX LV                0
      Cur LV                0
      Open LV               0
      Max PV                0
      Cur PV                1
      Act PV                1
      VG Size               97.75 GiB
      PE Size               4.00 MiB
      Total PE              25024
      Alloc PE / Size       0 / 0   
      Free  PE / Size       25024 / 97.75 GiB
      VG UUID               rP0ooH-VdCy-fMZM-sB0g-90zi-Gv2o-gBZWC1
    pls help i am now stuck

    mattbarszcz wrote:So I went back to the live cd, I ran efibootmgr with no arguments, and sure enough there was only 1 entry for the Windows Boot Manager.  It seems that efibootmgr commands don't seem to take effect.
    Because of bugs in efibootmgr and/or EFI implementations, efibootmgr doesn't always work. Using bcfg from an EFI shell or bcdedit in Windows can be more effective on some systems. That said, if efibootmgr worked for you before, I'm not sure why it would stop working, or why an existing entry might disappear. (Some EFIs do delete entries that they detect are no longer valid. This shouldn't have happened with a whole-disk dd copy, but if you duplicated the partition table and then used dd to copy partitions, it might well have happened to you. I suppose it's conceivable that the firmware detected the change from one physical disk to another, too, and deleted the original entry because of that change.)
    I referenced the rEFInd page here: http://www.rodsbooks.com/refind/installing.html#windows and followed the procedure to install an entry for rEFInd from Windows.  I was able to add an entry no problem through windows.
    Does anyone have any suggestions as to why this doesn't work?  Nothing has changed about the system other than the disk.
    It's unclear from your post whether the entry you created in Windows now works. If it does, then don't sweat it; just keep using that entry, and if you need to make changes and efibootmgr doesn't work in the future, plan to use either Windows or the bcfg command from an EFI version 2 shell.

  • 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.

Maybe you are looking for

  • Import/Rip using more than one CD/DVD drive at the same time.

    I have two DVD/CD dual layer readers/burners and would like to be able to import audio CDs into iTunes from both drives at the same time. Is this supported? If so, how do I do it? If not, is it planned for future releases? Thanks in advance! AMD 3500

  • Certain PDF documents not spotlight-indexed nor copy/paste to TextEdit

    Hello, I've got a problem with certain PDF documents and Preview.app. I can read them perfectly by eye (I understand there's an overlying image?) but the text characters, when copied and pasted into TextEdit, are little rectangles with a tiny alien f

  • Mail completely deleted

    Hello, Several days ago I went online and clicked the Mail stamp icon, only to active a dialogue box indicating a problem with accessing my email, which unfortunately I didn't read thoroughly. There was some indication that activating the Mail would

  • Hyperlink box is not active when attempting to link text to a webpage

    In Numbers Application, I attempted to link text in a box to a web page. The Inspector box for Hyperlinks was not active. It also was not active when I attempted the same through Insert Suggestions?

  • Recording google hangouts

    IOS7 while in a google hangout I go to another screen --in the top of the other screen I see "recording google hangout" just where is that recordng and how do I stop this from recording my hangouts? I think this is an iOS issue not an option in googl