Damaged Fusion Drives

Hello all, I'm coming to the communities with the sad news that my iMac a few days ago started acting up, upon running a few 'repair disk permissions' tasks, I learnt that there was something unusual as it started showing messages like these:
Open error 5: "Input/output error" on…
and
Open error 1: "Operation not permitted" on…
Around the same time many apps would quit unexpectedly, I was unable to log out, and basically all I did would take an awful long time. Looking up the errors on the internet I learn that they likely had to do with a drive that had gone defective. As I had DIYed a fusion drive myself, I was unable to know which one was going south, so I de-fused them and I've now reinstalled Mavericks on the SSD.
I would appreciate if anyone has a comment to make as to whether you've experienced the same errors as I have and how did you solve them. I also would like to know if there is a utility out there (free, preferently) to put both drives to the test, to be able to confirm if there's something wrong with any or both of them. What surprises me though is this...
My 2010 iMac qualified for a HDD replacement, so the new one has been in for roughly just 6 months. On the other hand, the Crucial-branded SSD has similarly been installed for only 8-9 months. The fact that any or both of them are becoming un-reliable is more than disappointing, really sadenning.
All/any help you provide will be much appreciated.
Jorge...

This diagnostic procedure will query the log for messages that may indicate a system issue. It changes nothing, and therefore will not, in itself, solve your problem.
If you have more than one user account, these instructions must be carried out as an administrator. I've tested them only with the Safari web browser. If you use another browser, they may not work as described.
Triple-click anywhere in the line below on this page to select it:
syslog -k Sender kernel -k Message CReq 'GPU |I/O e|find tok|n Cause: -|NVDA\(|timed? ?o' | tail | open -ef
Copy the selected text to the Clipboard by pressing the key combination 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 into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Normally the command will produce no output, and the window will be empty. If the TextEdit window (not the Terminal window) has anything in it, post it — the text, please, not a screenshot. The title of the TextEdit window doesn't matter, and you don't need to post that.

Similar Messages

Fusion Drive - HDD spins up often

Hi,
I am currently using Fusion Drive and all seems to be working fine.
The only thing I could remark on at the moment is that the HDD is being turned on and off very often by Fusion Drive. Sometimes, it even stalls the computer, until the HDD is fully spun-up. I'm a little worried that all the start / stop cycles will eventually weaken and damage the HDD.
The question is: can Fusion Drive be tweaked (terminal ?) ?
The configuration is
1x 128 GB OWC Mercury EXTREME Pro 6G SSD:
1x 500 Gb Western Digital Blue drive
Thank's all.

From the menu bar, select
 ▹ System Preferences ▹ Energy Saver ▹ Power Adapter
and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.

Mac mini fusion drive startup slow

Unfortunately my fusion drive was damaged and replaced by Apple service center. When I got it back it startup very slow, even slower than my white mac book.
Initially, I though it was not start up from SSD so I tried to select SSD as the start up disk. There are only one hard disk to select (bundled SSD and typical HDD and it showed a size of 1.1 TB). Is this normal to see only only one hard drive? I thought there should be 2 disc, SSD and normal HDD.
I also erased the disc and reinstalled the mountain lion, but it still start up slow.
Is there any configuration I have to do in order to make it boot up from SSD?

Thank you for your help.
My Mac HDD and SSD are as follow.
Is there anything wrong?

Disk Utility error when verifying DIY fusion drive

