Aliases failing after migrating to new disk

Question

I migrated from my original 500GB disk to a new 1TB disk by using Disk Utility's "Restore" function.  For those of you that are not familiar with Restore, it should be the highest fidelity form of coping a partition given that it does a "block copy" - e.g. it copies the data byte-by-byte instead of doing a file based copy.  Also it verifies after the copy is done.  In my opinion, it is the gold standard for copying an entire partition.
The new disk booted up fine, but I was surprised to find out that about half of my 190 aliases were broken.  When I looked inside the alias files themselves I saw that they contain a lot of data, including a path to the target file.  In all cases where the aliases stopped working on the new drive, this path was not correct.  In other words, I had moved the target file on the old drive before cloning the whole partition onto a new drive.
I reinstalled the old drive and verified that all my aliases were in fact functioning so this was not an issue in on the source disk.  The aliases were able to work properly even with outdated path data in them.
After doing some reading on how OS X aliases work, I found out they use multiple ways to find the target file.  If the path inside the alias is not good, OS X has other means to find the original target file.  But somehow this broke after copying to the new disk.
So the question is if there is a way to force aliases to get refreshed so that all their data is correct?  In other words, before I do a migration to a new disk, can I run some command that causes all the aliases on my existing disk to be resolved to their targets and then have the contents of the aliases be made fully consistent with that resolved target data.  This would fix the broken paths in the aliases which would allow them to work after the migration to the new disk.

Answer 1

Try this:
Make a folder on your destop called F.
Inside folder F make two subfolders called A and B.
Inside A create a text file called T.
Now creas an alias to T which we will call T.alais.
Test out T.alias.  It should open T.
Now move T to folder B.
Again, test out T.alias.  It should open T even though it has been moved.
Now use CCC to copy F to another disk.
Delete the original F and empty the trash.
Now try to open T.alias.  It will fail.
The reason it fails is that you moved the target of an alias (from A to B) then copied the whole thing (both alias and target) to a new disk.
I just tried it and it failed for me.
This is what happens to me en-mass when I move from one disk to another.