Time Machine Error

No, I made it unnecessarily complicated all by myself. I had a drive that I thought had failed, which turned out to be 100% and when I went to clone the drive from a new MBP drive onto it I forgot that Superduper doesn't copy the recovery partition across.
Yet again you come up with a different solution to the one I use (Carbon Copy Cloner).

Basically I put the slave MBP in target disk mode and using a FireWire 800 connection and Carbon, the entire process is unattended and painless. I really hope in future they'll allow the use of the thunderbolt port for this (should fly if both MBPs have SSDs).

Considering CCC is donateware ("free"), why did you choose Superduper?
 
Last edited:
[)roi(];7317735 said:
Yet again you come up with a different solution to the one I use (Carbon Copy Cloner).

Basically I put the slave MBP in target disk mode and using a FireWire 800 connection and Carbon, the entire process is unattended and painless. I really hope in future they'll allow the use of the thunderbolt port for this (should fly if both MBPs have SSDs).

Considering CCC is donateware ("free"), why did you choose Superduper?
SuperDuper also has a free version - paying just unlocks a few additional features. At the time I was shopping for cloning software CCC hadn't yet been updated to the whatever version of OsX I was using at the time. I've got mine set up so that as soon as the drive is connected the backup is automatic.

Unfortunately neither clone the recovery partition so ideally you want to try and remember to create that first! :o
 
SuperDuper also has a free version - paying just unlocks a few additional features. At the time I was shopping for cloning software CCC hadn't yet been updated to the whatever version of OsX I was using at the time. I've got mine set up so that as soon as the drive is connected the backup is automatic.

Unfortunately neither clone the recovery partition so ideally you want to try and remember to create that first! :o
Interesting, didn't know that... apparently can also be done by re-running the upgrade.
 
[)roi(];7285929 said:
What is the format of your HDD, and is there any chance you made this a boot drive at some point? For example loaded a bootable copy of Lion on it, then manually removed the folders?

....

The HDD was bought specifically for time machine. Nothing was done to it before it was connected to my machine. Lion asked if I'd like to use it for time machine and I clicked "yes".
 
The HDD was bought specifically for time machine. Nothing was done to it before it was connected to my machine. Lion asked if I'd like to use it for time machine and I clicked "yes".
In that case it's format is most likely NTFS and most probably won't have a bootable partition.

The only thing I can suggest is to try to break / create the partition and reformat as HFS in the hope this resolves your issue (no guarantees sorry). I have a Seagate drive that is formatted as NTFS with a bootable version of Lion; I experience the same behavior if I forget to eject it before rebooting.
 
Last edited:
[)roi(];7318471 said:
In that case it's format is most likely NTFS and most probably won't have a bootable partition.

The only thing I can suggest is to try to break / create the partition and reformat as HFS in the hope this resolves your issue (no guarantees sorry). I have a Seagate drive that is formatted as NTFS with a bootable version of Lion; I experience the same behavior if I forget to eject it before rebooting.

Thank you... I will give your suggestion a try.
 
Thank you... I will give your suggestion a try.

Not sure if this tip has been covered but on mac, if you use a new hdd you have to re format by going through disc utility and 'erase' before you start - I did - also had that 'did not eject correctly' message when mac awakes - this has disappeared on its own. hopefully won't come back.
I found most of my mac tips on mac forums -
http://www.mac-forums.com/forums/sw...ommended-free-apps-download-your-new-mac.html

cheers
 
Top
Sign up to the MyBroadband newsletter
X