From: "aelist" Received: from atl4mhob14.myregisteredsite.com ([209.17.115.52] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5522793 for AE-List@media-motion.tv; Thu, 10 Jul 2014 05:18:47 +0200 Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s6A3IjMs032377 for ; Wed, 9 Jul 2014 23:18:45 -0400 Received: (qmail 29049 invoked by uid 0); 10 Jul 2014 03:18:45 -0000 X-TCPREMOTEIP: 58.104.31.172 X-Authenticated-UID: russ@maehl.com Received: from unknown (HELO ?10.1.1.5?) (russ@maehl.com@58.104.31.172) by 0 with ESMTPA; 10 Jul 2014 03:18:45 -0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_87DD5A22-4AF9-41B6-B054-A5798F3ACB35" Message-Id: <00CF6FFE-8E95-4B65-B357-04DEA149D538@maehl.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [AE] Lesson learned Date: Thu, 10 Jul 2014 13:18:53 +1000 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.1878.6) --Apple-Mail=_87DD5A22-4AF9-41B6-B054-A5798F3ACB35 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 10 Jul 2014, at 12: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 = 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 = does > not show the device ID of the drives, just what you named them so I = made > the (incorrect) assumption "disk 6s3" was my boot drive. Eventually I > discovered that you can open Terminal, type "diskutil list" and it = will > return a detailed list of device ID's as well as their "names." Aha.=20= > "Device disk 6" was that faulty Firewire drive. >=20 > 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 = backed > up then wiped clean an SSD for the clean installation of the OS. It = was > an expensive and time-consuming experience but I learned a lot. >=20 > 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. >=20 > Robert W. Walker > Los Angeles CA USA >=20 >=20 >> -------- Original Message -------- >> Subject: Re: [AE] Lesson learned >> From: "Allen Ellis" >> Date: Wed, July 09, 2014 10:20 pm >> To: "After Effects Mail List" >>=20 >>=20 >> Wow. Thanks for the story. Any more insight into how you used the = console >> to trace the problem to the disk i/o error? Sounds intriguing. >>=20 >> --Allen >>=20 >>=20 >> On Wed, Jul 9, 2014 at 9:20 PM, Robert W. Walker = >> wrote: >>=20 >>> About three weeks ago I went through a major day-and-a-half battle = to >>> get a Mac Pro 5,1 on OS 10.9.2 to behave. I was getting bizarre = Finder >>> crashes, infinite beachballs when trying to import any element at = 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 apps = and >>> plugins one by one. That took most of a day. >>>=20 >>> However the machine was still intermittently unusable, even to 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 to = the >>> one that seemed to be the culprit. Bam. Looking good again. >>>=20 >>> Until today when the problem recurred. Long story short, through = Console >>> I traced the problem to a disk i/o error on an external Firewire = drive. >>> Console is pretty great. I took the drive off-line and everything = was >>> back to normal. >>>=20 >>> Huh. Machines. >>>=20 >>> I learned that many symptoms can be caused by many things, not = always >>> the most "logical" or the first thing that comes to mind. >>>=20 >>> Robert W. Walker >>> Los Angeles CA USA >>>=20 >>> +---End of message---+ >>> To unsubscribe send any message to >>>=20 >=20 > +---End of message---+ > To unsubscribe send any message to >=20 --Apple-Mail=_87DD5A22-4AF9-41B6-B054-A5798F3ACB35 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On 10 Jul 2014, at 12:50 = pm, Robert W. Walker <AE-List@media-motion.tv> = 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 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 does
not show the device ID of the = drives, just what you named them so I made
the (incorrect) assumption = "disk 6s3" was my boot drive.  Eventually I
discovered that you = can open Terminal, type "diskutil list" and it 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 backed
up then wiped clean an SSD = for the clean installation of the OS. It 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 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-motion.tv>wrote:

About three weeks ago I went = through a major day-and-a-half battle to
get a Mac Pro 5,1 on OS = 10.9.2 to behave. I was getting bizarre Finder
crashes, infinite = beachballs when trying to import any element at 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 apps and
plugins = one by one.  That took most of a day.

However the machine = was still intermittently unusable, even to 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 to the
one = that seemed to be the culprit. Bam. Looking good again.

Until = today when the problem recurred. Long story short, through Console
I = traced the problem to a disk i/o error on an external Firewire = drive.
Console is pretty great. I took the drive off-line and = everything was
back to normal.

Huh. Machines.

I learned = that many symptoms can be caused by many things, not 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>


= --Apple-Mail=_87DD5A22-4AF9-41B6-B054-A5798F3ACB35--