|
#1
|
|||
|
|||
Cloning system to new drive
Hello! First-time poster here ...
I am running Leopard on a Mac mini and have a 160GB drive that I would like to use to replace (physically swap) the 80GB that shipped with, and is currently in the machine. I realize that SuperDuper! is not yet Leopard-compatible, so I am waiting for that to become available. In the meantime I wanted to make sure that what I have planned will indeed work! Seems like this is simple enough, but let me know if I am missing anything here. My plan is to connect the new drive via a USB-to-SATA interface, use SuperDuper! to make a bootable clone of the existing internal drive, then swap out the drives. Is it just that easy? I made bootable clones to FireWire drives under Tiger, and they seemed to work fine, but I wasn't sure if there was anything different to consider when the drive was destined to be the internal. Any tips, tricks, advice appreciated! |
#2
|
||||
|
||||
Assuming it's properly partitioned for your Mac, and you make sure the new drive is named the *same* as the old one, yes. Should work fine.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Dave, thanks for the quick and personal response! I setup the drive with a GUID partition table, which I believe is what it should be. I wasn't aware of the naming convention though -- it is OK to give the external drive the same name as the internal during the copy process, or should it be renamed after it's installed?
|
#4
|
||||
|
||||
Rename it before you try to start up from it.
__________________
--Dave Nanian |
#5
|
|||
|
|||
Could I ask why you recommend this?
I keep a clone on a partition of my internal with the same name as the boot, which means if my boot fails I can switch to it and all aliasses etc will be correct and I could carry right on. I agree it is potentially confusing have two same name disks. When it comes to saving files etc, there is potential error of saving to wrong one. I actually Keep the clone unmounted to reduce this. I have booted from the clone to test it without seeing a problem. I should say I have only been doing this (same name for clone) since Leopard, and until SD is compatible I am using Disk Image to make the clone. Is your reason for saying re-name the clone a Superduper! specific one, or for any clone? Thanks Mike |
#6
|
|||
|
|||
FYI, tonight just for yuks, I decided to try cloning my internal drive to a SATA drive connected via USB using Disk Utility. Although I had named my destination volume as simply "Seagate," as soon as I started the cloning process, Disk Utility immediately changed the name of the drive to "Mac mini HD," which is the name of my internal drive.
When the process was through, I put the cloned drive inside the mini, and so far, it is working great. Haven't noticed anything unusual (which isn't to say that I WON'T ...) |
#7
|
||||
|
||||
I recommend the same name because aliases might resolve to the wrong volume if the drive names are different.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Windows equivalent to SuperDuper!? | jreffner | General | 21 | 08-13-2009 05:36 PM |
Please help me! Hard drive failing, cloning errors... | jasong | General | 3 | 10-22-2007 09:24 AM |
Best process to replace internal hard drive using SuperDuper!? | emikysa | General | 26 | 02-09-2007 05:03 PM |
Fw Drive Wont Boot | Budgie | General | 3 | 11-05-2006 01:22 PM |
Long Hang While Copying | BackerUpper | General | 4 | 06-12-2006 08:26 AM |