Migrating to a new disk

Sorry if this is the wrong place for this, but I'm not sure where else it will fit.
The basic story is this: I currently have /home on a huge HDD and everything else on a small SSD. I just got a new SSD and was wondering what the best way to copy everything from the old SSD to the new one without screwing up booting or breaking arch. Anyone have a guide or tool that would help? This is not my area of expertise so anything would be helpful.
Thanks in advance.
Last edited by zorkfandm (2011-12-01 18:22:19)

hello zorkfandm
Well yes it can be done.
option 1) if new ssd is equal or bigger than old one - clonezilla
option 2) use rsync and do not forget to correct fstab and grub/menu.lst in new ssd
example :
rsync -avxHAXS --delete --progress /OLDROOT /NEWROOT
keep in mind it will copy only files that are on root partition but if you have separate /usr or /var or w/e it will not copy them, so you need to repeat for eatch of them same operation aka /OLDROOT/usr /NEWROOT/usr etc.....
option 3) well many many more ways but IMO they are more complicated
Last edited by cybertorture (2011-12-01 19:20:44)

Similar Messages

SVM: migrating to a new disk device

Hello,
We have a 70GB LUN from one SAN disk array on a Solaris 10 server. This LUN has been configured into SVM using a single disk device and then carved up into soft partitions. We will need to migrate this LUN to a new disk array. Since SVM only sees this LUN as a disk slice and not as a metavolume, is there any way to mirror/replace the disk without disabling the applications that have been built on the soft partitions? In this case, we have several active Solaris Containers root file systems living on these soft partitions. Some metastat output to give you a better picture:
# metastat -c
d112 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d111 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d110 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d109 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d108 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d107 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d106 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d105 p 5.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d104 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d103 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d102 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d101 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
# metastat d101
d101: Soft Partition
Device: /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
State: Okay
Size: 6291456 blocks (3.0 GB)
Device Start Block Dbase Reloc
/dev/dsk/c4t600507630EFE08ED0000000000000105d0s0 0 No Yes
Extent Start Block Block count
0 1 6291456
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c4t600507630EFE08ED0000000000000105d0 Yes id1,ssd@n600507630efe08ed0000000000000105
I looked at the manual for "metareplace" and the language indicates that it would only work with a metavolume and not directly with the disk device.
Thanks.

