Fusion Drive  4TB + SSD m4 512 Go DEAD can't reformat

Hello,
I have an iMac 27 late 2010 i5 3.6 with 16 Go of RAM running 10.8.3
For Christmas, I received a M4 SSD 512 Go and decided to replace the 2TB in my iMac with a 4TB and create a Fusion Drive.
The operation worked beautifully and my iMac became incredibly fast, which was the goal.
Yesterday, the iMac did not start and I got the white screen with the spinning wheel. After reading about zapping the pram and Vram, nothing worked.
I booted from an external hard drive with Mac os X 10.8.2 and ran Disk Util to check the drive. I got a lot of red lines in the report and got the error Disk Utility can't repair this disk. back , reformat and restore.
I was able to copy some of the files on the drive and decided to reformat the drive.
Everytime I try to reformat the drive (4.4tB Fusion Drive) the mac shuts down and restarts.
I tried to un fuse the fusion drive and I get the same result.  the screen goes black, the computer restarts and displays that the mac encountered a problem and had to restart.
when I type the commande in terminal diskutil cs file, I see the logical volume group.
When I do a diskutil cs Delete Volume xxxxxx xxxx xxx x x x x x x x
started CoreStorage operation on disk 2 iMac
Unmounting disk2
Removing Logical Volume from Logical Volume Group
then the mac shuts down and restarts.
it took me 2 hours to crack the beast open to perform the disk implant last  christmas and it was scary. I thought I would never manage to close it properly.
I understand that this operation voided the warranty (i have the Apple Care for 3 years).
Any help greatly appreciated.
Thanks
Phil

Thanks for your answers.
I still don't know if it was the SSD or the HD that was faulty but I found a solution via this post
https://discussions.apple.com/message/21492423#21492423
Jerome Tremblay
This solved my questionRe: Unable to reformat/repartition Fusion Drive 
Mar 12, 2013 11:05 AM (in response to Topher Kessler)
@Topher : It did not work, and it failed with POSIX errors similar to the zeroDisk message I posted above.
However, While I was unable to "cleanly" solve my problem, I managed to reset everything by booting in single-user mode from an external hard drive (with cmd-S) and overwriting the disk directly with
cat /dev/random > /dev/disk0 cat /dev/random > /dev/disk1
Then I rebooted and I could reformat the drives (actually, I created another fusion drive using these directives).
I was able to reformat the drives as a Fusion Drive. My time Machine backup was only a week old but it worked perfectly. I was able to add the rest via my Backblaze subscription.
Don't know how long the Fusion drive will last but I am prepared with my backups in case it happens.
Phil