Hi,
It has been a while since I had to post a problem, but I need others advice on this if you can help. When 10.8.3 came out I installed an M4 512gb ssd in my main drive bay of 2008 unibody aluminium macbook and put a 1tb spinner in the optibay. Created a fusion drive, migrated data and all has been great. Decided to run disk utility today to check for any errors as I had a sleep issue with the 10.8.4 update which I ended up solving by changing the sleep settings in terminal - the issue had caused a few forced shutdowns. I have Disk Utitliy Version 13 (450). The Fusion drive is shown as the logical volume group followed by the volume disk. When I run a verify disk on the volume itself it is all ok:
Verifying volume “Cybernet”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 6 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Cybernet appears to be OK.
When I run it on the LVG it comes up as:
Verifying partition map for “M4-CT512M4SSD2 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 40 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
Verifying partition map for “WDC WD10JPVT-00A1YT0 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 43 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
I got the same when I did a safe boot and when rebooted from the recovery partition.y question is, do I repair or could it damage my setup? eg is Disk Utility being accurate and it can repair the error, or is it a phantom issue that should be ignored bearing in mind it's a DIY fusion drive and it could end up getting mashed?
Thanks!

Hi,
The computer's running fine since I sorted the sleep issue. No issues as far as I can tell, which is why I was surprised to see the error. What does the error actually mean - is it saying that the volume is a different size than the computer thinks it should be and therefore it'll just change a few values? In which case I suppose a repair is harmless? I just don't want to repair and then reboot to find the volume corrupted.

Issue with Fusion drive (Late 2012 iMac)

I have a late 2009 iMac that has been backed up with Time Machine. I recently picked up a late 2012 iMac with the 1TB Fusion drive. When I first plugged in my Time Machine drive, I was asked if I'd like to transfer my files over. I did, and everything was working fine. I was using about 800GB of my 1.12TB Fusion Drive.
I recently decided to add a new partition to the Macintosh HD in order to put Windows on it. I did this through the Disk Utility. I noticed that it was taking an inordinately long time to create this partition. Finally, I realized that the Disk Utility was locked up. I was forced to reboot to fix it.
I went back and tried again and I got an error stating that the drive had errors and I couldn't make a new partition. So I attempted to "repair disk". That gave me an error "Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility."
So I rebooted into recovery. Recovery was absolutely no help either. It couldn't repair the drive, even though it had me erase all the data. So I downloaded 10.8.2 on my Mac Mini and made a boot disk out of my Thunderbolt drive. I booted into OS X and tried again to repair, thinking it would work since the Fusion was no longer the boot drive. No such luck. I then booted back into recovery and had recovery download and install a fresh version of 10.8.2. 2+ hours into the download/install, I get an error that says "OS X couldn't be installed because the disk Macintosh HD is damaged and can't be repaired."
Ok, so as a final attempt, I had recovery use my time machine to start over. That worked, kinda. It now shows my Fusion drive as being completely filled in Disk Utility (49KB remains, only about 800 or so was used before), and Finder shows the Fusion drive as being 860GB capacity with 837GB used. I still can't repair the disk. And now my Time Machine acts like I'm working on an entirely new computer and says there's not enough room on the drive unless I format my Time Machine drive and start over.
Yeah, TL;DR, but does anybody have any idea how I can get this issue resolved? I wonder if doing the TM restore from my 2009 iMac may have introduced the non-Fusion version of Disk Utilities that doesn't know how to fix my issue.

Yes I have AppleCare.
Before that I've now made a bootable disk and tried to repair the internal drive, but this was not possible.
I have a Time Machine backup, but excluded some temporary folders.
Is there a way to access these folders in case they aren't in a damaged area?
Maybe using "Target Disk mode"?
I've never done this before.
This Mac has no FireWire, but we have an adaptor for Thunderbolt to FireWire - could I connect an older Mac with FireWire using this adaptor for Target Disk Mode?
Many thanks.

What caddy do I need to remove data from a fusion drive?

my MacBook Pro has died due to water damage to the logic board and ssd I have the fusion drive removed and have been told I need a caddy to remove the data and put it on another machine, what am I looking for?

You don't have a Fusion Drive. You should be able to find an enclosure for the SSD at macsales.com and perhaps elsewhere. Of course, if the SSD has been damaged, you won't be able to recover data from it.

Which configuration of iMac 27" ? Fusion drive or not ? RAM upgrade ?

