So I finally got a 180GB Vertex 2 SSD, which I want to use as boot/OSX drive, while keeping the current 750GB HDD intact in my Mac Pro, which is also ideal to separate the /Users folder from the boot drive. If the SSD ever dies, I still have the original HDD to boot from as a backup (This HDD Volume is actually a RAID1 made by 2 identical HDDs). Here's what I prepared: via Chronosync I copied my original boot HDD to a bootable SSD volume, excluding the /Users folder (as that folder is over 400GB). On the SSD, I created a symlink referring to the /Users folder of the original HDD, in order to keep that folder accessible, while being on the original HDD. All the /System /Application /Library etc folders and hidden files/folders have been duplicated from the original HDD to the SSD. Then I selected the new SSD drive in the SystemPrefs as startup disk, and restart the system. Here's the issue: while being able to boot, the SSD drive is just partly being used as startup disk. It seems that a lot of system files and application are simply still being loaded from the original HDD (I can hear that, and notice that due to the lack of performance gain). When I examine both Volumes via the Finder, I notice the SSD Volume has a path start with "/Volume/OSX SSD", while the original HDD has "/" as path (Volume is called OSX). Looking at the startup preference pane, I still see the SSD as boot disk selected. I guess OSX keeps the original paths to system and application files still stored somewhere, which is causing a conflict as I have 2 semi identical volumes now in my system (SSD + HDD both have identical OSX files, with the exception of the /Users folder). Any ideas what I might be missing here during the migration of OSX to a smaller SSD?