From: "adam mercado" <AE-List@media-motion.tv>
Mime-Version: 1.0 (Apple Message framework v753.1)
In-Reply-To: <list-5522780@media-motion.tv>
References: <list-5522780@media-motion.tv>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <1C0318D1-323A-4D0A-A02F-D1322862C9DC@influxx.com>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [AE] Lesson learned
Date: Wed, 9 Jul 2014 21:34:31 -0700
To: "After Effects Mail List" <AE-List@media-motion.tv>

Uhg. Episodes like that try your patience (and your wallet). Good for =20=

you for following it through and finding a solution.

I wrote an article a while ago about my educational but fruitful =20
delve into Terminal. I totally agree it is a very useful tool for =20
everyone to become familiar with.

http://www.influxx.com/why-every-creative-needs-to-know-a-little-unix/


Adam Mercado
Influxx Media Production
Fullerton, CA

Moving Images. For Business
714=B0928=B09896
http://www.influxx.com
http://www.twitter.com/influxx
http://www.linkedin.com/in/influxx
http://influxx.tumblr.com/archive
http://www.flickr.com/photos/influxx


On Jul 9, 2014, at 7:50 PM, Robert W. Walker wrote:

> Console more or less keeps a running log in real time of all the
> processes on your Mac.  Each event is time-stamped.  In my case I =20
> noted
> several "disk 6s3 i/o error" entries, along with reams of other code I
> do not understand at all.  I checked Disk Utility for clues but it =20
> does
> not show the device ID of the drives, just what you named them so I =20=

> made
> the (incorrect) assumption "disk 6s3" was my boot drive.  Eventually I
> discovered that you can open Terminal, type "diskutil list" and it =20
> will
> return a detailed list of device ID's as well as their "names."  Aha.
> "Device disk 6" was that faulty Firewire drive.
>
> By the way, along the way I bought (again) Disk Warrior which was no
> help at all, booted into Safe Mode and ran the RAM hardware test
> overnight, bought MORE RAM in case the whole lot was failing, and =20
> backed
> up then wiped clean an SSD for the clean installation of the OS. It =20=

> was
> an expensive and time-consuming experience but I learned a lot.
>
> I have always shied away from Terminal; and never used Console in my
> life before a couple of weeks ago. But it turns out that with some
> digging around online you can find a load of useful troubleshooting
> techniques that do not put your machine in further harm's way.
>
> Robert W. Walker
> Los Angeles CA USA
>
>
>> -------- Original Message --------
>> Subject: Re: [AE] Lesson learned
>> From: "Allen Ellis" <AE-List@media-motion.tv>
>> Date: Wed, July 09, 2014 10:20 pm
>> To: "After Effects Mail List" <AE-List@media-motion.tv>
>>
>>
>> Wow. Thanks for the story. Any more insight into how you used the =20
>> console
>> to trace the problem to the disk i/o error? Sounds intriguing.
>>
>> --Allen
>>
>>
>> On Wed, Jul 9, 2014 at 9:20 PM, Robert W. Walker <AE-List@media-=20
>> motion.tv>
>> wrote:
>>
>>> About three weeks ago I went through a major day-and-a-half =20
>>> battle to
>>> get a Mac Pro 5,1 on OS 10.9.2 to behave. I was getting bizarre =20
>>> Finder
>>> crashes, infinite beachballs when trying to import any element at =20=

>>> all
>>> into AE, even Disk Utility freezing up.  I did a major update to my
>>> backups, did a clean install of Mavericks and reinstalled all =20
>>> apps and
>>> plugins one by one.  That took most of a day.
>>>
>>> However the machine was still intermittently unusable, even to =20
>>> the point
>>> of refusing to Shut Down properly.  Next thought was "bad RAM."  I
>>> started removing and swapping RAM sticks until I narrowed it down =20=

>>> to the
>>> one that seemed to be the culprit. Bam. Looking good again.
>>>
>>> Until today when the problem recurred. Long story short, through =20
>>> Console
>>> I traced the problem to a disk i/o error on an external Firewire =20
>>> drive.
>>> Console is pretty great. I took the drive off-line and everything =20=

>>> was
>>> back to normal.
>>>
>>> Huh. Machines.
>>>
>>> I learned that many symptoms can be caused by many things, not =20
>>> always
>>> the most "logical" or the first thing that comes to mind.
>>>
>>> Robert W. Walker
>>> Los Angeles CA USA
>>>
>>> +---End of message---+
>>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>