Problems with SSD

[wellerccs]

I upgraded to Yosemite, worst decision in my life. It was excruciatingly slow, I have an 128GB SSD start up disk, with a 500HDD in a caddy inside, 2.4Ghz processor and 8GB ram. So I back up regularly and apple said to hold cmd + R on start up and restore from time machine. I did this and selected my SSD, but the process was stopped and it said the disk could not be erased. Thereafter i could not startup from the disk and my only option was to restore onto my HDD but obviously I want to install the OSX onto the SSD to ensure my macbook is as quick as possible. I have attached a photo, I would like to format it to be able to restore to it, but so far i can't do anything with it and when I updated osx I think it asked me to encrypt it but disk utility does not see it as encrypted.

Thanks in advance.

 

[T'hain Esh Kelch]

Have you set up a Fusion Drive?

 

[cjmillsnun]

Disk Utility is quite possibly seeing it as encrypted.

It's calling it a Logical Volume Group. It's been converted to Core Storage. This is a necessary step to encryption.

To fix this, you're going to need to do some stuff in terminal.

Have a look here

http://apple.stackexchange.com/ques...-corestorage-logical-volume-from-the-terminal

 

[gr8tfly]

I upgraded to Yosemite, worst decision in my life. It was excruciatingly slow, I have an 128GB SSD start up disk, with a 500HDD in a caddy inside, 2.4Ghz processor and 8GB ram. So I back up regularly and apple said to hold cmd + R on start up and restore from time machine. I did this and selected my SSD, but the process was stopped and it said the disk could not be erased. Thereafter i could not startup from the disk and my only option was to restore onto my HDD but obviously I want to install the OSX onto the SSD to ensure my macbook is as quick as possible. I have attached a photo, I would like to format it to be able to restore to it, but so far i can't do anything with it and when I updated osx I think it asked me to encrypt it but disk utility does not see it as encrypted.

Thanks in advance.

The problem I see is that there is no partition on the SSD. Only the Logical Volume Group. This a result of how Yosemite sets up a drive. Once partitioned, you should see a Logical Partition. For instance:

• SSD Logical Volume Group
  • SSD Logical Partition

I think all you need to do is creat a single partition on the SSD a Logical Volume Group using the Partition tab as always (if you've used it in the past).

I think it asked if you want enable encryption on a volume; it does so now [in Yosemite] as it's faster because CoreStorage logical volumes is already setup - FileVault requires it.

 

[Weaselboy]

Somehow you managed to delete the logical partition an still have the logical volume group there at the top, as gr8tfly pointed out.

Go back to recovery from the TM disk and open Terminal from the Utilities menu and run the command below then tell us the output and we can help you beat that logical volume group off of there.

diskutil cs list

 

[wellerccs]

Have you set up a Fusion Drive?

Nope thats for HDD for over 1TB and only certain models.

 

[wellerccs]

The problem I see is that there is no partition on the SSD. Only the Logical Volume Group. This a result of how Yosemite sets up a drive. Once partitioned, you should see a Logical Partition. For instance:

• SSD Logical Volume Group
  • SSD Logical Partition

I think all you need to do is creat a single partition on the SSD a Logical Volume Group using the Partition tab as always (if you've used it in the past).

I think it asked if you want enable encryption on a volume; it does so now [in Yosemite] as it's faster because CoreStorage logical volumes is already setup - FileVault requires it.

I cant do anything within the partition tab either?

 

[Weaselboy]

I cant do anything within the partition tab either?

You will not be able to since core storage is on for that disk. If you give me the output of that command I can help you out. Or you can try it on your own.

In Terminal run this command.

diskutil cs list

The output will look similar to this. Yours will be a bit different because I think you somehow already deleted the logical volume at the bottom.

CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 296F2A7E-FF8C-48B5-B0B5-8F63225510C5
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         120473067520 B (120.5 GB)
    Free Space:   4096 B (4.1 KB)
    |
    +-< Physical Volume 1A04CDF6-BE9B-4B04-B8CF-0F211BB3F8EE
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     120473067520 B (120.5 GB)
    |
    +-> Logical Volume Family E4F6B94E-AB03-41F5-928B-04C0C8D02B01
        ----------------------------------------------------------
        Encryption Status:       Unlocked
        Encryption Type:         AES-XTS
        Conversion Status:       Complete
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            Yes
        Passphrase Required:     Yes
        |
        +-> Logical Volume 8ECB95D8-4D59-4288-8382-B875C46976A6
            ---------------------------------------------------
            Disk:                  disk1
            Status:                Online
            Size (Total):          120137519104 B (120.1 GB)
            Conversion Progress:   -none-
            Revertible:            Yes (unlock and decryption required)
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS

Now look at the top there where it says Logical Volume Group. Command-c copy that number string (UUID) and command-v paste it in to the command below like this using the real UUID. Get the command all set there then hit return and it should kill that logical volume and you can manipulate the drive normally again with Disk Util.

diskutil cs delete 296F2A7E-FF8C-48B5-B0B5-8F63225510C5

 

[wellerccs]

The solution

you will not be able to since core storage is on for that disk. If you give me the output of that command i can help you out. Or you can try it on your own.

In terminal run this command.

diskutil cs list

the output will look similar to this. Yours will be a bit different because i think you somehow already deleted the logical volume at the bottom.

corestorage logical volume groups (1 found)
|
+-- logical volume group 296f2a7e-ff8c-48b5-b0b5-8f63225510c5
    =========================================================
    name:         Macintosh hd
    status:       Online
    size:         120473067520 b (120.5 gb)
    free space:   4096 b (4.1 kb)
    |
    +-< physical volume 1a04cdf6-be9b-4b04-b8cf-0f211bb3f8ee
    |   ----------------------------------------------------
    |   index:    0
    |   disk:     Disk0s2
    |   status:   Online
    |   size:     120473067520 b (120.5 gb)
    |
    +-> logical volume family e4f6b94e-ab03-41f5-928b-04c0c8d02b01
        ----------------------------------------------------------
        encryption status:       Unlocked
        encryption type:         Aes-xts
        conversion status:       Complete
        conversion direction:    -none-
        has encrypted extents:   Yes
        fully secure:            Yes
        passphrase required:     Yes
        |
        +-> logical volume 8ecb95d8-4d59-4288-8382-b875c46976a6
            ---------------------------------------------------
            disk:                  Disk1
            status:                Online
            size (total):          120137519104 b (120.1 gb)
            conversion progress:   -none-
            revertible:            Yes (unlock and decryption required)
            lv name:               Macintosh hd
            volume name:           Macintosh hd
            content hint:          Apple_hfs

now look at the top there where it says logical volume group. Command-c copy that number string (uuid) and command-v paste it in to the command below like this using the real uuid. Get the command all set there then hit return and it should kill that logical volume and you can manipulate the drive normally again with disk util.

diskutil cs delete 296f2a7e-ff8c-48b5-b0b5-8f63225510c5

thank you so much this worked, but it says it will take 5 hours to restore 70GB of files to the SSD when it only took an hour on the HDD? So I tried this overnight to wake up to and error half way through saying the disk cant be restored? Shall I just try again?