Shannon A. ([info]shannon_a) wrote,
@ 2008-11-19 00:11:00
Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Mac Attack
Well, I have a Mac again. I'll cross my fingers that that continues to be the case.

I don't even know what happened exactly. I rebooted the thing last Tuesday because it was getting slow, and when it came back up it would no longer run Mozilla Thunderbird, Adobe Illustrator, Adobe Photoshop, or Microsoft Anything.

Now some folks might consider their computer not running Microsoft Anything a blessing, but it was kind of a problem for me, especially since I'm still trading chapters of the iPhone Book with copy editors and proofreaders (and writing some new iPhone articles too, for that matter). At least it happened after I finished the main text of the book. The day after I finished the main text of the book, as it happens.

Fortunately I have a Time Machine running on the Mac. So I time-machined back to the day before the problems happened (after, y'know, trying to fix the problem, because computers shouldn't just totally go wacky, irreparably like that). Afterward, the machine remained stable for approximately two minutes. Then it started failing to run every frickin' program *and* when I rebooted it, it got into a reboot-crash infinite loop.

Nice.

So I time machined back further, to October 31, then I used Time Machine to restore just the Documents directory from yesterday. Thus far, it's been running solidly for four or five hours.

I probably lost a few things in other directories, like local mail, but if I notice anything I can't live with, I suppose I can try to get that back from Time Machine too.

I'm *still* very suspicious of the Mac. A machine that fails under super mysterious conditions twice is very untrustworthy. I've already checked the memory, but if it happens again, I'll suspect the disk (though that comes up OK on tests too).

Well, at least nothing was lost--other than many hours of my time.

I must say, using the older Windows machine for the last week, with its teeny screen felt like being in prison.



(Post a new comment)


[info]davidgoldfarb
2008-11-19 12:27 pm UTC (link)
A while ago my iMac was doing some similar things -- having programs crash on startup, having trouble booting, and so on. It seemed to happen after a restart. One time reinstalling the OS helped, another time restoring from Time Machine backup did. Hasn't done it recently.

(Reply to this) (Thread)


[info]shannon_a
2008-11-19 05:43 pm UTC (link)
So much for the vaunted stability of Macs.

(Reply to this) (Parent)(Thread)


[info]viktor_haag
2008-11-19 08:44 pm UTC (link)
Of all the computer operating systems I have used over the past decade, OSX is the second most stable, behind Solaris. Portions of the Linux system I used were more stable, but portions of it are waaaaay less stable.

I have had torch and rebuild incidents with OSX perhaps three times over the past decade. Two of those were strictly hardware related incidents, and one was a file system corruption issue which could have been caused by a software problem or by a power-outage causing a sudden system halt.

I have had other, minor stability issues with OSX over that time; most have been caused by misbehaving applications, and once the causes were determined I was able to avoid them (for example, the NVIDIA GPU bug that seemed to be exercised only by iTunes in very particular circumstances, which has since, apparently, been fixed).

(Reply to this) (Parent)


[info]viktor_haag
2008-11-19 02:11 pm UTC (link)
That sounds suspiciously like disk corruption that's torched some of your shared framework libraries or other such sensitive common system files. Nothing usefully informative in your console logs?

Have you run Disk Utility or some other more serious disk checker to verify the file system and the integrity of the disk hardware?

If the disk checks out OK, and the problems persist, then it could also end up being (::shudder::) more serious, and increasingly less intermittent hardware issues (such as a soldering crack somewhere that's widening, faulty RAM sectors, etc).

* Is your TimeMachine on a separate physical volume (he says hopingly?)

* I'd be tempted to back up all the data, reinstall the OS from scratch, and then reinstall the apps, and restore your data. Yes it's fairly drastic, and probably will take you the better part of a day, but it should also get you to the point where you have a fresh software system on the machine and can start narrowing down the cause.

(Reply to this) (Thread)


[info]shannon_a
2008-11-19 05:43 pm UTC (link)
Yeah, I figured something with the disk, hopefully just one time corruption, which is why I went out to the older backup. In any case, the disk did show clean in Disk Utility, but I haven't run anything more serious.

The Time Machine is a separate device, which is why I haven't run around yelling screaming. The next step is definitely an OS restore from scratch, but I'm hoping this one stays stable.

(Reply to this) (Parent)(Thread)


[info]viktor_haag
2008-11-19 06:14 pm UTC (link)
OSX's file system is reasonably resistant to the kind of shared library corruption that shows up in Windows, that flakiness like this that I've seen in the past has nearly always signalled badness, I hate to say.

I guess the TIme Machine complete restore is actually a slicker way to do a wipe-and-reinstall, as long as you don't mind seeking backwards for one that "works".

I suspect that it's quite useful to have a notable copy of a machine with "fresh OS plus all Software Updates plus fresh apps installs plus all apps updates" which you can then archive and use that as a starting point for re-imaging. It occurs to me that "bookmarks" in TimeMachine might actually be rather useful for such things, but I guess writing down a date/time would also work... 8)

(Reply to this) (Parent)


Create an Account
Forgot your login or password?
Login w/ OpenID
English • Español • Deutsch • Русский…