From: "Robert W. Walker" Received: from p3plwbeout04-01.prod.phx3.secureserver.net ([72.167.218.222] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5522779 for ae-list@media-motion.tv; Thu, 10 Jul 2014 04:50:51 +0200 Received: from localhost ([72.167.218.245]) by p3plwbeout04-01.prod.phx3.secureserver.net with bizsmtp id QSqq1o0085JG3DC01SqqJG; Wed, 09 Jul 2014 19:50:50 -0700 X-SID: QSqq1o0085JG3DC01 Received: (qmail 21953 invoked by uid 99); 10 Jul 2014 02:50:50 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Originating-IP: 172.250.73.93 User-Agent: Workspace Webmail 5.7.1 Message-Id: <20140709195049.89259f98f291d771214680e8971719cb.5533ed0db5.wbe@email04.secureserver.net> To: "After Effects Mail List" Subject: RE: [AE] Lesson learned Date: Wed, 09 Jul 2014 19:50:49 -0700 Mime-Version: 1.0 Console more or less keeps a running log in real time of all the=0Aprocesse= s on your Mac. Each event is time-stamped. In my case I noted=0Aseveral "= disk 6s3 i/o error" entries, along with reams of other code I=0Ado not unde= rstand at all. I checked Disk Utility for clues but it does=0Anot show the= device ID of the drives, just what you named them so I made=0Athe (incorre= ct) assumption "disk 6s3" was my boot drive. Eventually I=0Adiscovered tha= t you can open Terminal, type "diskutil list" and it will=0Areturn a detail= ed list of device ID's as well as their "names." Aha. =0A"Device disk 6" w= as that faulty Firewire drive.=0A=0ABy the way, along the way I bought (aga= in) Disk Warrior which was no=0Ahelp at all, booted into Safe Mode and ran = the RAM hardware test=0Aovernight, bought MORE RAM in case the whole lot wa= s failing, and backed=0Aup then wiped clean an SSD for the clean installati= on of the OS. It was=0Aan expensive and time-consuming experience but I lea= rned a lot.=0A=0AI have always shied away from Terminal; and never used Con= sole in my=0Alife before a couple of weeks ago. But it turns out that with = some=0Adigging around online you can find a load of useful troubleshooting= =0Atechniques that do not put your machine in further harm's way.=0A=0ARobe= rt W. Walker=0ALos Angeles CA USA=0A=0A=0A> -------- Original Message -----= ---=0A> Subject: Re: [AE] Lesson learned=0A> From: "Allen Ellis" =0A> Date: Wed, July 09, 2014 10:20 pm=0A> To: "After Effect= s Mail List" =0A> =0A> =0A> Wow. Thanks for the st= ory. Any more insight into how you used the console=0A> to trace the proble= m to the disk i/o error? Sounds intriguing.=0A> =0A> --Allen=0A> =0A> =0A> = On Wed, Jul 9, 2014 at 9:20 PM, Robert W. Walker = =0A> wrote:=0A> =0A> > About three weeks ago I went through a major day-and= -a-half battle to=0A> > get a Mac Pro 5,1 on OS 10.9.2 to behave. I was get= ting bizarre Finder=0A> > crashes, infinite beachballs when trying to impor= t any element at all=0A> > into AE, even Disk Utility freezing up. I did a= major update to my=0A> > backups, did a clean install of Mavericks and rei= nstalled all apps and=0A> > plugins one by one. That took most of a day.= =0A> >=0A> > However the machine was still intermittently unusable, even to= the point=0A> > of refusing to Shut Down properly. Next thought was "bad = RAM." I=0A> > started removing and swapping RAM sticks until I narrowed it= down to the=0A> > one that seemed to be the culprit. Bam. Looking good aga= in.=0A> >=0A> > Until today when the problem recurred. Long story short, th= rough Console=0A> > I traced the problem to a disk i/o error on an external= Firewire drive.=0A> > Console is pretty great. I took the drive off-line a= nd everything was=0A> > back to normal.=0A> >=0A> > Huh. Machines.=0A> >=0A= > > I learned that many symptoms can be caused by many things, not always= =0A> > the most "logical" or the first thing that comes to mind.=0A> >=0A> = > Robert W. Walker=0A> > Los Angeles CA USA=0A> >=0A> > +---End of message-= --+=0A> > To unsubscribe send any message to = =0A> >