SD 2.5 - Clone disk hangs on boot

[ashkit]

Hi all,

Upgraded to SD 2.5 (over the top of existing SD) on Leopard. Program ran fine but the disk image hangs during boot.

I have confirmed I can boot the disk image in safe mode (shift on boot) but in normal mode things just hang around the time launchd is starting up (its a little hard to tell). When things hang, CPU hits 100% and no disk activity.

I have tried recreating the backup using Erase than Copy (initially it was a Smart Update) and reformatted the disk between updates. I also tried rebuliding prebindings to no avail.

Boot disk is external USB. I've tried removing the plist from /Library/LaunchDaemons for VMWare and Crashplan but to no avail.

Any ideas on how to diagnose the hang on boot (down to what is actually hanging?) - or anyone else having a similar problem?

-d

[Bruno_08]

There may be something related to this post (http://www.shirt-pocket.com/forums/showthread.php?t=3564) ?
Tell us if yes , we try to find out where the problem may come ...

[dnanian]

Are you sure it's hanging and not rebuilding caches, etc? Perhaps you can send me a system profiler report...

[ashkit]

Are you sure it's hanging and not rebuilding caches, etc? Perhaps you can send me a system profiler report...

Defiantly hanging. CPU goes to 100% and no IO activity. When booting off the external drives, these are the last few messages before it freezes:

--external boot--
Feb 10 11:40:07 localhost kernel[0]: Jettisoning kernel linker.
Feb 10 11:40:07 localhost kernel[0]: Resetting IOCatalogue.
Feb 10 11:40:11 localhost bootlog[37]: BOOT_TIME: 1202604002 0
Feb 10 11:40:11 localhost rpc.statd[20]: statd.notify - no notifications needed
Feb 10 11:40:12 localhost fseventsd[29]: bumping event counter to: 0xbc8d75 (current 0x0) from log file '0000000000bc8c3a'
Feb 10 11:40:16 localhost DirectoryService[33]: Launched version 5.0 (v514)
Feb 10 11:40:17 localhost DirectoryService[33]: WARNING - dsTouch: file was asked to be opened </Library/Preferences/DirectoryService/.DSIsRunni
ng>: (File exists)

--normal boot--
Feb 10 11:48:01 localhost kernel[0]: Jettisoning kernel linker.
Feb 10 11:48:01 localhost kernel[0]: Resetting IOCatalogue.
Feb 10 11:48:04 localhost kernel[0]: display: family specific matching fails
Feb 10 11:48:04 localhost kernel[0]: Matching service count = 0
Feb 10 11:48:04 localhost kernel[0]: Matching service count = 1
Feb 10 11:48:05: --- last message repeated 4 times ---
Feb 10 11:48:05 localhost kernel[0]: display: family specific matching fails
Feb 10 11:48:05 localhost kernel[0]: Previous Shutdown Cause: 3
etc.


Full txt of /var/log/system attached. Btw, the system profiler is 160KB compressed - can I email this through instead?

[dnanian]

Yes, please. I assume that starting up a second time from the same copy also hangs?

[legaltocarry]

Hi! I'm having boot issues also. I just purchased Sd to use the smart backup feature and the first attempt at a clone failed to boot, the second clone failed to boot and finally I repartitioned and re-erased the disk and set the monitor NOT to go to sleep and the third clone DID finally boot. I've been cloning for years using the free version of SD, the Apple Disk Utility and using CCC. I've had them all work properly and I've had all of them fail to boot on occasion. Seems there's no rhyme or reason for whether they're successful at booting or not. Tom

[ashkit]

Correct. I have tried using the clone image several times to boot. But to no avail.

It seems as if the startup sequence is very different (according to system log) - and when the copies are made, a large number (numerically) of files are not transferred. This is using the "Backup - All Files" script. I'm going to smart update and change the script not to exclude anything and see if this makes any difference.

Email is on its way with System Profiler stuff

-d

Updated: No luck even when all files are copied (custom script with no excludes).

[dnanian]

Update your backup with Smart Update, then open Terminal and run:

sudo update_prebinding -root "/Volumes/the-backup-volume-name" -force

substituting your volume name, of course. Then try starting up from it.

[Bruno_08]

Update your backup with Smart Update, then open Terminal and run:

sudo update_prebinding -root "/Volumes/the-backup-volume-name" -force

substituting your volume name, of course. Then try starting up from it.

Hi Dave

This work great for me.
I just do a test successfully
As i said before by mail and in the forum, i had this problem too and i was making a Rebuid Prebinding on the clone after the boot. (because it was possible for me to launch only "tiger cache cleaner" only)

Perhaps, if I may, be useful to add this feature to update prebinding clone in a future update of SD ! :)

[dnanian]

Yes: the question is, why should it be necessary? It seems Leopard is doing something unusual here on some systems...

[Bruno_08]

Yes: the question is, why should it be necessary? It seems Leopard is doing something unusual here on some systems...

Yes.

I try to discover what is not going to, but I am not a programmer.

Little snitch ?
Clamxav ?
Hardware Monitor ?

I don't think so, i tested with and without.

Maybe, Dave, can you tell us how to achieve a shell script Rebuild prebinding to incorporate to SD after copy completes,
for those who encounter this problem in waiting to find what's wrong ?

[ashkit]

Mate,

no luck here. I tried a rebinding first up (and again at your request). :/

Could there be any interaction from having a boot camp partition on the Mac's startup drive? (Obviously I am not attempting to clone this)?

Any idea how to get the system log to give more detail on boot to find out why things are getting stuck?

[dnanian]

None that I'm aware of.