I created a bootable clone (Firewire external hard drive) of my Powerbook G4 internal hard drive (which I've replaced with a new, bigger drive) using Carbon Copy Cloner, but for some reason the external hard drive won't boot (I've also tried it on an iMac with the same results).
That's to say the drive comes up and is selectable in the "Startup disk" preference pane, but after rebooting the "spinning circle" on the screen just goes on forever. I've looked up the "bless" command and tried it to no avail. although something strange happened:
I entered the following command in the OSX command-line Terminal (according to a Carbon Copy Cloner help page and other sources online):
I expected the command-line prompt to reappear, conforming the command had gone through, but instead I just got a > (greater than character). Seems like it had gone into some different mode, because no UNIX commands (or anything else for that matter) responded, just giving me a new line with >. I was able to return to the command-line by entering CTRL-C)
I've also run Disk utility to check the drive and permissions. The latter needed some fixing, but all's well now. The drive itself checked out without any issues.
What could be the cause of this, and what can I do to fix it?
That's to say the drive comes up and is selectable in the "Startup disk" preference pane, but after rebooting the "spinning circle" on the screen just goes on forever. I've looked up the "bless" command and tried it to no avail. although something strange happened:
I entered the following command in the OSX command-line Terminal (according to a Carbon Copy Cloner help page and other sources online):
Code:
sudo bless -folder "/Volumes/EXTERNAL_DRIVE_NAME/System/Library/CoreServices/"
I expected the command-line prompt to reappear, conforming the command had gone through, but instead I just got a > (greater than character). Seems like it had gone into some different mode, because no UNIX commands (or anything else for that matter) responded, just giving me a new line with >. I was able to return to the command-line by entering CTRL-C)
I've also run Disk utility to check the drive and permissions. The latter needed some fixing, but all's well now. The drive itself checked out without any issues.
What could be the cause of this, and what can I do to fix it?
Last edited: