whrrr whrrr whrrr
Nov. 15th, 2013 10:03 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jazzfishWednesday was Wednesday: much-needed brain-off-time, counseling appointment, LG&S game that ran like the good parts of worldbuilding with a few 'what to do now' hiccups here and there. More downtime would have been good, I think; I should have gone ahead and taken the rest of the week off work. Oh well.
Thursday I opened Twitter for the first time in two weeks, and clicked on a link, and was rewarded by my first exposure to a kernel panic, OSX's equivalent of the Blue Screen Of Death. So I finally yanked the problematic memory chips and replaced them with the old good ones. This prevented any future problems but didn't solve the current one, namely: the machine hemmed and hawed and refused to exit command-line mode ("single-user mode").
I let it run for several hours, hoping it would come to its senses. I gnashed my teeth and tore my hair and poked the internet and determined that the likely culprit was a corrupt code-signing authentication database. (Can't verify that any programs are what they claim they are, so it refuses to run them. This includes system processes.) I called Apple Support and was told it would be $19 for phone help. A reasonable amount, given that I bought the machine over three years ago, but still, argh. Eventually it occurred to me that I've got a recentish Time Machine backup. So I spent another couple of hours figuring out how to pull the handful of new/updated files onto a USB stick from the command line, and then told it to Restore From Backup.
That ran all night. This morning, barring some reinstalling of applications and rejiggering of preferences that inexplicably didn't get saved, everything seems to be working fine. And I've got an RMA for the bad memory and will be sending that out today.
Could have been much worse. Moral: always, always, always back up your data.
... and I had a bunch of other stuff I wanted to write about, too. Later.
Thursday I opened Twitter for the first time in two weeks, and clicked on a link, and was rewarded by my first exposure to a kernel panic, OSX's equivalent of the Blue Screen Of Death. So I finally yanked the problematic memory chips and replaced them with the old good ones. This prevented any future problems but didn't solve the current one, namely: the machine hemmed and hawed and refused to exit command-line mode ("single-user mode").
I let it run for several hours, hoping it would come to its senses. I gnashed my teeth and tore my hair and poked the internet and determined that the likely culprit was a corrupt code-signing authentication database. (Can't verify that any programs are what they claim they are, so it refuses to run them. This includes system processes.) I called Apple Support and was told it would be $19 for phone help. A reasonable amount, given that I bought the machine over three years ago, but still, argh. Eventually it occurred to me that I've got a recentish Time Machine backup. So I spent another couple of hours figuring out how to pull the handful of new/updated files onto a USB stick from the command line, and then told it to Restore From Backup.
That ran all night. This morning, barring some reinstalling of applications and rejiggering of preferences that inexplicably didn't get saved, everything seems to be working fine. And I've got an RMA for the bad memory and will be sending that out today.
Could have been much worse. Moral: always, always, always back up your data.
... and I had a bunch of other stuff I wanted to write about, too. Later.