I'd love to get a new 27" iMac for my Mother, but cannot decide if the higher i7 processor (3.5) is worth the price, and cannot decide if the 3TB "Fusion" drive is worth the extra $350.
The retail Apple stores stock the i7 only with the 3TB Fusion drive, the better graphics card, and stock 8GB of RAM, but one can configure the machine if ordering on-line via the link below. Her husband will reimburse me or it will be a gift. Money is not the issue.... just whether or not the money is worth spending.
One last thing: The apple store rep said that the "Geniuses" have to do the RAM upgrade, say from 8GB to 32GB because the 21" unit has to be opened. So the consumer doing the RAM upgrade will void the warranty. Yet I see website indicating that the 21" has a nice convenient door to open and the RAM is user-upgradable without voiding the warranty. Which is true ?
Apple wants to charge $600 (parts and labor) for the RAM upgrade to 32GB. But Crucial has 32MB of this RAM for under $300 with a lifetime warranty. Is there a reason to use the RAM from Apple ?
LINK: http://store.apple.com/us/buy-mac/imac?product=ME089LL/A&step=config

1. 27" iMac with 3.4Ghz i7 and NVIDIA GeForce GT 775M with 2GB video memory is just $200 more than 27" iMac with 3.2Ghz i5 and NVIDIA GeForce GT 755M with 1GB video memory. How much is her time worth per hour? If it's for business use, it pays for itself quickly. Same opinion for the 'build-to-order' upgrades in speed and video available on the 27" i7.
2. Fusion drive is a hybrid combining 128GB SSD with either a 1TB or 3TB rotating platter hard drive.
Analysis and review of Fusion drive in a 2012 iMac: http://www.anandtech.com/show/6679/a-month-with-apples-fusion-drive
Conclusions and performance are on pages 5 and 6 of the review.
3. 27" iMac RAM is "user-replacable", quoting from the 2013 'Important Product Information' addendum to the manual:
"Do Not Make Repairs Yourself
Your iMac doesn’t have any user-serviceable parts, except for memory, which is user-replaceable in 27-inch models only. Do not attempt to open your iMac. If your iMac needs service, contact an Apple Authorized Service Provider or Apple for service.
If you open your iMac or install items other than memory in 27-inch models, you risk damaging your equipment. Such damage isn’t covered by the limited warranty on your iMac."
quoted from http://manuals.info.apple.com/MANUALS/1000/MA1662/en_US/imac_late2013_ipig.pdf
OWC video of the 27" RAM upgrade installation: http://eshop.macsales.com/installvideos/imac_27inch_late_2012_mem_m/
4. If it's for business, go for the i7 and the video upgrade.
5. I'd do the upgrade myself, purchasing from a reliable vendor of Apple RAM such as crucial.com or macsales.com. I have no experience with the other vendor you mentioned, RAMfinder.com. Factory-installed RAM offers the pricey convenience of having a machine configured by you online and shipped directly to your mother in a few days with no one else needing to be involved. I'd avoid any Apple salesperson who apparently doesn't know the 27" iMac product well enough to give you the truth about user-installable RAM upgrades. OWC (macsales.com) will purchase system-pull original RAM allowing you to recoup a small portion of the cost of the upgrade, though nothing close to the resale price of the RAM.
Message was edited by: kostby

Will the 2013 update to the regular macbook pro include a fusion drive option?

What is the likelihood that the 2013 update to the regular macbook pro will include a fusion drive option?

Apple will only modify the hardware of your computer in case something is damaged. However, if you want, you can try to make your own Fusion Drive on the MacBook Pro, as Apple doesn't support it officially on that Mac > http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html

DIY MAC Fusion Drive

