Top stories

Apple Devotes Entire Home Page To Jerome York Obituary

20100318-york.jpg

If ever you needed a sign that Apple was a different kind of technology company, this is it.
What other computer manufacturer would remove its top-selling, hype-inducing, industry-altering new product from the prime spot on its website home page, and replace it with an obituary to an investor?
This is one of those “Here’s to the [...]

Coming Soon: Steve Jobs, the Sitcom

Fake Steve creator Dan Lyons just signed a deal to bring Steve Jobs to another small screen near you.
The half-hour series called “iCon” is billed by the presser as “a savage satire centering on a fictional Silicon Valley CEO whose ego is a study in power and greed.”
Making sure the barbs prick will be the [...]

What’s Next For the iPad? A Tabletop iPad, According to Xerox PARC Circa 1991

Way back in 1991, just as Apple was transitioning from 68k to PowerPC chips, the braniacs at Xerox PARC were predicting it’s entire iPod, iPhone and iPad strategy. And next up for the iPad is a blackboard-sized device.
Nearly 20 years ago, just as personal desktop computers were taking off, researchers at Xerox started thinking about [...]

iPhone App Arms Users With Silent Panic Button

A new app called Silent Bodyguard features a panic button that sends an SOS distress signal with GPS coordinates to potential rescuers without alerting onlookers.
While the $3.99 app, available on iTunes, isn’t the first ICE (in case of emergency) app, this one is backed by Dr. Clint Van Zandt, former FBI chief hostage negotiator and criminal [...]

Time Machine Bug Raises Backup Reliability Questions

A bug in the OS X 10.5.3 update creates trust issues with the reliability of some Time Machine backups, writes Baltimore Sun reporter David Zeiler. Hourly system backups to some Mac Pro machines are inconsistently met with the vague error message

tm_error_msg.png

which leaves the option of staring at the screen or clicking the OK button and pretending the failed backup doesn’t matter.

MacRumors has had a discussion thread going on this topic since the end of May, and the support forums on the Apple website show a question on this topic that remains unanswered after 69 replies.

A simple fix may help in some cases, according to blogger David Alison. Run the Console application in your Utilities folder, and select All Messages on the left. Then start searching using the box in the upper right. All Time Machine activity is logged under the process name of “backupd”, so searching for that will pull up all the relevant logs. If you’ve got an open backup that’s listed as “In Progress,” even though Time Machine is not running, try deleting that to see if it allows your backups to continue.

If you enjoyed this article:
Subscribe via RSS or email, or follow us on Facebook and Twitter

About the author

Lonnie Lazar

Lonnie Lazar is a writer, musician, web designer attorney. He writes about Apple for Cult of Mac and Mac|Life, and about VoIP and telecommunications for Voxilla. Follow Lonnie on Twitter @LonnieLazar, join the Cult of Mac on Facebook, and find Lonnie's photos on Flickr.

Email the author | Read more posts by Lonnie Lazar.

8 comments

    I’ve been getting that message lately with my time machine back up, but I haven’t had time to even think about it. I guess I should be worried. I’ll try the fixes. Thanks.

    I get that on my G5 iMac. Going to TM’s console and choosing backup now seems to solve the immediate issue but it would be nice not to have to do this manually from time to time.

    The most common error message I get is that some random .DS_Store file can’t be found. Was I under the misapprehension that .DS_Store files should stay put once they’re created? Fortunately these errors clear up next time Time Machine runs.

    I also get more serious meltdown-class errors when my TM disk is close to full. I have been solving these by deleting blocks of my backup where incremental data in unimportant to me, thus freeing up disk space until the next meltdown.

    I have been getting errors like this one, even though I go on with a hard core backup strategy, meaning copying all files and checking the total number of items and sizes via info manually. Only this way I have the chance to dig through to find those files, which cannot be copied due to non ANSI encoded name or ill permissions. By the way, I had experienced no problems with this strategy in the days of Tiger. So I rather assume that the “bug in the OS X 10.5.3″ is related to file copying mechanism rather than the fancy Time Machine backing-up.

    I get this regularly on my brand new 3GHz iMac that’s had Time Machine running since it came out of the box. So no excuses that I can think of. Today I needed a file that got messed up since yesterday lunchtime, but there were no successful backups between 9am and 3pm, even though the Mac was running constantly and should have been backed up every hour. Time Machine is fantastic, but this needs fixing…

    The article tells how to monitor Time Machine using the Console application. As an alternative to that method I’ve created a Unix alias that runs the following command in an xterm.

    tail -F /private/var/log/system.log | grep backupd

    This command does nothing special that Console doesn’t do. It’s just my preferred way on monitoring Time Machine.

    [...] looks like there are quite a few other Mac users experiencing this error, [...]

    The long thread about time machine backup failing on apple.com has been pulled. or someone got a link that work?

Buy Inside Steve's Brain Buy from Amazon.com Buy from Barnes & Noble