- Joined
- Nov 23, 2010
- Messages
- 36
- Motherboard
- CustoMac GA-Z77x-UD5H
- CPU
- Core i7 3770k
- Graphics
- Gigabyte HD 6970
- Mac
- Classic Mac
- Mobile Phone
Hi all,
I encountered a weird problem over the weekend and think I have just now gotten it figured out, but need a bit of advice. On thursday, I updated my copy of Carbon Copy Cloner on my CustomMac. I have a scheduled task in CCC that clones over my OS X boot drive installation to another internal drive regularly; this update ran and I thought nothing about it.
Come Sunday, I rebooted my computer for one reason or another. Immediately upon choosing my boot partition in Chameleon, I receive a KP. Not immediately seeing the link to CCC, I spend the next six hours futzing with the system, reinstalling, restoring cloned backups, etc. I started to see a pattern once I started disconnecting internal HDs- anything cloned from CCC and left plugged in created KPs at the next boot.
I have now confirmed that this extends not only to my OS X boot drive, where chameleon is installed, but even to my "Data" volume. If I clone "Data" over to another internal backup drive, I receive the same KP, even if Chameleon isn't installed on Data and no other drives are connected with CCC clones. Without the presence of CCC cloned drives/partitions, the OS loads perfectly.
So now that I've determined CCC is the issue, how do I get around it short of using only external backup drives that aren't connected at startup? Is there a new setting in CCC that is causing this? In CCC, I've unchecked "chameleon" that shows up at the root of my boot drive, but that seems to make no difference. Has anyone yet experienced this?
Assistance is greatly appreciated.
Garth
I encountered a weird problem over the weekend and think I have just now gotten it figured out, but need a bit of advice. On thursday, I updated my copy of Carbon Copy Cloner on my CustomMac. I have a scheduled task in CCC that clones over my OS X boot drive installation to another internal drive regularly; this update ran and I thought nothing about it.
Come Sunday, I rebooted my computer for one reason or another. Immediately upon choosing my boot partition in Chameleon, I receive a KP. Not immediately seeing the link to CCC, I spend the next six hours futzing with the system, reinstalling, restoring cloned backups, etc. I started to see a pattern once I started disconnecting internal HDs- anything cloned from CCC and left plugged in created KPs at the next boot.
I have now confirmed that this extends not only to my OS X boot drive, where chameleon is installed, but even to my "Data" volume. If I clone "Data" over to another internal backup drive, I receive the same KP, even if Chameleon isn't installed on Data and no other drives are connected with CCC clones. Without the presence of CCC cloned drives/partitions, the OS loads perfectly.
So now that I've determined CCC is the issue, how do I get around it short of using only external backup drives that aren't connected at startup? Is there a new setting in CCC that is causing this? In CCC, I've unchecked "chameleon" that shows up at the root of my boot drive, but that seems to make no difference. Has anyone yet experienced this?
Assistance is greatly appreciated.
Garth