I check my Hackintosh computer’s disk with Disk Utility every now and then to make sure there are no problems. Usually it says the disk is okay. This time it said “
error: drec_val object (oid 0x8f62a): invalid type (0). fsroot tree is invalid.” Disk Utility also told me that it couldn’t repair it. I found some discussion boards online which say the only solution is to reformat the disk and restore from backup.
This is a problem.
I was issued a new MacBook Pro at work. As I copied my data to it and set up the applications I use, I decided to keep track of the apps I put onto it (as an iOS developer).
My MacBook Pro has a 500GB solid-state drive. (Technically 512GB, I suppose, but it reserves all the rest to replace blocks as they fail. I’m okay with that.) When I first got this computer, I decided to allocate 380 gigs of that to Mac OS, and the remaining 120 gigs to Windows, because I like being able to dual-boot into Windows when I want to help someone with Windows or play a game.
Turns out that I don’t use much storage on the Mac side; I prefer to keep most of my data on my desktop, where it’s more secure. But meanwhile, Windows games are big and I have a bunch of them (darn Steam sales), so I was running out of room on the Windows side.
So I decided to shrink the Mac partition and expand the Windows partition, to give them each 250 gigs.
The best backup software I’ve found for Windows is Acronis True Image.
Unfortunately, the software really sucks.
Let me illustrate the problem. I told Acronis (on their Facebook wall) that I want a simple “set and forget” backup that doesn’t require a lot of configuration and maintenance, and I asked what the latest version of their product can do for me. Their reply:
An incremental backup stores changes to the data against the latest backup. So you need access to previous backups from the same chain to recover data from an incremental backup. To clean up an older backup chain (Full backup + dependent incremental backups) you’ll need to create a new full backup as a base for next incremental backups. Here you can find different clean up schemes available in the custom backup scheme: http://www.acronis.com/…/document…/ATI2017/index.html… For your scenario I’d suggest using an option “Keep size of the backup no more than [defined size]” – to limit maximum size of the backup. After creating a new backup version, the program checks whether the total backup size exceeds the specified value. If it’s true, the oldest backup version will be deleted.
This is the year 2016. I shouldn’t have to deal with “full” versus “incremental” backups. I shouldn’t have to worry about what will happen when my backup disk fills up. I should just be able to plug in a backup disk, hit a button, and have the backup software take care of the rest.
I’ve always been somewhat compulsive about putting things in order. I remember as a kid waiting in line at stores, I’d pass the time by sorting and rearranging the products on the shelves – much to the amusement of the adults who felt I had a promising future as a stock boy.
All around us, it was as if the universe were holding its breath, waiting. All of life can be broken down into moments of transition or moments of revelation. This had the feeling of both.
I don’t want to count how many years it’s been since Babylon 5 went off the air, but quotes from it keep coming back to me. (Such a well-written piece of science fiction that was.) This has been a year of transition, and I’ve been so busy living it that I haven’t had the presence of mind to write about it.
It’s nice that Apple has bundled all the tools necessary to turn a Macintosh into a server (mail, web, file sharing, DHCP, DNS, &c.) into a $20 app store purchase. I think the Server version of Mac OS X used to cost $500, and the new low price really puts the power of a server into the hands of the masses.
Unfortunately, Apple has also dumbed down the whole server interface. I can see what they were trying for; they want to turn the experience of editing config files into the experience of clicking on something that looks like an on/off switch. Problem is, there’s still a need for server administrators and there’s still a need to know how to edit config files. It would be like buying a button for your car’s dashboard that says FIX IT and telling you, hey, congratulations, you’re a mechanic now! But if you press that button and nothing happens, then, well, you’re in trouble.
Mom once told me a story of when she was a little girl, and the kid down the street had a new battery-operated light on his bike. “I’m not supposed to use up the battery,” he said, but he proudly switched the light on and then quickly off again.
“Maybe that was the last time it will work,” Mom said, “maybe you used up the battery.”
“Nuh-uh!” the boy said, and switched the light on and off again.
“Maybe that was the last time,” Mom teased.
I love fixing up old computers. Who needs the latest-and-greatest if all you’re going to do is web surfing, email, and some light word processing? I’ve accepted donations of dozens of unloved computers around town, I’ve wiped them clean and put Ubuntu Linux on them, and I’ve given them new homes with families who need them. The new owners don’t mind much that Ubuntu can’t run Windows games or Windows viruses.
I’ve got a collection, in fact, of very old Mac computers. One of my favorite is a Mac IIfx, which was totally the boss of its day. 40MHz! “It can finish an infinite loop in twelve seconds!” people would say. “It takes seven HALT instructions to stop it!” I hear the Linux m68k project has come to life again; maybe someday I can put Debian on it.
I wish I knew as much about fixing cars as I know about fixing computers.
So, my first tech tip of this new blog.
I installed WordPress and customized a theme to match the rest of this site. (I used to do Enchanter.net entirely in hand-written HTML, but then I decided to “get with the times” and try using a template-based site-generation tool to do the work for me. In hindsight, I should have just continued to write the HTML by hand.) Everything went smoothly, but there was one hitch.
WordPress has a “Permalink Settings” page where I can change the URLs of my blog posts from something boring – “
https://enchanter.net/ao/?p=123” – to something more trendy like “
https://enchanter.net/ao/2013/04/sample-post/“. Problem is, to enable this, I had to either use a
.htaccess file with some rewrite rules in it, or else modify the server’s
httpd.conf with the rewrite rules.
There was much gnashing of teeth as I tried to figure out how to get this to work.