Okay, there's two ways to use SPs and mirrors. The easist way in most cases is to create a large mirror, then carve the SPs out of it. But you really have to start off doing that. Trying to convert this layout to that would be annoying, assuming it's possible at all.
The other way is to take the SP, toss a concat/stripe on it, then use that as the submirror base. It's a bit more annoying because you have to create the SPs on the other disk in the same manner.
So you'd take a look at 'metastat -p' output. That shows the commands to recreate the current layout. Use the SP creation items, but run them on the second disk. This sets up a second set of SPs.
Then take all the SPs and put a concat/stripe on them. So for one of the existing SPs (like d101), you'd do like this;
metainit d151 1 1 d101
Do that for all the SPs (on both disks). Now you can create the one-way mirrors from the currently-used side. As an example:
metainit d201 -m d151
Now you've got the mirror. The problem is that the filesystem is still mounted from d101. You've got to unmount from d101 and mount d201 before you can sync the mirror to the other side (that's the only step that can't be done online). Once the side is no longer mounted, you can sync up.
metattach d201 d171 (or whatever you've named it).
Good luck.
Darren

Migrate to a new disk

I have a PowerMac G4-450 AGP which still meets most of my needs, except disk space. the original 27 Gb drive is constantly maxed out, so I got a new 120 Gb drive and installed it as a slave drive. I moved most of my user files and a lot of apps to the new drive, but still, the main drive is always maxing out due to virtual memory, caches, Library space, etc.
Is there a way, now that I am in this mess, to install OS X on the big drive, and cleanly move all of the installed software from the small drive to the big one, without having to reinstall everything? Is it necessary to re-jumper the drives to make the big one the master if I do this, or can I just leave it as-is?
Thanks
JEH

Use Carbon Copy Cloner to move the existing Mac OS X installation from the old drive to the new one.
(23377)

Aliases failing after migrating to new disk

I migrated from my original 500GB disk to a new 1TB disk by using Disk Utility's "Restore" function. For those of you that are not familiar with Restore, it should be the highest fidelity form of coping a partition given that it does a "block copy" - e.g. it copies the data byte-by-byte instead of doing a file based copy. Also it verifies after the copy is done. In my opinion, it is the gold standard for copying an entire partition.
The new disk booted up fine, but I was surprised to find out that about half of my 190 aliases were broken. When I looked inside the alias files themselves I saw that they contain a lot of data, including a path to the target file. In all cases where the aliases stopped working on the new drive, this path was not correct. In other words, I had moved the target file on the old drive before cloning the whole partition onto a new drive.
I reinstalled the old drive and verified that all my aliases were in fact functioning so this was not an issue in on the source disk. The aliases were able to work properly even with outdated path data in them.
After doing some reading on how OS X aliases work, I found out they use multiple ways to find the target file. If the path inside the alias is not good, OS X has other means to find the original target file. But somehow this broke after copying to the new disk.
So the question is if there is a way to force aliases to get refreshed so that all their data is correct? In other words, before I do a migration to a new disk, can I run some command that causes all the aliases on my existing disk to be resolved to their targets and then have the contents of the aliases be made fully consistent with that resolved target data. This would fix the broken paths in the aliases which would allow them to work after the migration to the new disk.

Try this:
Make a folder on your destop called F.
Inside folder F make two subfolders called A and B.
Inside A create a text file called T.
Now creas an alias to T which we will call T.alais.
Test out T.alias. It should open T.
Now move T to folder B.
Again, test out T.alias. It should open T even though it has been moved.
Now use CCC to copy F to another disk.
Delete the original F and empty the trash.
Now try to open T.alias. It will fail.
The reason it fails is that you moved the target of an alias (from A to B) then copied the whole thing (both alias and target) to a new disk.
I just tried it and it failed for me.
This is what happens to me en-mass when I move from one disk to another.

Photoshop elements 10 will not migrate to my new macbook pro/retina display. There is no CD/DVD player on this machine. Any suggestions on how to get Elements onto my machine? Yes, I have the disk(s).

Photoshop elements 10 will not migrate to my new macbook pro/retina display. There is no CD/DVD player on this machine. Any suggestions on how to get Elements onto my machine? Yes, I have the disk(s). Am I going to have to buy an external CD/DVD player to load this one program:(

I have ordered a USB3 BluRay/DVD/CD player/burner and will use that both with my iMac ( in which the Superdrive seems to be failing ) and the MBPro Retina I just bought .

How to migrate to a new 4TB disk (switching from MBR to UEFI)

I have an HP Pavilion p7-1167c running Windows 7 Home Premium Service Pack 1.
My 1TB drive ran out of space, so I want to migrate to a new 4TB drive. However, the current drive is a MBR drive and I understand that I need to use UEFI to be able to utilize the full 4TB (ie I am limited to using 2TB of the 4TB if the 4TB drive is formatted as an MBR drive).
In the past when migrating to a new drive, I just cloned the drive. Can I still do this, even though they are formatted differently? I'm not sure if a cloning process would clone data from a MBR disk to a UEFI disk while keeping the disk formatting, or if a clone requires that the source and target disks be the same formatting.
If I can clone a drive from a MBR disk to a UEFI disk, how would I get my PC to boot using the new disk? Do I maybe need to change something in the BIOS to cause the PC to support UEFI?
If I can't clone the drive due to needing to go from MBR to UEFI, what should I do? Is the only option to do a build from scratch (ie reinstall the OS from scratch with the UEFI disk installed, then re-install all the apps, and then re-load my data from a backup)? I'm hoping to avoid this, due to the obvious large amount of effort that would take.
Thanks in advance for any guidance as to how how I might migrate my system to this new drive, while being able to utilize the full 4TB of space.
Thanks!

Hi Steve,
Another point of clarification. You should be able to use a 4 TB hard drive for data. To use it as a replacement boot drive would required some special efforts using retail media and provided that the boot sources will support UEFI boot devices. If you boot up W8 installation media in UEFI mode then you could try installing W8 to the GPT formatted hard drive. I haven't tried this on your particular model so I can't say for sure that it will work.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

I installed ML on a new disk and didn't get much migration

I bought a new 750GB HD for my early 2009 MBP. I intalled ML on the new disk using a FW drive enlosure. I took the drive out of this enclosure and put it into my MAC. I took my old drive and put it into the enclosure and used migration assistant to take over all the data. I don't have any of my contacts or email setsups. I have my apps, but that is it. My desktop is also blank.
I did this once before from Leopard to SN and everyting came over fine and I was able to use my MAC right after the migration.
Is there anything I did wrong?

Repeat the process, ensuring that you erase and format the new HD properly, Mao OS Extended and with the GUID partitioning scheme. Install ML and on first boot, use the Setup Assistant to do the migration. See Pondini's Setup New Mac guide, wherein you treat the new HD as a new Mac. Then, swap the HDs.

Should I wiat for Snow Leopard to migrate to new disk?

I have a Macbook Pro 13" and had a repair resulting in anew hardrive. Did an erase and install of original Leopard to at least have the machine up to date. My question is that I will be migrating all my info and setting from my Imac's Time Machine to the new disk on the Macbook Pro, which I did when I first bought it a few months ago. Would it be better to wait a day or two--when my Snow Leopard DVD Upadte Disk--will be arriving and then migrate everything over of is it the same as migrating now and then updating the computer when the new OS arrives either tomorrow or Saturday.

Hi, again.
Nobody who's allowed to talk about it knows as of today exactly what's involved in the installation, but all indications are it's not a big deal.
Purely from past experience, however, I always recommend doing major things one step at a time. If you do one right after the other, you multiply the (small) chances of error, and may have no clue about which step caused any problems.
I'd say do the migration first. Start Time Machine (or other) backups immediately. Then use the Mac for a while to be sure everything's kosher.
There are bound to be bugs in Snow Leopard. Probably minor overall, but no major (and few minor) upgrade in the history of the computer has been entirely bug-free. So make sure your Pro is working fine on Leopard, and is properly backed-up, before installing SL.

Clean install from Leopard to M. Lion on new disk

I have a late 2007 MacBook Pro with 10.5.8 and a too small disk. I just purchased a 500GB internal disk. I'd like to do a clean install from Leopard to Mountain Lion using the new disk. What is the recommended procedure? I'd like to avoid the extra step of installing Snow Leopard first as documented.

Well, I wouldn't do it that way, too many steps.
I would:
1. Clone your current drive to the external drive, instead of using Time Machine. (Carbon Copy Cloner or SuperDuper)
2. Boot from your external drive, update it to Snow Leopard.
3. Purchase and download ML from that external boot. Save a copy of the installer to a location other than the Applications folder, that way it won't be erased after you use it. (verify that you've made a copy and not just an alias)
4. Install your new drive, format it.
5. Boot from your external, run the ML installer, select your new empty internal as the install destination, when prompted, use Setup Assistant to migrate your data from the external to the internal.
6. When done, you should have a fresh install of ML on your new internal and a bootable SL on your external as a backup. If you decide that you want to go back to SL, you can just erase the internal and clone the external back to the internal.
Note: You don't need to make a bootable USB installer, they're too slow anyway. Just keep a copy of the ML installer on your external, bootable drive, so that you won't have to download it again.
Another option: Since you're replacing the intrenal with a 500 Gig drive, you could partition it to two 250 Gig partitions. Put ML on one and SL on the other, i.e.,

OID/DAS migrate content to new install with a different realm - help

Hi all.
Need some advice.
We have a dev/test 9.0.4 (10gr1) apps environment that has a specific domain. However the PROD domain is different as the person who installed it couldn't work around the fact that the server had a different domain name than test/uat. So they put in place a Virtual Host.
I want to fix this as PROD is different to dev/uat.
1) I believe this can be done using the OUI_HOSTNAME of the runInstaller option on a new install
Can anyone confirm this ??
2) Once I build a NEW 9.0.4 infrastructure/middle tier with the correct domain - how do I:
a) Migrate users from "bad" domain to new infrastructure tier domain and maintain all SSO/privledges ?? Ldap export and import ??
b) Migrate my content across => we are using oracle Portal and an OC4J instance. I assume I can do a 'portal export' from old install and import into new install ?? IS this valid ....... and then just re-deploy the "ear" file to new application server install ??
many thanks on your advice

