Will a DIY fusion drive work when upgraded to Mavericks?

Mavericks was exciting for all it's power, but I have noticed that a ton of pp are experiencing problems with their home-brew fusion drives when upgraded to Mavericks, is that true? And if it is, is there any fix?
Thanks!

The link is for installing 10.9 on a DIY fusiondrive (though explained for a DP). It works just fine on the final release. I just had it done and is as smooth as whistle.....
http://pintofcode.com/blog/2013/8/19/mavericks-and-fusion-drive
best of luck.

Similar Messages

Iphoto 9.2.3 does not work when upgrading to maverick

I updated my mac to maverick and does not work iphoto 9.2.3 What I can do to fix it without buying new?

thanks for your answer, try updating yesterday and opens the appstore and shows me that I have no pending updates.

DIY Fusion drive not working after Mavericks install

Hi Everyone,
I had setup a DIY fusion drive on my iMac 27" Mid 2011 - installing a Samsung SSD and a new 1TB drive. Everything was working swimmingly in Mountain Lion but as soon as I upgraded to Mavericks - everything slowed down.
In speed test I get an average write speed of 70 MB/s and a read of about 100MB/s...
Did I do something wrong? I installed Mavericks via the App Store.
Thanks.
Martin

Did you ever figure this out? I have a similar experience (read below) and wanted to know if anything you learned helped?
Hi all. I have a 3.2GHz i5 w 24 GB of Ram. Purchased in January 2014.
My good friend helped me install a DIY Fusion. I purchased a 256GB Samsung 840 Pro SSD and he did the work to "fuse" it with the regular 1TB HD the iMac came with. It is attached via USB 3.0 in an OWC case.
Originally, after being set up - Black Magic Speed tests benched it at 250-350 write and 500-650 read. I'm not a techie, but spent enough time to know that is pretty smoking and well above a typical disk hard drive.
Well, now it is down to 70-80 write and 180-250 read. The imac still boots in less than 25 seconds, so I don't feel the system is slow. (and it certainly blazes next to the first generation aluminum iMac I had before - a 2008 model). But I am concerned at deterioration of speed and really thought the extra investment would have led to faster sustained speeds.
So my questions are:
* Does anybody have any ideas why this is happening?
* Any idea what the fix is? I'm hoping not to have to start over.
* Any ideas whether it would have been better just to keep the 256 a boot drive for OS & apps, and leave the 1TB for media? I almost did this and wonder if it would have simplified things or led to better performance.
* Any idea where to go from here?
BTW, I know a little about TRIM, but I think my friend said the Samsung will handle that itself.
Lastly, you can probably tell I know a bit ABOUT this stuff, but not much on HOW to do it. So regular maintenance and upkeep is not my strong suit.
Thanks in advance for comments & suggestions.
Jake

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.

Slow boot up on 2012 Mac mini with DIY fusion drive

Hello everyone, I bought a Mac mini (2012) 2 months ago with a stock 500GB HDD.
I added another SSD to make a DIY fusion drive, and everything is working fine, except that I'm experiencing a very slow boot up.
I have confirmed both by information from the OS and some tests with command line tools, that the fusion drive itself is a success and absolutely working fine.
The slow boot up happens on cold boot only (a reboot does not have such problem).
Symptom: the Mac mini is stuck on the gray blank screen for about 40 seconds, and then finally shows up the apple logo.
Everything after this is pretty fast and fine.
I have tried the following methods and none of them seems to help:
1. Go Preferences -> Startup Disk, select the Machintosh HD. (Suggested by Apple in the Fusion Drive FAQ)
2. Verify the whole disk along with the partition with Disk Utility.
3. Reset NVRAM by holding Command+Option+P+R during boot up.
4. Reset SCM/PMU.
Does anyone have an idea on the cause of my problem?
Best regards and thank you.

If you have more than one user account, these instructions must be carried out as an administrator.
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
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged after the boot, during the time something abnormal was happening. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. Please include the BOOT_TIME message at the beginning of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Repair DIY fusion drive possible?