I'd like to create my own MAC Fusion Drive, but I'm not a dev so I need a little bit of guidance, which would also help a lot of people I'm guessing.
I am trying to follow jollyjinx's instructions, which are not that detailed. Specifically, I am trying to find the names of my two drives and I can only find one. Maybe the drives are not connected in a way to do this I'm not sure. I have a 750GB HDD and an 80GB SSD installed internally in my 2011 Mac Mini. I have been using both drives, SSD for the OS and a handful of common files and the HDD for iPhoto and iTunes libraries. A Fusion drive would be perfect!
When I run dmesg in Terminal, here is what I get:
-bash-3.2# dmesg
PMAP: PCID enabled
Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64
vm_page_bootstrap: 2003271 free pages and 77497 wired pages
kext submap [0xffffff7f8073e000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff800073e000]
zone leak detection enabled
standard timeslicing quantum is 10000 us
standard background quantum is 2500 us
mig_table_max_displ = 74
TSC Deadline Timer supported and enabled
corecrypto kext started!
Running kernel space in FIPS MODE
Plist hmac value is    735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
Computed hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
corecrypto.kext FIPS integrity POST test passed!
corecrypto.kext FIPS AES CBC POST test passed!
corecrypto.kext FIPS TDES CBC POST test passed!
corecrypto.kext FIPS AES ECB AESNI POST test passed!
corecrypto.kext FIPS AES XTS AESNI POST test passed!
corecrypto.kext FIPS SHA POST test passed!
corecrypto.kext FIPS HMAC POST test passed!
corecrypto.kext FIPS ECDSA POST test passed!
corecrypto.kext FIPS DRBG POST test passed!
corecrypto.kext FIPS POST passed!
AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
AppleACPICPU: ProcessorId=3 LocalApicId=1 Enabled
AppleACPICPU: ProcessorId=4 LocalApicId=3 Enabled
AppleACPICPU: ProcessorId=5 LocalApicId=255 Disabled
AppleACPICPU: ProcessorId=6 LocalApicId=255 Disabled
AppleACPICPU: ProcessorId=7 LocalApicId=255 Disabled
AppleACPICPU: ProcessorId=8 LocalApicId=255 Disabled
calling mpo_policy_init for TMSafetyNet
Security policy loaded: Safety net for Time Machine (TMSafetyNet)
calling mpo_policy_init for Sandbox
Security policy loaded: Seatbelt sandbox policy (Sandbox)
calling mpo_policy_init for Quarantine
Security policy loaded: Quarantine policy (Quarantine)
Copyright (c) 1982, 1986, 1989, 1991, 1993
          The Regents of the University of California. All rights reserved.