I figured out the answer shortly after posting my question: I booted to new disk in the FW enclosure while attached to my MBP, and ran Migration Assistant, selecting to copy data from the (old) internal disk to "this mac". I'll see how everything works six hours from now...
Regards,
Ira

MIGRATION TO A NEW HDD

I am thinking of buying a new larger Hard Disk to put into my Macbook 13".
Can somebody tell me if I can migrate the whole present disk (as it is) complete with apps.
If it can be done please tell me how.
I had the thought of installing the operating system and then restoring using Time Machine.
But will this install EVERYTHING?
regards Barry

I'd get an external drive and clone one drive to the other. You can also get connectors which allow you to temporarily connect a bare (no enclosure) drive to the computer for quick file transference.
http://www.newertech.com/products/usb2_adaptv2.php
Cloning And Backup Tools
A bootable clone is an exact copy of your drive which is capable of booting your computer. Making a copy of your computer which is capable of actually starting the computer requires special copying procedures which simply dragging files in Finder won't achieve. Some people just back up data files but if you have problems you have to reinstall all your operating system and all your applications. With a bootable clone you just start up from the backup drive and clone back everything.
To clone one hard drive to another hard drive you can use:
[CarbonCopy Cloner|http://www.bombich.com/software/ccc.html] (donationware)
[SuperDuper|http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html] (shareware)
[IBackup|http://www.grapefruit.ch/iBackup/index.html] (free)
The Restore function of Disk Utility included in OS X. [Kappy's directions|http://discussions.apple.com/message.jspa?messageID=8799711#8799711]
[Tri-Backup (commercial)|http://www.tri-edre.com/english/tribackup.html] (payware)
[Kappy's Backup Software Recommendations|http://discussions.apple.com/message.jspa?messageID=9065665#906 5665]
[Overview of Mac OS X Backup Programs|http://8help.osu.edu/1247.html]

Supported way to migrate to larger hard disk

I am a happy, no exctatic owner of a Macbook Pro 15 inch 2.6, purchased in December 2012.
The 750 GB hard disk is a bit tight.
So I'm looking at getting a 1.5 TB drive and migrating to it.
I don't want to lose my restore partion or anything else I've already done.
How should I go about it?
I have thought of using:
Carbon Copy for Mac
Clonezilla
Booting a Live CD Linux and using dd
Anyone done what I'm trying to do?
Configuration:
Main boot is Mac with refit add in to manage boots.
200 MB for Mac boot
200 MB for bootcamp Windows
The rest of the drive is allocated for Centos 6.4 I use grub as the boot manager for centos and windows.
Hope this is enough.

Mine looks exactly like yours.
What I'm hoping to clone is the entire hard disk.
I've followed CCC guidelines and set up a recovery partition and copied the Mac OS parition.
I was hoping to copy bootcamp and centos across as well, but so far no luck.
Though I know bootcamp and the centos stuff are accessible in other ways.
I could just as easily boot centos and use dd to do the job here. Partition up the new disk before hand using the apple disk tool and dd parition by parition using centos. Seems like an awful lot of work though.
Since Mac OS is open source based, I assume I could do this job with dd running under the main OS. Problem there is fdisk works a little differently.
I know i can if successfully clone non Mac paritions either before or after the disk switch. I'm a Unix/Linux geek after all.
Thanks for all the good input.

Hard drive volume appears in sidebar Favorites when new disk mounts

Hard drive on my 17” MacBook Pro Quad Core i7 (2.5 GHz, 8GB SDRAM OS 10.8.2) is partitioned into 4 volumes; I'll call them A-Mountain Lion startup drive, B-Personal, C-Work, D-minimal clean Mt. Lion for emergencies. Problem relates to my regular boot drive.
I have Finder sidebars set to show 8 or 10 folders in the "Favorites" section and have ticked all boxes in the "Devices" section. Most of the time I have no external disks, CDs, etc., connected to the MBP, so the Devices section generally shows my computer and the four partitions. So far, so good.
Lately, every time an external volume is mounted and every time a disk image is mounted, the Personal volume (B) of my internal drive, which is already showing under Devices, also pops up in the Favorites section of the sidebar. I remove it from the Favorites, but the next time an external disk or a disk image mounts, there it is again. It's always volume B, never A, C, or D.
I have tried everything I can think of to cure this odd behavior: Used Disk Utility (verify all disks/volumes; repair volumes; repair permissions; etc.), though nothing seemed wrong. I've run Disk Warrior on all volumes. I cleaned out everything possible on the startup drive (A) with the latest version of Onyx. I've repeatedly trashed the plists I could identify in my user Library that had "sidebar" or "finder" in their names. I've logged in and out; started and restarted; started with shift key down. Still, every time a new volume or disk mounts, up pops this extra volume B among the Favorites (where it shouldn't be). I checked and unchecked various combinations of sidebar items in Finder Preferences. I've Forced Quit the Finder. It doesn't matter whether all, some, or no devices are checked; when a new disk mounts, there's the extra volume B again.
I have only two other clues to add. (1) I created a new temporary user account on my startup drive (volume A), and this behavior did NOT occur in the new account. (2) This same behavior had arisen once before, a couple of months ago. I went through similar blind attempts to cure it then, but at some point I must have done something right because I it got fixed. For the life of me, I can't remember which of all the things I tried did the trick.
Many thanks to anyone who can shed light on this annoying behavior.

I can add a bit to my earlier description. I had said the problem did not occur in a new user account. Well, after using the new account for a while, it showed up. Eventually I erased the startup volume and installed Mountain Lion (plus updates to 10.8.2) fresh. I used migration assistant to transfer only my old user, pared down applications, and network settings -- no preferences, application support stuff. The old user carried over the problem. But I immediately created a new user and have been working from it for the past two weeks, very gradually opening apps, adjusting settings, etc., and testing for the anomaly at each change. In some cases I did move preferences from a backup clone, but was always careful to test after each addition. All was well for a week, until one morning I noticed the data partition had appeared in sidebar Favorites. So I'm back to where I was. I had been documenting each change or introduction I made. The only things my notes said from the day before the sidebar anomaly appeared was launching and struggling to activate QuarkXPress 9.3, and copying over my old prefs and settings for TextWrangler. I completely removed every trace of QXP, but the problem remained. (I did not remove TextWrangler because I just can't believe it could be the culprit -- but could it?)
I also noticed a similar (though maybe not identical) problem posted in another thread <https://discussions.apple.com/message/20591050#20591050>, but so far no answers there either.

Migrate Database to new LUN

Hello,
we are running a Oracle RAC Cluster with ASM.
We will have to replace our current SAN-System.
At the moment there are 5 LUNs assigns to the DB-Servers.
3 LUNs are a Disk Group for the DB Files.
2 LUNs are a Disk Group for the Archive Logs, Controlfiles, Online Logs
How could I migrate the Data to a new SAN?
Do I have assign the new LUNs to the DB Servers and add them to the current disk groups in ASM?
Or do I have to create new Disk Groups in ASM?
Edited by: 882151 on 29.08.2011 02:21

Hi,
Sorry, but I'm not a pro in Oracle RAC.You must be very careful to perform these operations.
eg: When you execute the alter diskgroup add / drop disk (EM or SQLPlus), and the prompt is released does not mean you can remove the disks, this command starts the process of rebalance and you need to ensure when disks can be removed.
I suggest you read this thread.
Re: Data to be moved to new Storage Array : ASM_POWER_LIMIT question
Regards,
Levi Pereira

How can I upgrade ver 10.5.8 so I can migrate with my new macpro

I am using Max OS X Ver 10.5.8. How can I upgrade my MacBook
I am using Max OS X Ver 10.5.8. How can I upgrade my notebookso I can migrate with my new MacPro?

Hello,
One way is to get & Install 10.6, then update it to 10.6.8.
Snow Leopard/10.6.x Requirements...
General requirements
   * Mac computer with an Intel processor
    * 1GB of memory (I say 4GB at least, more if you can afford it)
    * 5GB of available disk space (I say 30GB at least)
    * DVD drive for installation
    * Some features require a compatible Internet service provider; fees may apply.
    * Some features require Apple’s MobileMe service; fees and terms apply.
Which apps work with Mac OS X 10.6?...
http://snowleopard.wikidot.com/
Call Apple Sales...in the US: 1-800-MY-APPLE. Or Support... 1-800-275-2273
Other countries...
http://support.apple.com/kb/HE57
It looks like they might still have it...
http://store.apple.com/us/product/MC573Z/A?fnode=MTY1NDAzOA

Migrating to a new disk

Similar Messages

Maybe you are looking for