<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
> <channel><title>Comments on: Time Machine Bug</title> <atom:link href="http://chris.pirillo.com/time-machine-bug/feed/" rel="self" type="application/rss+xml" /><link>http://chris.pirillo.com/time-machine-bug/</link> <description>News and Reviews! Geek, Internet Entrepreneur, Hardware Addict, Software Junkie, Book Author, Once TV Show Host, Technology Enthusiast, Shameless Self-Promoter, Tech Conference Coordinator, Early Adopter, Idea Evangelist, Tech Support Blogger, Bootstrapper, Media Personality, Technology Consultant, Thicker Quicker Picker Upper.</description> <lastBuildDate>Tue, 24 Nov 2009 17:33:24 -0800</lastBuildDate> <generator>http://wordpress.org/?v=2.8.5</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Sandrs Poppers</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-625460</link> <dc:creator>Sandrs Poppers</dc:creator> <pubDate>Sun, 04 May 2008 22:28:23 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-625460</guid> <description>I  got this error and the process of turning off time machine, shutting down, disconnecting and reconnecting worked for me. Thanks for the tip</description> <content:encoded><![CDATA[<p>I  got this error and the process of turning off time machine, shutting down, disconnecting and reconnecting worked for me. Thanks for the tip</p> ]]></content:encoded> </item> <item><title>By: VesperDEM</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-596562</link> <dc:creator>VesperDEM</dc:creator> <pubDate>Wed, 27 Feb 2008 20:04:49 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-596562</guid> <description>Wow, so I guess what happened to me was different than what happened to you. I&#039;m sorry to hear that you had to wipe the drive in order to get the drive working again. Kind of defeats the whole purpose of Time Machine.Lets all hope that they get this one fixed soon.</description> <content:encoded><![CDATA[<p>Wow, so I guess what happened to me was different than what happened to you. I&#8217;m sorry to hear that you had to wipe the drive in order to get the drive working again. Kind of defeats the whole purpose of Time Machine.</p><p>Lets all hope that they get this one fixed soon.</p> ]]></content:encoded> </item> <item><title>By: Phil Hendry</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-596020</link> <dc:creator>Phil Hendry</dc:creator> <pubDate>Tue, 26 Feb 2008 12:12:03 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-596020</guid> <description>I tried disconnecting and reconnecting the drive to no avail. I was able to run Disk Utility though and it found no errors. The support rep I spoke to did assure me that the issue is now logged and will be reviewed by the dev. team.</description> <content:encoded><![CDATA[<p>I tried disconnecting and reconnecting the drive to no avail. I was able to run Disk Utility though and it found no errors. The support rep I spoke to did assure me that the issue is now logged and will be reviewed by the dev. team.</p> ]]></content:encoded> </item> <item><title>By: Jon</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-595902</link> <dc:creator>Jon</dc:creator> <pubDate>Tue, 26 Feb 2008 03:45:52 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-595902</guid> <description>I believe I ran into this problem a while ago. I too was a little confused. My workaround was to delete just the oldest backups and restart. Has been working fine since. (That way, you wouldn&#039;t have to delete all of your backups)</description> <content:encoded><![CDATA[<p>I believe I ran into this problem a while ago. I too was a little confused. My workaround was to delete just the oldest backups and restart. Has been working fine since. (That way, you wouldn&#8217;t have to delete all of your backups)</p> ]]></content:encoded> </item> <item><title>By: VesperDEM</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-595823</link> <dc:creator>VesperDEM</dc:creator> <pubDate>Mon, 25 Feb 2008 22:28:32 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-595823</guid> <description>Neither guys. I had the exact same situation just last night. I got the same error after my drive was out of space. I had less than 20GB&#039;s left on a 1TB drive.My first thought was to run Disk Utility to see if I could scan it for errors. I wasn&#039;t able to scan it because the program wasn&#039;t able to &quot;unmount&quot; the drive.So, I turned off Time Machine, shut down my system, disconnected the drive and restarted it. Once the system was restarted, I plugged the drive in again, and started Disk Utility. I was then able to scan the drive and found no errors. I started Time Machine and all is good again.I didn&#039;t have to wipe the disk or do anything other than disconnect the drive and reconnect it.Mind you, this may be a different problem than the one that Philip had, but from the sounds of the error and the symptoms, his problem and mine sound identical.I hope if this happens to someone else, that they at least try my solution before wiping the backup drive.</description> <content:encoded><![CDATA[<p>Neither guys. I had the exact same situation just last night. I got the same error after my drive was out of space. I had less than 20GB&#8217;s left on a 1TB drive.</p><p>My first thought was to run Disk Utility to see if I could scan it for errors. I wasn&#8217;t able to scan it because the program wasn&#8217;t able to &#8220;unmount&#8221; the drive.</p><p>So, I turned off Time Machine, shut down my system, disconnected the drive and restarted it. Once the system was restarted, I plugged the drive in again, and started Disk Utility. I was then able to scan the drive and found no errors. I started Time Machine and all is good again.</p><p>I didn&#8217;t have to wipe the disk or do anything other than disconnect the drive and reconnect it.</p><p>Mind you, this may be a different problem than the one that Philip had, but from the sounds of the error and the symptoms, his problem and mine sound identical.</p><p>I hope if this happens to someone else, that they at least try my solution before wiping the backup drive.</p> ]]></content:encoded> </item> <item><title>By: Smalltalk Tidbits, Industry Rants</title><link>http://chris.pirillo.com/time-machine-bug/comment-page-1/#comment-670225</link> <dc:creator>Smalltalk Tidbits, Industry Rants</dc:creator> <pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate> <guid
isPermaLink="false">http://chris.pirillo.com/2008/02/24/time-machine-bug/#comment-670225</guid> <description>&lt;!--%kramer-pre%--&gt;Chris Pirillo&lt;!--%kramer-post%--&gt;</description> <content:encoded><![CDATA[<p>Chris Pirillo</p> ]]></content:encoded> </item> </channel> </rss><!--
This site's performance optimized by W3 Total Cache:

W3 Total Cache improves the user experience of your blog by caching
frequent operations, reducing the weight of various files and providing
transparent content delivery network integration.

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached
Page Caching using memcached
Database Caching 10/26 queries in 0.025 seconds using memcached
Content Delivery Network via maxcdn.chris.pirillo.com

Served from: 192.168.20.62 @ 2009-11-25 08:24:30 -->