MAC Framework successfully initialized
using 16384 buffer headers and 10240 cluster IO buffer headers
IOAPIC: Version 0x20 Vectors 64:87
ACPI: System State [S0 S3 S4 S5] (S3)
PFM64 (36 cpu) 0xf10000000, 0xf0000000
[ PCI configuration begin ]
AppleIntelCPUPowerManagement: Turbo Ratios 0057
AppleIntelCPUPowerManagement: (built 13:47:00 Aug 14 2012) initialization complete
console relocated to 0xf60010000
PCI configuration changed (bridge=16 device=5 cardbus=0)
[ PCI configuration end, bridges 13 devices 18 ]
mbinit: done [96 MB total pool size, (64/32) split]
Pthread support ABORTS when sync kernel primitives misused
rooting via boot-uuid from /chosen: 7B269773-B97B-335A-A4EF-A3D6956395BA
Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
com.apple.AppleFSCompressionTypeZlib kmod start
com.apple.AppleFSCompressionTypeDataless kmod start
com.apple.AppleFSCompressionTypeZlib load succeeded
com.apple.AppleFSCompressionTypeDataless load succeeded
AppleIntelCPUPowerManagementClient: ready
BTCOEXIST off
BRCM tunables:
pullmode[1] txringsize[ 256] reapmin[   32] reapcount[ 128]
highWaterMark: VO[ 192] VI[ 192] BE[ 192] BK[ 192]
FireWire (OHCI) TI ID 823f built-in now active, GUID c82a14fffeeaff8c; max speed s800.
USBMSC Identifier (non-unique): 1690A44191FF 0x59b 0x370 0x0
USBMSC Identifier (non-unique): AA19164300000896 0x3f0 0xb107 0x8192
Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/EHC1@1D,7/AppleUSBEHCI/U SB FLASH DRIVE@fd133000/IOUSBInterface@0/IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub /IOSCSIPeripheralDeviceType00/IOBlockStorageServices/IOBlockStorageDriver/hp USB Flash Drive Media/IOGUIDPartitionScheme/OS X MOUTNAIN LION INSTALL@2
BSD root: disk4s2, major 1, minor 15
imageboot_setup_new: root image url is file:///BaseSystem.dmg
IOHDIXController: NOTE: administrator is creating non-ejectable disk image
KDIFileBackingStore::_handleStart: initial R/W vn_open returned 30
imageboot_mount_image: root device 0x1000011
HFS: Low Disk: Vol: Mac OS X Base System freeblks: 30158, warninglimit: 30790
Kernel is LP64
ioqueue_depth = 64,   ioscale = 2
Previous Shutdown Cause: 0
[BroadcomBluetoothHCIControllerUSBTransport][start] -- completed
DSMOS has arrived
[IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification
[IOBluetoothHCIController][start] -- completed
BCM5701Enet: Ethernet address c8:2a:14:59:28:c5
AirPort_Brcm4331: Ethernet address 28:cf:da:01:31:fd
IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
IO80211Interface::efiNVRAMPublished():
[IOBluetoothHCIController::setConfigState] calling registerService
AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
en1::IO80211Interface::postMessage bssid changed
en1: 802.11d country code set to 'US'.
en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20 MAC AUTH succeeded
wlEvent: en1 en1 Link UP virtIf = 0
AirPort: Link Up on en1
en1: BSSID changed to 00:23:6c:bf:ae:20
en1::IO80211Interface::postMessage bssid changed
AirPort: RSN handshake complete on en1
[ffffff8018e64c00][BNBTrackpadDevice::init][75.15] init is complete
[ffffff8018e64c00][BNBTrackpadDevice::handleStart][75.15] returning 1
[ffffff8019e85800][AppleMultitouchHIDEventDriver::start] entered
[ffffff8018da6c00][AppleMultitouchDevice::start] entered
MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20 MAC AUTH succeeded
MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20 Unsolicited Auth
wlEvent: en1 en1 Link UP virtIf = 0
AirPort: RSN handshake complete on en1
wl0: Roamed or switched channel, reason #4, bssid 00:23:6c:bf:ae:20
en1: BSSID changed to 00:23:6c:bf:ae:20
en1::IO80211Interface::postMessage bssid changed
-bash-3.2#
I can only find one reference to a drive in the data, but maybe I'm missing something. Any help would be greatly appreciated!

So far, so good! The article steps worked perfectly. I setup the Fusion Drive and then restored from my Time Machine Backup (from the SSD). I then moved the files over that were on the HDD (which I also backed up on my external drive. Everything seems to be working great! The volume was previously named 80 SSD OS X (to differentiate from the HDD) and it is still named that, although, as you can see from the screenshot, it now has a 576GB capacity (not 750GB, which is what I thought I put in there--my memory is horrendous! lol) ....not a big deal. I consider this a huge success at this point. Thanks again for the article!

Creating a Fusion Drive Safely

Hello. I currently have a macbook pro mid 2012 13 inch with a 256 SSD start up and a 1T regular hard drive with 16GB RAM.
Even though the 1T hard drive is in the DVD drive it sort of just acts like an external hard drive as it shows up as a separate drive in finder and I am wondering if one of you amazing people can tell me how to make a fusion drive in a way that is safe and time machinable, so that for all functional purposes I just turn on my computer and it looks like I have a 1.256T system that flows perfectly.
Also if this is achieved and I can time machine back it up; in a few years when I upgrade to say the new 2T Macbook pro ssd will there be any issues importing directly from time machine if my previous computer, the one I am using now, had or has a fusion drive.
Thank you.

Oh, my solid stage 256 is where the original hard drive used to be and the 1terrabye regular hard drive is in where the dvd drive used to be. If the dvd drive is the optical drive then I should be having the correct hardware configuration.
If that is correct and I do have the correct configuration, can you please share with me a recommended link or procedure to follow for making me a DIY Fusion Drive.
I talked to one of the techie guys from Simply Computing yesterday (apple authorized dealers in canada) and he said that he has this setup and it works great and when I mentioned about performance, he said that there is a slight reduction in speed and described it as, "A normal solid state is 4 times as quick and with a fusion it is 3.5 times".
If all this info is correct I would just like to proceed with it and get a recommendation for how to do it or a suggested link that has been used and proven to work for such DIY Fusion Drives. Is the one that I shared good enough for it. Thanks everyone for your kind time and attention to this.

Creating a Fusion Drive ?

Hi All,
I have a mid-2011 iMac which I plan to install a Samsung 840 Pro SSD to use as part of a Fusion Drive setup.
Typically I backup using Carbon Copy and wil be taking a backup prior to the mod.
Once the drive has been configured...... will I need to reinstall the OSX from scratch, or is it just a matter of bringing back the Backup ??
Pete

When you use CoreStorage to format the SSD and mechanical HD it will be a destructive format/paritioning so the new Fusion disk will look like one HD but in fact will be two under the hood. You should be able to use CC to restore your image as it will look like a single drive.
I'm not sure if that model iMac has a Fusion tool supplied by Apple or not. I think you have to use one of the many guides found online to manually configure the drives to be a single Fusion drive using diskutil at the command line. If I remember correctly, you'll need to boot with a thumb drive with 10.8.3 installation on it. Then go to the Terminal to configure the Fusion drive setup. Then you would have to find some way to run CC from a bootable thumbdrive, etc. I think you could boot the backup disk made with CC then run CC from it to clone to the new Fusion drive. That should work. Worse case scenario, you always could just re-install OS X on the Fusion drive and then use the Apple Migration Assistant to grab your data from the CC'd drive.
Either way, give yourself at least half a day in the event you run into issues and have to work around things.

I am planning to buy an iMac 21.5 inch with Fusion drive and 16 GB RAM while i visit USA for a conference. My country of origin is India. Once i am back to India, will my iMac be covered by the Apple's Protection Plan?

I am planning to buy an iMac 21.5 inch with Fusion drive and 16 GB RAM while i visit USA for a conference. My country of origin is India and the option of configuring to my need is not avaialble here in India. My concern is once i am back to India, will my iMac be covered by the Apple's Protection Plan if something goes wrong here in India?
I recently came across some posts regarding International warranty related issues for iPhone and iPad....hence this crossed my mind...
Waiting for response from the support group members...

Thanks Ralph
This essentially means that if my iMac develops some problem (both software and hardware) in my country (India), it will be completeley attended (even the whole system requires replacement) by the AASP in India...is that what you say?

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#

Is there a way to run a external ssd with my mid 2011 iMac hdd in a raid configuration and basically have a fusion drive

is there a way to run a external ssd with my mid 2011 iMac hdd in a raid configuration and basically have a fusion drive

A Fusion Drive is not a RAID; it's a CoreStorage logical volume group. While it's technically possible to do as you suggest, there would be little or no benefit from it.

Programs repeatedly crashing on my late 2012 Mac Mini Fusion Drive

I have a late 2012 Mac Mini Fusion Drive 2.6ghz, 16gig RAM running Mac OSX 10.9.4 . For the past week or so I have had a number of programs - both Apple and third party apps crash repeatedly, I have repaired permissions and restarted numerous times but nothing seems to fix it. For example Mail would crash each time I cancelled a password being accepted by Mail in a particular account, Safari has crashed for various reasons. Apple Motion has also crashed more times in the past day or so than it ever has in the past year. It's crashing when I try to add a point or node to a line in an animation I'm finishing.
Does anybody have any idea why this is happening now and does anybody know how to fix it?

Launch the Console 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 Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Damaged Fusion Drives

Similar Messages

Maybe you are looking for