It seems as the mechanical drive in my DIY fusion drive setup has failed. It took forever to start the computer and the disk sounds weird. I ran the disk tool and it said that it had repaired something that was broken (can't remember what). When I restarted the computer I got a questionmark instead of an apple during startup. If I boot from an external drive I can't even find my fusioin drive in Finder. Can this be fixed or am I screwed?

You will need to reboot the machine with the DIY Fusion drive from a clone or a USB thumb drive with the Recovery HD on it. Then open Terminal and type diskutil list to view the drives. You would then need to rebuild your Fusion drive using the Terminal commands you previously used like LowLuster points out.
Using the Recovery HD would be preferred, in my opinion, because after rebuilding your Fusion drive you can Reinstall OS X from the OS X Utilities menu.

Undoing a DIY "fusion drive"

Good evening all.
I'll try to keep this as short and simple as I can.
I have a Macmini6,2 that I installed a secondary SSD into. My plan was to use the SSD for the OS and Apps and use the stock 5200rpm drive for files and data. I used an OWC instructional video on YouTube (for those interested search YouTube for: techKNOWlogy by OWC - Keeping your System and User files on Separate Drives) and was able to get it to work.
It really does work well, sort of like a DIY Fusion drive but without the system choosing what files go on the SSD. The problem is that it doesn't play nicely with one of the programs I need for work, Avid's ProTools, and I just can't afford to have this problem.
I have Time Machine backups and I was wondering if there was a way I could "unfuse" the drives and put everything onto the SSD without having to really nuke my system and start from scratch.
Any help would be much appreciated!

Yes. The way to set it up is to create a new administrator account (I called mine Boot Admin), and then install the SSD. After the SSD was in, I formatted and did a clean install of OSX onto it. When OSX asked if I wanted to transfer files from another location with migration assistant, I selected the original 5400rpm hard drive. I selected all of the options EXCEPT for the original user. So all of the Apps, files and the Boot Admin account minus my original, starting user acct.
After all software updates, I went into the System Prefs with the Boot Admin acct and created a new user account using the same name and password as the account on the original drive. I clicked Advanced Options on the newly created acct. --> Choose --> select home folder om Original 5400rpm drive ---> hit open. So I changed the Home Directory for the acct to the other drive. Then I set the new drive to the default startup drive.
Then, I deleted the App, System and Library files off the the HDD. Likewise for the Home Folder for the acct on the SSD. Then, as a final step to clear up more space, I deleted and repartitioned the recovery disk on the SSD OS to give it maximum space.
Thanks!

DIY Fusion Drive on MacBookPro8,2

Yes, I know it's not supported out ot the box.
I've been trying to set up a DIY Fusion Drive on my Early 2011 MBP 15" with no luck.
I've been googling a bit and found several others reporting the same problems on the MBP8,2. Seems this setup works on most Mac's, just not this model. Has anyone gotten this to work with any sort of hack? Please share your experience.

In case you are not already aware of these resources here are some links
http://blog.macsales.com/15617-creating-your-own-fusion-drive
http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html
There are others, but the most salient point from the first link is that it alleges the 2012 Mini is the only Mac that uses a version of Disk Utility capable of creating a Fusion volume. This sounds dubious to me though since I find it hard to believe CoreStorage is dependent upon a version of Disk Utility that exists only for the Mini. The only reason I mention this is that I consider OWC knowledgeable about the subject.
Without further details of how you intend to accomplish this I am curious how you justify the following comment:
The OS handles where the files go so I can use the time to work instead of managing where the files go for best performance.
We know Apple's Fusion Drive accomplishes these actions in firmware or software that exists in their new iMacs, but what resource led you to conclude this ability exists in your MacBook Pro, or anything other than the current production 2012 iMacs for that matter?
If you are certain it does, I may do it also. I like challenges too.

DIY Fusion Drive Problem (8,2)

Hey,
I wanted to go a step further and create my own DIY Fusion Drive. I had no problems installing the new ssd (128gb Samsung 840 Pro) instead of the hdd (standard mac hdd) and moving the hdd to the place where the optical drive has been.
I then proceeded to boot from a recovery USB Stick runing the mountain lion recovery partition on it. I configured both of these drives without any problems and finally created my Fusion Drive (visible in disk utility).
But here are things getting worse. My original plan was to recover from a TimeMachine Backup i created right before I started working on the Fusion Drive. But no, it said an error occured and I should restart the PC. After googling this error a little bit (and trying the recovery over and over again, different attempts to repair the time machine, which doesn't seemed to be broken etc.), I came up with the idea that my TimeMachine data could be corrupted and a whole backup is not possible. No problem I thought to myself.
You just try to install Mountain Lion fresh with your Recovery USB Stick and then get one or two folder from your backup that you need. But nope, installing Mountain Lion aborted with an error too while checking if my MacBook would fit the installation or something.
Last try: Cmd+R to start internet recovery. Downloaded the whole thing. Now I was able to reinstall LION fresh on my system (which of course would be the basic installation since my macbook came with Lion). Problem is: Lion doesn't know anything about Fusion Drive and I couldn't select any drive to install it on.
Right now I'm really thinking about installing the os on the ssd alone, what I didn't want to do. But I'm not seeing a possiblilty to get the system back up and running they way I wanted it to.
Now it's on you guys. My last hope. Do you have any ideas on how to fix this problem? I read so many guides and neither of them came up with the problems I have. They just say "and after configurating your fusion drive, you just install moutain lion again and you're good" :|
Thank you very much,
MrMütze

I just tried what would happen if a delete the Fusion drive again. I was able to start the installation process of LION to my SSD, but Mountain Lion still aborted with an error while evaluating my system. So it shouldn't be a problem associated with the FusionDrive.

Hard Drive warning when upgrading to Mountain Lion. 2 try and I was able to upgrade. Software update for IPhoto, had problems restarting. Do I need my hard drive checked

Hard Drive warning when upgrading to Mountain Lion. 2nd try and I was able to upgrade. Software update for IPhoto, had problems restarting. Do I need my hard drive checked

Yes.
Choose Apple menu > Restart. Hold down the Command (⌘) and R keys as your computer restarts.
When you see a white screen with an Apple logo in the middle, you can release the keys.
Click Disk Utility, and then click Continue.
In the list at the left, select the item you want to repair. (Be sure to select an item that’s indented to the right in the list, not an item at the far left.)
Click First Aid.
If Disk Utility tells you the disk is about to fail, back it up and replace it. You can’t repair it.
Click Repair Disk.
If Disk Utility reports that the disk appears to be OK or has been repaired, you’re done.
Otherwise, you may need to do one of the following steps.
If Disk Utility can’t repair your disk or it reports “The underlying task reported failure,” try to repair the disk or partition again. If that doesn’t work, back up as much of your data as possible, reformat the disk, reinstall Mac OS X, and then restore your backed-up data.
If you continue to have problems with your disk, it may be physically damaged and need to be replaced

Super drive issue not working after upgrade of Maverick or Mountain Liont

Super drive issue not working after upgrade of Maverick or Mountain Liont
try this commands , it will wrk and respond after few trys
go to APPS - Utiltiy - Terminal
Put these commands in
drutil status
drutil info
drutil getconfig
drutil eject
it will keep ejecting for bit or sign of life in it and after couple try in 5 mins it will wrk. and dont waste ur money to buy new one .

Super drive issue not working after upgrade of Maverick or Mountain Liont
try this commands , it will wrk and respond after few trys
go to APPS - Utiltiy - Terminal
Put these commands in
drutil status
drutil info
drutil getconfig
drutil eject
it will keep ejecting for bit or sign of life in it and after couple try in 5 mins it will wrk. and dont waste ur money to buy new one .

Why won't my adobe flash drive work when I try to use it?

Why wont my adobe flash drive work when I try to use it? I am going to school online and I just bought this mac book pro. My old mac book worked just fine with the adobe flash drive and shackwave.

You must mean Adobe Flash Player and Adobe Shockwave Player. Get the latest versions here:
http://www.adobe.com/downloads/
Right side column.

Will a WD hard drive work with AirPort Extreme to connect with an iPad Air

Will a WD hard drive work with Airport Extreme to connect by a iPad Air

If you already have an AE and a WD drive .. the best idea is plug it in and see on a mac in airport utility is the drive recognised.
If not you have problems.. if it is formatted correctly (Not NTFS mainly) then it can be a drive that is not compatible.
assuming it works get your ipad and pay for filebrowser or at least download a test copy and see how it goes.
Always the best way to find out.. try it.

HT201758 Will a USB3 External Drive work in the USB2 port?

Will a USB3 External Drive work in the USB2 port?

Some do and some do not. You should read the technical information carefully to determine if it's USB 2.0 compatible.

I don't want to spend 60 pounds on a apple cd hard drive, so will any cd hard drive work with a macbook air?

I don't want to spend 60 pounds on a apple cd hard drive, so will any cd hard drive work with a macbook air?

As you quote the price in 'Pounds' I'm assuming you are in the UK!
You might want to consider one of these from Amazon. I have one on my MBA and it works well.

Will a DIY fusion drive work when upgraded to Mavericks?

Similar Messages

Maybe you are looking for