/usr/sbin/update Lossage After 10.4.3 install

Question

I just moved from 10.3.9 to 10.4.3 on my G5 (dual, 2.0ghz; I used CCC to clone my 10.3.9 boot disk to a firewire drive and did a clean install. I migrated applications and user settings only. The install was of 10.4 and I immediately did a software update to 10.4.3 using the Combo update. Relatively immediately, my console started to get this message:
Jan 1 17:42:43 Duende /usr/sbin/update: FIXME: IOUnserialize has detected a string that is not valid UTF-8, " C˚^?¸?¸?¸?˝_¸/¯'‡ ".
This repeats every 30 seconds because this (update) is the daemon that writes the internal file system cache back to memory (every 30 seconds). Looking at the string by copying and pasting to the terminal, it is:
" C\313\232^?\302\270?\302\270?\302\270?\313\235_\302\270/\302\257'\342\200\241 "
(I'm supposing this is some unicode string, but I don't know whether it's supposed to be a file name or some internal structure or what.)
My PB running 10.4.3 with roughly a clone of the above system doesn't have the problem.
I did the usual:
* disk utility
* fsck -fy (from safe-mode boot)
Initially, Disk Utility reported 2 "illegal names" which it fixed when booted from the install DVD. (I even tried the idea I read of it being wacky file names in the Adobe CS2 Legal directories and deleting the wacky ones).
The system appears to run ok otherwise, so the real problem I guess is the size of the logs and the messiness of looking for other stuff in them.
Any ideas?
-rpg-
Dual G5 2ghz Mac OS X (10.4.3) 8gb ram, 2 250 gb ATA drives
Dual G5 2ghz Mac OS X (10.4.3) 8gb ram, 2 250 gb ATA drives

Answer 1

When the Migration Assistant (which I think is what the Setup Assistant uses) asked me on first boot in 10.4 whether I wanted to migrate from an existing computer, it found the firewire disk I had cloned to. As best I know, Target Disk Mode just makes the other computer a firewire drive.
Also, since your note, I booted from the firewire clone of 10.3.9 and it worked just fine. So, I think this is not the problem.
I think it would be easier to somehow figure out where the bad string is coming from. I'm guessing it's a unicode filename that is not UTF-8, just like it says. There seems to be a lot of non-Roman file names around, and I've seen threads where Adobe CS2 has created some some have caused problems for Tiger, so I'm guess it's a similar thing.
The logs give a hint, the string is this:
C˚^?¸?¸?¸?˝_¸/¯'‡
But this is a mapping from what the string really is to what can be represented in the log.
However, if after a while I can't figure it out, I'll do another erase and install and reload things by hand. What makes me hesitate is that I have a wiki which is kind of a mess to install afresh.