While I'm on my blog break, more edited versions of my Twitter posts from the past week, newest first:
Labels: amazon, apple, backup, birthday, cancer, film, geekery, linksofinterest, music, news, olympics, photography, politics, religion, science, space, television, twitter
A few weeks ago, I replaced the old wireless router in our upstairs den with a new Apple AirPort Extreme base station, which has generally worked great. One extra benefit of the design is that, like Apple's similar Time Capsule, I can use it as a wireless backup device device by hooking up an external USB hard disk, like this:
The disk I use is a 500 GB Western Digital MyBook, perched to the left of the base station itself. If you look closely at the photo, you'll notice that the disk enclosure is sitting on a folded cloth napkin.
Here's why. The shelf all that networking gear sits on is made of light wood, and sits loosely on a wooden lip around the edges of the inside of the den closet. The other side of the closet's back wall is the south wall of our bedroom.
So, after I set up automatic backups for our various Macs using Time Machine and other tools (apparently not officially supported in this setup, by the way!), whenever the hard drive was active (especially at night), our bedroom wall would rumble disconcertingly as the disk mechanism chugged away. The shelf and the closet drywall were acting as a big soundbox amplifier.
And so, the napkin, my half-baked attempt to damp down the vibrations from the disk mechanism. It sort of works. Now, when the drive is active, the wall makes something more akin to subtle stomach-growling noises, rather than louder rumbling. During the day, that's fine, but at night it's still prone to keeping us awake.
The temporary solution has been to make sure backups occur during the day when it doesn't bother anyone. But I still must unhook the USB drive at night to avoid the grumblies, during what seem to be random administrative disk accesses (perhaps search indexing) that occur anyway from time to time. But I'd rather not do that. I'm considering putting some foam under the edges of the shelf itself, or maybe moving the whole setup to different, less resonant part of the closet.
Wow, this sure is a first world problem.
Labels: apple, backup, geekery
A bunch of stuff I've been accumulating over the past few months:
Labels: apple, backup, band, blog, environment, extremesports, food, google, linksofinterest, macosx, microsoft, music, publicspeaking, web
This site runs on Blogger, as it has for more than seven years, but if I were starting over again today I'd probably use WordPress. That's what I recommend to my friends and relatives, so that other sites I work with, such as Simon's, my wife's podcast (as well as her personal blog), and Inside Home Recording all use it.
If you use the free WordPress.com hosting service, all maintenance and upgrades are handled for you by the fine folks who run it. But if, like me, you're reasonably geeky and need the extra customization available by running WordPress on your own server, the main hassle has been that, when a new version of WordPress comes out, upgrading the software involves:
I've gotten reasonably good at that, but it's still time consuming, especially for multiple sites. Today, while surfing around feeling gross from chemo side effects, I read about the Automatic Upgrade Plugin (via Scott Beale on Twitter). It does all of that stuff with only a few clicks.
I tried it on two websites without a hitch, even using the Automated Mode that avoids the multi-screen, "Here's the next step, CLICK HERE if you're sure you want to proceed" process—with hardly a hitch.
Then, confident, I proceeded to the third site, Inside Home Recording, again in Automated Mode, got almost all the way through, and encountered the dreaded "500 Internal Server Error" page. I tried rolling back to my previous installation of WordPress manually. No dice. I noticed even the IHR forums (which use different software) were dead, which was mysterious and a bit freaky. And when I tried putting a generic "Sorry I broke the site" HTML page at index.php or index.html at the root of the site, it still didn't work. Yikes! I'd blown up the whole website!
I had a hunch, and took a peek at the invisible .htaccess file. That's a plain old text file sitting on the IHR web server (which I think is in Texas). The ubiquitous Apache web server software it's running uses .htaccess as a list to answer the question, "What do I do with stuff on this machine when I sent it out to the Web?" It seems that either WordPress or the Automatic Upgrade plugin had added some extraneous stuff to the end of that file. I deleted the extra text and, bingo, IHR was back up.
Having rolled back to the older version of WordPress, I made sure I had proper backups again (I remind you, back up, back up, back up your stuff), then tried the Automatic Upgrade plugin once more, but this time in Manual Mode (i.e. confirmed each step). No problems on this second attempt, and IHR is spiffed up with the latest software release.
Elapsed time from upgrade to blow up to fix up? Less than ten minutes. Sometimes I'm glad I have some web-fu when I need it.
Labels: backup, blog, family, friends, geekery, insidehomerecording, lipglossandlaptops, podcast, software, web
It turns out that my dead hard disk is still well under its five-year warranty, and that Seagate, the manufacturer, has an efficient online return system that helped me diagnose and then set up a return merchandise authorization (RMA) for it, including printing a shipping label for me.
So rather than go through the rigamarole of trying to rescue any data from the drive (as far as I can tell, it's not even spinning up), I mailed it off to Ontario a couple of days ago, and Seagate will send me a new replacement that I can drop in its place. In the meantime I'm using the stock MacBook hard disk, and it's working fine.
Because of my backup regimen, I lost so little data that all I've had to do is go through a few pages of my Flickr photos and re-import the missing ones into iPhoto—nothing else critical is missing. At least not that I've discovered so far.
So I should have a new drive to put into the MacBook next week, and I can use the one I have now once again as an external backup. One thing I do need to do is take some of my recent backups offsite, because right now I'm protected against failures, but if we get burglarized or the house burns down, important data could still be at risk.
You should do the same with your backups. You do have backups, don't you?
Labels: apple, backup, geekery, macbook, repairs, seagate
I thought that a few months ago, when my MacBook laptop finally returned from getting a new heat sink, fan, and battery, it would be stable. But no. Today I was working away, just having uploaded a bunch of photos to Flickr, when the MacBook froze up, which is unusual. I rebooted it.
Click click, said the hard disk. No booting. Grey screen, as if there were no disk inside at all. Not good. This disk is completely invisible to the utilities I own, as if it wasn't even there. I have backups, and very little data on the drive doesn't exist somewhere else, so that's not my worry—I learned my backup lessons years ago.
But it is certainly annoying. The 100 GB, 7200 rpm SATA disk drive is just over a year old: I installed it when I bought the MacBook, putting the stock drive in an external USB housing. It should have lasted much longer than this, but I suspect that all the nasty sudden power shutdowns with the battery problems I had may have damaged it, so that it decided to die today.
I'm typing on the MacBook now, having restarted from my external FireWire backup drive. I've reinstalled the original stock 80 GB, 5400 rpm hard drive and am copying over my data files so that it will work again. It should be in relatively normal shape later tonight.
But I'm not giving up on the bigger, faster drive yet. I don't trust it, but I want to see if I can bring it back to life again. The excellent DOS-based utility SpinRite apparently performs miracles on dead drives like that quite regularly. My dad owns a copy, but it's not intended to run on Macs, and sure enough, when I tried booting his CD on the Intel-based MacBook, it started up fine, but did not recognize the keyboard, so I couldn't do anything.
I'm going to see if I can get a SATA-to-IDE adapter to hook up the disk to one of my dad's Windows PCs, which will run SpinRite and may be able to get the disk working again.
Regardless, I will probably have to get another new internal drive (maybe a bigger one now, 160 GB or 200 GB) as the main one for this machine in the long run. I like this laptop and it has done great work for me, but it's sickly, to be honest.
Labels: apple, backup, geekery, macbook, repairs, spinrite