Similar Messages

  • Is anything written permanently to the Fusion Drive's SSD?

    Is anything written permanently to the Fusion Drive's SSD or is it just a very large cache for the HD component?
    I'm wondering, because I'd like to know, mostly out of curiosity, if the mechanical portion of the Fusion Drive were to fail, might the computer still boot from information on the SSD?

    (I back it up with Carbon Copy Cloner AND Time Machine.)
    So, if either part fails, the machine is quite dead until the internal drive is replaced?  I ask because these two drives are detected separately in utilities such as TechTools Pro, where their S.M.A.R.T. data can be retrieved and tested independently.
    If a failure of either portion of the drive totally disables the whole drive, would this sort of double the chance of a Fusion drive's failure?

  • HT5446 If I buy a mac mini with a fusion drive and add windows using boot camp, can I make the SSD function be dedicated to the windows partition?

    If I buy a mac mini with a fusion drive and add windows using boot camp, can I make the SSD function be dedicated to the windows partition?

    Additional information from Linc's post. Basically, only one additional partition can be added to a Fusion Drive and it resides on the HDD.
    Do computers that come with a Fusion Drive support Boot Camp?
    Yes. Use the Boot Camp Assistant to create a Windows partition and install Boot Camp. The Windows partition will exist on the hard disk drive, not the Flash drive, and is not part of Fusion Drive Logical Volume Group. 3TB Fusion Drive configurations need to update to OS X Mountain Lion v10.8.3 or later to install Windows 8. See iMac (27-inch, Late 2012): Boot Camp alert with 3T hard drive for more information.

  • I keep my library on an external hard drive 4TB.  It's full.  Can I use more than one hard drive to keep my library on?

    I keep my iTunes library on an external hard drive 4TB.  It's full.  Can I use more than one hard drive to keep my library on? Like two 4TB next to each other.

    Create a concatenated disk set
    Increase storage space with a concatenated RAID set (also called “Just a Bunch of Disks” or JBOD). If you need one large disk, but you have only several smaller disks, you can create a concatenated disk set to use several small disks as one large disk.
    Open Disk Utility, in the Utilities folder in Launchpad.
    Select one of the disks that you want in the set, and then click RAID.
    Click Add (+), and type a name for the RAID set.
    Choose a format from the Format pop-up menu. Usually you’ll choose the Mac OS Extended (Journaled) format.
    Choose Concatenated Disk Set from the RAID Type pop-up menu.
    Drag the disks you want to add to the set to the list on the right.
    Click Create.
    Exerpt from:
    Disk Utility 12.x: Create a RAID set - Apple - Support
    Note that the biggest CON to concatenated RAID configurations is vulnerability to volume failure. If either disk fails, the whole volume fails. If you choose this option, I would highly recommend backing up your music to a cloud service. There are very cheap per GB/storage, and some of the most reputable actually offer unlimited storage:
    Five Best Cloud Storage Providers - Lifehacker

  • Fusion drive vs ssd 256gb which is better

    hoi gang, im in the market for a new mac mini. and i need some help with choosing the right options when buying it.
    " i do music " and i need a mini that fast and runs at the highest possible speed when making music. and of course using it for some fotos, emails and yes internet. 
    so ....
    specs im choosing
    2.6 ghz
    16GB 1600MHz DDR3 SDRAM - 2x8GB
    Now here is my problem which one do i choose?
    1TB Fusion Drive [Add $250.00]
    or
    256GB Solid State Drive [Add $300.00]
    Remember i need the mac that is the best at everything and speed is important!!!

    Choose the 256 GB SSD disk if you need more speed. Fusion Drive is a small flash drive and a hard disk that work together, so OS X automatically puts your most used apps and documents on the flash storage.
    If you need storage, you can choose the Fusion Drive or the SSD and an external disk

  • HT3476 Fusion drive versus ssd drive issues

    HHow can I compare the fusion drive to the ssd drive in the MAC mini

    Lanny wrote:
    A fusion drive will be a little faster than a HDD and a SSD will be a lot faster than both, especially if it's connected via PCExpress 2.
    I agree with the second half of your statement but my experience with the fusion drive VS a standard 5400 RPM HHD is that it is significantly faster, not a little. Apple has managed to find a good balance between permanently storing often used items on the SSD and using it for buffering.

  • Fusion Drive on a 2010 iMac with 2tb HDD & 256gb SSD

    Hi,
    well basicailly the title says it all!
    I have a 2010 iMac with the 256gb SSD and 2TB HDD which to me seems like it would be great option for the Fusion Drive...
    Does anyone have any ideas on how I could make the drives work like the new Fusion Drive?
    I've seen the Macworld Tutorial on a DIY Fusion Drive but i'm still not sure if doing that will work in the same way as the preinstalled 2012 iMac Fusion Drive... I know that Mac OSX will treat the combined drives as one, but in terms of moving files depending upon their usage is another matter.
    If the Macworld step by step is followed will Mountain Lion handle frequently used files / apps like the apple presentation states or will it just use the drives as one and not increase the performance of my machine?
    Any help on this would be much appreciated, especially if anyone has followed the Macworld steps etc!
    Thanks
    Darren

    Thanks fir the reply, I thought with the fusion drive the SSD and HDD were two seperate storage devices seen by OSX as one volume, and the software determins where the files most used will be placed and accessed from.
    I've read a bit about this here;
    http://macs.about.com/od/diyguidesprojects/ss/Setting-Up-A-Fusion-Drive-On-Your- Current-Mac.htm
    but would be great to hear first hand experience!!
    With this DIY approach it appears that the same functionality of the 2012 iMacs is achieved but simply not using the older Disk Utility, but a newer version only included on the newer models...

  • Fusion Drive like a 128GB SSD if I don't go over?

    Hi everyone!
    I have a few questions regarding the Fusion Drive. I bought a refurbished late-2013 iMac for a good price but the Fusion drive is bothering me. I'm planning to do video editing and all my applications that I need fit on the SSD. So my questions are:
    1. If I don't go over 128GB (Fusion Drive's SSD portion) am I essentially using a 128GB Flash storage? (I'm planning to edit on external drives)
    2. And is there a way to check how much files my SSD portion of the Fusion drive is holding?
    3. If I bootcamp my 3TB fusion with 1TB for Windows 7, does the SSD portion get affected when booting up Mac? I'm only using my Windows 7 for gaming.
    4. I've heard that Disk Drives get slower as it fills up, is this true? If so, could you elaborate on it please. I may leave the other 2TB remainder alone if that's the case.
    5. Lastly, I'm planning to upgrade the 8GB Ram with an extra 16GB Ram from amazon. I just wanted confirmation that these rams do indeed work on my iMac Late-2013 system. http://www.amazon.ca/gp/product/B008LTBJFW/ref=ox_sc_sfl_title_2?ie=UTF8&psc=1&s mid=A3DWYIK6Y9EEQB
    Thanks!

    You are over-complicating using your computer, simply use the Fusion drive as you would any internal HD. There is nothing special you need to do!
    As for Boot Camp, simply follow the on-screen instructions in Boot Camp Assistant (Applications - Utilities - Boot Camp Assistant) for installing. In addition you may find the manual for Boot Camp helpful, click http://manuals.info.apple.com/MANUALS/1000/MA1583/en_US/boot_camp_install-setup_ 10.7.pdf to view the manual.
    As for RAM I would STRONGLY recommend buying RAM from OWC (www.macsales.com) if you are in the USA, if you are  outside the US then buy it directly from Crucial, they have an on-screen utility to help you choose the correct RAM for your iMac. The correct RAM from OWC would be found at
    http://eshop.macsales.com/shop/memory/iMac/2012_27/DDR3L

  • Unable to install Windows on an 2010 iMac with home-made Fusion Drive

    Hi there,
    I've been very happy using mi iMac eversince I installed the SSD alongside the HDD.  Only recently I tried to install Windows 7 but it doesn't seem to work.  The installer runs, it seems as though Windows is installing but it doesn't ever seem to be able to boot.  I've tried countless times.  Everytime it boots to Windows it shows nothing but just a black screen with the cursor blinking at the top left corner.
    Now, when I home-made the Fusion Drive the Mac OS was only 10.8.2 or older and I know that with 10.8.3 Apple has made improvements towards boot camp and especially the 3TB HDDs.  I wonder if this could have anything to do.
    Anyway, please enlighten me as to what is it that I need to do to make it work.  I've been reading something about the position in which the Windows partition resides compared to GUID and EFI but honestly I have just the tiniest idea about all that.  Just for the record, the following is what shows in the Terminal after diskutil list command:
    diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *256.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:          Apple_CoreStorage                         255.7 GB   disk0s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk1
       1:                        EFI                         209.7 MB   disk1s1
       2:          Apple_CoreStorage                         942.3 GB   disk1s2
       3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
       4:       Microsoft Basic Data                         57.0 GB    disk1s4
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Fusion Drive           *1.2 TB     disk2
    Hope you can help..!

    Hello again, by reading a couple of posts I learnt the steps and so, using an external OS I repartitioned the two internal drives making sure the Windows partition wasn't part of the Fusion Drive.  I was very excited as I was sure it would work and went ahead and started the Win7 installation even before the MacOS was restored into the iMac.
    No good news though.  The installer run as expected however, when the time came for the iMac to boot from the newly installed Windows7, all I saw was a blank screen and a blinking dash at the top left corner of the screen.
    Lastly, this morning I woke up to see that my old system was fully restored from Time Machine external back up.  I also leart that using the Boot Camp Assistant I could remove the Windows partition that I created on Terminal from the external OS, which was surprising, I honestly thought that that partitioning arrangement would be off-limits for the Boot Camp Assistant.
    Still, I haven't been succesfull installing Windows back to my Mac, can anybody help?

  • Can mac mini mid2011 support fusion drives?

    I have installed 2 drives a SSD for my apps and all programs and the original HDD that came with the mini to use as a media drive.  can the Mac mini support fusion drive if so, anyone knows where I can get info on how to make both drives into a singel fusion drive

    Yes, a mid-2011 Mac Mini supports a DYI Fusion drive as long as you're running Mountain Lion. I have done this on mid-2011 prior to purchasing my current late-2012 Mac Mini.
    Here's a link to give you the steps of how to create one.

  • How to clean-install Mavericks to a fusion drive?

    Because I cannot find a complete answer here or anywhere else, I seek information about reinstalling Mavericks on a 1TB fusion drive on my late 2013 iMac. I see discussions about reinstalling, backing up data, Boot Camp issues, rebuilding a fusion drive, making a fusion drive from scratch, and the like; but I do not find the level of detail I am seeking about starting over with a fusion drive. I upgraded to Mavericks from Mtn Lion and now see hints that I needed to do something special to take advantage of the properties of this drive.
    That said, here are my questions:
    (1) When I "Command-R" reboot to Recovery and get to the Disk Utility, I see a separate 1TB HD as an extended partition as well as a 125GB drive that is root (/), which I presume is the SSD. To accomplish the clean installation, do I format BOTH? Or will formatting only the 1TB HD suffice? Does formatting only the 1TB HD also take care of formatting the SSD? Maybe it's not advisable to format the SSD ...?
    (2) Does the downloaded Mavericks installer loaded onto a USB stick using DiskMakerX have the capability to do this clean install properly? or is it necessary, in order to take advantage of the fusion drive properties (SSD+HD), to download Mavericks Installer after wiping the HD so that support for the fusion drive is maintained?
    (3) Because I am curious, where does OS X (I mean the OS, not data) reside after the installation is done? on the SSD? on the HD? I ask this because I have read that "the OS remains on the SSD," but, seemingly in conflict, that the SSD is for quick access to frequently used programs and data. Both could be correct.
    Sorry for the length of this. And thanks.

    The screenshot of DU within the booted Mavericks, not Recovery.
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage                         121.0 GB   disk0s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:          Apple_CoreStorage                         999.3 GB   disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *1.1 TB     disk2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk3
       1:                        EFI EFI                     209.7 MB   disk3s1
       2:                  Apple_HFS LaCie                   499.1 GB   disk3s2
       3:                 Apple_Boot Recovery HD             784.2 MB   disk3s3
    And you know what this is, per your request. It shows the OS on the SSD portion, the Recovery partition on the HD, etc. It's a little confusing because the disk reference numbers do not agree with those in the screenshot below, but that probably is because the shot below results from booting from a USB stick.
    Now to your comments/answers/thoughts:
    (1) Issue of number of drives. This is a fuzzy iPhone screenshot of DU after booting from a USB Mavericks installation stick:
    Looks like I cannot format the SSD directly, if that is what disk5 really is. Below I mention another possibility for getting it formatted (third paragraph from the end).
    (2) Which source for new installation of Mavericks
    I agree that it's probably best not to use the USB stick I have but to use the Recovery method to download a fresh copy. I'm not sure about the reliability of the USB vs downloading, either, but there is some evidence out there (somewhere -- I've seen it but I don't recall where) suggesting it.
    (3) Where OS X is installed -- fusion drive portion or HD portion of the Macintosh HD:
    From the information given with "disk5" in the screen shot just above, it does appear that after a USB boot, DU sees items separately, including the main storage (Macintosh HD), the Recovery partition (disk4-used also for creating the USB stick installer), and OS (disk5). Some of this layout may hold true with a "Command-R" boot from the Recovery partition, and I know I've looked at it but for the moment cannot recall the information.
    Further, it appears the OS is on the SSD. It also appears it cannot be formatted UNLESS such formatting occurs when the target for the formatting process is "Macintosh HD." I am inclined to believe now that when I make this clean reinstallation, the new copy of OS X will be put on the SSD portion, as you state. I am aware that the moving of data back and forth from SSD to HD is outside user control.
    Lowluster, thank you for answering my questions in such an organized fashion (that I can follow!). I feel confident now about proceeding even though not all questions are answered definitively.
    Allan, I'm glad to know about fusing separately an SSD with an HD. It will be useful should I run into another user's desire to create a fusion drive. Thank you again.
    David

  • How to reset 3TB fusion drive to original partition scheme

    When I first purchased my 27" iMac in early 2013 I was unable to use Boot Camp to create a Windows partition (with the version of OSX it shipped with bootcamp was initially disabled but added in an update later).  I found a guide online for untangling the Fusion Drive partitions and essentially setting up bootcamp manually.
    However, a few days ago I had Windows 8 get screwed up and needed to reformat.  I figured that since Apple now updated Mavericks to allow my machine to use bootcamp I would start from scratch and do it properly.  The problem is, I cannot seem to get my machine back into a "factory default" setup.  I tried removing the CoreStorage volume and letting the Disk Utility tool "reset" the drive, and that -seemed- to work.  I had one 3TB partition (according to the GUI) and re-installed OSX.  I used Bootcamp to split 2TB for Windows (games) and leave 1TB for Mac.  Everything went fine and I restarted into the Win8 installer.  However, at this point Windows refused to install to the 2TB partition.  I tried formatting it, and delete/create but it said it couldn't install to that partition.  The confusing part is that according to Windows I had about 8 partitions (EFI and Recovery I understand but the rest I don't know the reason for).
    So now I'm back at the OSX Recovery and this is what "diskutil list" is giving me.  Why are there all these 524.3 KB partitions?  I can't seem to remove or merge them.  I know I should have recorded what the original structure is, but it's too late now.  Can someone tell me what the 3TB Fusion Drive *should* look like, and how I can get back to that? 
    bash-3.2# diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage                         121.0 GB   disk0s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *3.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:          Apple_CoreStorage                         144.2 GB   disk1s2
       3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
       4:       Microsoft Basic Data                         2.1 TB     disk1s4
       5:          Apple_CoreStorage                         801.4 GB   disk1s5
       6:                 Apple_Boot Boot OS X               134.2 MB   disk1s6
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *1.3 GB     disk2
       1:        Apple_partition_map                         30.7 KB    disk2s1
       2:                  Apple_HFS OS X Base System        1.3 GB     disk2s2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *1.1 TB     disk3
    /dev/disk4
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk4
    /dev/disk5
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk5
    /dev/disk6
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk6
    /dev/disk7
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk7
    /dev/disk8
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk8
    /dev/disk9
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *6.3 MB     disk9
    /dev/disk10
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *2.1 MB     disk10
    /dev/disk11
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk11
    /dev/disk12
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk12
    /dev/disk13
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk13
    /dev/disk14
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk14
    Also including what my CoreStorage structure looks like...

    Since it won't let me edit my post, here is the text from the picture:
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group CB783377-EA29-4751-B149-FE6B210648B5
        =========================================================
        Name:         Internal Drive
        Status:       Online
        Size:         1066587906048 B (1.1 TB)
        Free Space:   12288 B (12.3 KB)
        |
        +-< Physical Volume 0221F6E1-8EE1-453A-A0EB-B32348EB6E53
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     144162512896 B (144.2 GB)
        |
        +-< Physical Volume F74A0E21-6435-4CB2-801F-95682108A391
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     120988852224 B (121.0 GB)
        |
        +-< Physical Volume C2BD0D1A-7EA2-4E36-A3EF-82A7E63BE439
        |   ----------------------------------------------------
        |   Index:    2
        |   Disk:     disk1s5
        |   Status:   Online
        |   Size:     801436540928 B (801.4 GB)
        |
        +-> Logical Volume Family 9DD06D63-96CD-4088-8F0E-061026E68C29
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume A531CC02-E337-473E-8F1F-F462595E1354
                Disk:                  disk3
                Status:                Online
                Size (Total):          1060804022272 B (1.1 TB)
                Conversion Progress:   -none-
                Revertible:            No
                LV Name:               Macintosh HD
                Volume Name:           Macintosh HD
                Content Hint:          Apple_HFS

  • Is any one having audio glitches with the new iMac 2013 (fusion drive)no matter what audio interface they are using?, is any one having audio glitches with the new iMac 2013 (fusion drive)no matter what audio interface they are using?

    Hello I recently purchased a new imac 2013 with fusion drive about five weeks ago I am currently using sounddevices usb-pre2 as my audio interface every 2 to 3 minutes i get audio glitches in the audio whether its itunes or the internet doesn't matter I checked on the internet evey on says its the fusion drive.it *****, I wonder if an update can fix this???

    Have you read for possible solutions over in the "More Like This" thread over here?----------------------->

  • I deleted my bootcamp via DU and then deleted the hard drive by using the terminal. My BOOTCAMP is still there and now my fusion drive is separated from the SSD portion and I have no idea how to fix it.

    First off I have a 3tb fusion drive.
    I created a 200gb bootcamp, I tried deleting the bootcamp because I thought I messed it up and googled how to delete a mac partition which told me to use Disk Utility, did that and then erased it and somehow it got locked and wouldn't let me do anything to any partition on my hard drive (everything was greyed out)
    After looking up and googling for hours I found a post saying the only way to fix it would be to go into CMD+R and go into the terminal window and type out disklist and then find the first UUID number and do something along the lines of disklist delete (UUID) i forget the exact formula. I did this, and then I had 3 separate untitled hard drives.
    One in the size of 1.9gb on in 800gb and one in 121.3gb (which is the SSD), I put my time machine backup onto the 1.9gb untitled and now my computer is booting slowly (because it's no longer running off of the SSD and the original bootcamp is still there.
    To be honest I am absolutely confused on what else to do!
    Is there anyway I can fix this?

    How do I go about deleting and then re-adding the hard drives? Completely lost on how to make it back to being a 3gb fusion drive.
    Thank you for all your help, I honestly really appreciate it.
    I followed your instructions and got the following
    diskutil list:
    -bash-3.2# diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            120.5 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *3.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:          Apple_CoreStorage                         1.9 TB     disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
       4:          Apple_CoreStorage                         251.9 GB   disk1s4
       5:                 Apple_Boot Boot OS X               134.2 MB   disk1s5
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *1.3 GB     disk2
       1:        Apple_partition_map                         30.7 KB    disk2s1
       2:                  Apple_HFS OS X Base System        1.3 GB     disk2s2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Untitled               *1.9 TB     disk3
                                     Logical Volume on disk1s2
                                     FD9357F1-1A71-44A0-A01E-41C84F1C8047
                                     Unencrypted
    /dev/disk4
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Untitled               *251.5 GB   disk4
                                     Logical Volume on disk1s4
                                     31B60F49-6981-47A3-9815-6396AD3A9BD6
                                     Unencrypted
    /dev/disk5
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *5.2 MB     disk5
    /dev/disk6
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk6
    /dev/disk7
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk7
    /dev/disk8
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk8
    /dev/disk9
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk9
    /dev/disk10
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk10
    /dev/disk11
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *6.3 MB     disk11
    /dev/disk12
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *2.1 MB     disk12
    /dev/disk13
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk13
    /dev/disk14
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk14
    /dev/disk15
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk15
    /dev/disk16
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk16
    /dev/disk17
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *319.4 GB   disk17
       1:                        EFI EFI                     209.7 MB   disk17s1
       2:                  Apple_HFS IMAC TMB                319.0 GB   disk17s2
    /dev/disk18
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *6.3 MB     disk18
    /dev/disk19
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:        CD_partition_scheme                        *804.4 MB   disk19
       1:     Apple_partition_scheme                         700.4 MB   disk19s0
       2:        Apple_partition_map                         32.3 KB    disk19s0s1
       3:                  Apple_HFS WD SmartWare            237.5 MB   disk19s0s2
    -bash-3.2#
    diskutil cs list
    -bash-3.2# diskutil cs list
    CoreStorage logical volume groups (2 found)
    |
    +-- Logical Volume Group 687E889E-B4A1-4F20-8B36-43D7A3701076
    |   =========================================================
    |   Name:         Untitled
    |   Status:       Online
    |   Size:         1946162462720 B (1.9 TB)
    |   Free Space:   5402624 B (5.4 MB)
    |   |
    |   +-< Physical Volume 7BCD8D9C-AEB2-4D48-B248-257EFC7EA922
    |   |   ----------------------------------------------------
    |   |   Index:    0
    |   |   Disk:     disk1s2
    |   |   Status:   Online
    |   |   Size:     1946162462720 B (1.9 TB)
    |   |
    |   +-> Logical Volume Family 3A8A9627-5963-49BA-8E2F-96DC7A1B033D
    |       ----------------------------------------------------------
    |       Encryption Status:       Unlocked
    |       Encryption Type:         None
    |       Conversion Status:       NoConversion
    |       Conversion Direction:    -none-
    |       Has Encrypted Extents:   No
    |       Fully Secure:            No
    |       Passphrase Required:     No
    |       |
    |       +-> Logical Volume FD9357F1-1A71-44A0-A01E-41C84F1C8047
    |           ---------------------------------------------------
    |           Disk:                  disk3
    |           Status:                Online
    |           Size (Total):          1945804734464 B (1.9 TB)
    |           Conversion Progress:   -none-
    |           Revertible:            No
    |           LV Name:               Untitled
    |           Volume Name:           Untitled
    |           Content Hint:          Apple_HFS
    |
    +-- Logical Volume Group 98213AE6-9EA8-4FB7-8B72-8E08BFBFD82C
        =========================================================
        Name:         Untitled
        Status:       Online
        Size:         251864797184 B (251.9 GB)
        Free Space:   5226496 B (5.2 MB)
        |
        +-< Physical Volume 20CEF763-635D-4A0D-A107-40E8FB161D06
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s4
        |   Status:   Online
        |   Size:     251864797184 B (251.9 GB)
        |
        +-> Logical Volume Family 2D3173B3-5B04-47E6-B331-49D1BA58E9F2
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume 31B60F49-6981-47A3-9815-6396AD3A9BD6
                Disk:                  disk4
                Status:                Online
                Size (Total):          251507245056 B (251.5 GB)
                Conversion Progress:   -none-
                Revertible:            No
                LV Name:               Untitled
                Volume Name:           Untitled
                Content Hint:          Apple_HFS
    -bash-3.2#
    Disk0
    -bash-3.2# gpt -vv -r show /dev/disk0
    gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
    gpt show: /dev/disk0: PMBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: /dev/disk0: Sec GPT at sector 236978175
          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  235298960      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      235708600    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      236978136          7        
      236978143         32         Sec GPT table
      236978175          1         Sec GPT header
    -bash-3.2#
    Disk1
    -bash-3.2# gpt -vv -r show /dev/disk1
    gpt show: /dev/disk1: mediasize=3000592982016; sectorsize=512; blocks=5860533168
    gpt show: /dev/disk1: PMBR at sector 0
    gpt show: /dev/disk1: Pri GPT at sector 1
    gpt show: /dev/disk1: Sec GPT at sector 5860533167
           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  3801098560      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
      3801508200     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      3802777736        1912        
      3802779648   491923432      4  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
      4294703080      262144      5  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      4294965224  1565567911        
      5860533135          32         Sec GPT table
      5860533167           1         Sec GPT header
    -bash-3.2#

  • Can the hdd part of the fusion drive be replaced with a large sata ssd?

    Is there any technical reason why the mechanical (hdd) can't be replaced with a large sata ssd in the fusion drive setup?

    None of these replies addressed the reason for my original question.
    I do appreciate the answers however I see I should have been a bit more thorough in my query.
    I know how the fusion works.  I know you can get a 1 tb ssd with the imac.
    I also know that it is very very expensive to get a pure pcie 1 tb ssd as an option.
    The reason for my question is to see if the sata ssd which is a little slower and also much much cheaper than pcie flash ssds can be used instead of the slow
    hdd in the fusion configuration.  I have ordered the 512 gb pcie flash for my imac so I am committed to pure ssd.  I would still like to know if
    what I mentioned is possible as a much less expensive option.
    Sorry for the confusion but in a rather lengthy search throughout the net and asking Apple's Geniuses I have been as yet unable to get any answer.
    It would seem to me that using a sata ssd instead of a sata hdd would be nothing but beneficial in the fusion setup.

Maybe you are looking for

  • Problem when printing from the browser

    The report is displayed in the browser properly. We are using rwcgi to view the reports in the browser. But when printed using the print option of the browser, the page setup is taken from the browser's page setup. How do we set the browser's page se

  • Sequence problem

    Hello Every One. I shoot HD, and i have the canon 5d, shoots which shoots at: 1920 x 1080,  and canon XHA1s, shoots at: 1440 x 1080. I shoot at 30 fps. Please let me know which setting is the best for my 2 camera's. There are so many settings, inside

  • Example of a metadata driven workflow?

    I see a post that highlights the fact that metadata driven workflows can be created (here), but I am looking for a complete example that I can run and modify.  Does anyone know where I could get a complete example of a metadata driven workflow?

  • Can't access my e-mails

    Started having problems accessing e-mails in the last couple of days. When I click on 'Email' in BT.com, I get the following message; "The server's security certificate is not yet valid!" In the browser, it shows https://signin1.bt.com/login/emaillog

  • Audio coming from only one field

    Hello, I just did a mic'ed interview with my little camera. I was wearing headphones and noticed audio coming from only the left side, but there was nothing I could do about it that I was aware of. Anyway, now that this thing is in Final Cut Express,