Incomplete Boot of Clone - Blue Screen
 

I just ran SD for the first time, cloned to a partition on another internal drive. Cloning seemed to go OK, sizes of original and cloned partitions about the same.

When I try to boot from the clone the boot gets to the "Starting Mac OS X" window, the progress bar goes about 2/3 of the way to completion, then I get a blue screen. I tried twice with the same result. Disk Utility says the partition is OK, and permissions are OK.

I already tried the "name both disks the same" trick, no joy.

Running 10.4.3 on a PMG4, Quicksilver 2002. SD 1.5.5 (v74)

What now?

TIA

If you could, please send me the system.log from the system that's failing to boot. You'll find it in /private/var/log/system.log on the volume that you copied to: use "Go To Folder" in Finder, followed by /Volumes/the-drive-name/private/var/log to get there.

Send that to the support address via email and I'll take a look (this should be after it's failed to boot, don't re-clone before sending me the log).

Thanks!

Done, Thanks
 

Dave, ignore the Nov. 8 entries in the system.log. SD failed when I tried to clone yesterday because of the Tiger /var/db/volinfo.database bug, which I fixed as suggested in the FAQ.

No problem, Argent -- I was looking for other stuff anyway. :)

Fixed!
 

Just a note to say that Dave provided me with a fix by email.

Many thanks for the quick service!

My pleasure, Argent.

Same problem
 

I have exactly the same problem. Earlier, I found the answer to "could not disabled Ignore Permissions through "Babybloc's" inquiry, but am now to this "blue screen" problem. The log wouldn't record.

An e-mail was sent as an answer as to how to deal with this, but that doesn't help me.

JT

I'm confused, JT. Did you get a reply from me via support that wasn't useful?

From JT (Jack)
 

You sent (I believe) Argent an e-mail that Argent indicated solved the problem. I'm new to all this type of communication and am sort of fumbling around. I hope I will become better at explaining this problem.

So, why am I getting the "blue screen" and am unable to clone my internal HD to my external HD?

Jack

Jack --

Are you getting the blue screen when you try to boot from the copy, or during the copy itself? If the latter, you're probably getting a "kernel panic" due to some low-level software.

What I'd suggest, if that's the case, is to send me a System Profiler report. To do so, run System Profiler, then choose File | Save. Save to the default (XML) format, archive if large, and send to me at the support email address. I'll take a look and see what I can see.

Sound OK?

Not completely computer illiterate, but I'll have to think this through a bit and get back to you. I might just consult my son on this, whom I've also just bought your SuperDuper, but he has not yet installed it on his G-5.

We'll eventually get this thing worked out.

Jack

OK, Jack -- sorry if I've been unintentionally confusing...

I've spent a few days now thinking this over and determined that SuperDuper probably has nothing to do with my problem. I'm most likely having problems with my external HD's. I bought a new external (I needed it anyway) and tried to clone it. The same thing happened as with my older external. I then decided to try and clone a volume on one of my internal HD's. I did a safety clone to a volume running 10.3 and now have 10.4.3 working there — perfectly.

I then decided to just try a regular installation from the Tiger installation disk to both my externals. The intallation continued until 73% completion and froze. I tried Panther and got to about 92% completion and stalled.

So, there has to be an issue (I believe) that has nothing to do with SuperDuper. Don't know if anyone else has run into this problem, but thought you'd like to know that I don't think your product was it, and I'll be looking at the Apple site to see if I can work this thing out.

Thanks for your assistance,

Jack

That definitely seems likely, Jack -- either bad cables, FireWire ports or cases.

Sorry to hear about the trouble, though! Stop back when you figure it out and let us know what it was -- it'd be good to have a record for others who might hit the same snag.