I'm back from a week of my son's mid-winter break.
We rented a neat house above Truckee (high high above Truckee) with a mess of friends and totally recreated. Cooking, playing, sledding, skiing. It was really great - what was better was re-introducing the kiddo to sledding. Just a "That's AWESOME!" after a snowbank drilling crash was enough to forgive him the snowball to the back of the head. Or the ones at the shuttle buses. Or the shovelful of snow down my back - something about this trip brought out his inner Calvin. We had a couple of days in deep snowstorm and then a few more in blue sky sunny weather - making Mitchell a very happy ski-woman.
Upon return I fired up my main development machine and was greeted by a growing stream of I/O errors as I did repository backups. (system.log and console.log, via the Mac OS Console app) This machine is one of the monster QuadG5's which still rips along nicely. Those machines have had a significant number of failures in their liquid cooled housings, so I'm always a bit on the lookout for goop leaking out. But nothing like all these hundreds of channel resets!
What?! This was only happening on my firewire buss too. Gah.
I've spent a fair number of hours doing all the various dances - different disks, Diskwarrior, reformatting, juggling cables, making coffee.
It was a firewire buss-powered camera, last used just before I left to Skype with Zach Thomas of Aeroplane Software, which was screwing everything up.
I was fretting about the gigabytes of data on those firewire drives... man it would hurt to lose that. But now as it's spinning out again to the backup drives I'm going to go get some pasta and celebrate.