Drobo customer support is trying but is coming up empty. Now I’m trying Data Rescue 3 to read data off the Drobo. DiskWarrior can’t see the Drobo because it isn’t mounted, but Data Rescue 3 can.

In fact, DiskWarrior also doesn’t see the Drobo when it’s run stand-alone off their DVD! I tried this on my wife’s iMac. OS X sees the disk (but does not mount it), Disk Utility lists it and allows me to try a Verify Disk and Repair Disk, but DiskWarrior doesn’t see it. I’ll try their tech support next.


I’m migrating my files and apps to my new MacBook Pro. A highly anticipated improvement was connecting my Drobo S to a USB 3.0 interface, instead of my previous laptop’s USB 2.0 bus.

During my migration, the Drobo Dashboard advised me that a Drobo firmware update was available. I did the update, which -boom- bricked my Drobo.

After trying rebooting, power-cycling the Drobo, and plugging it into the other USB socket, I’m at a point where Drobo Dashboard says the Drobo is healthy. But OS X won’t mount it. Disk Utility says:

Unable to bootstrap transaction group 6000: cksum mismatch
No valid commit checkpoint found
The volume xxxxxxx was found corrupt and needs to be repaired.
Problems were found with the partition map which may prevent booting
Error: This disk needs to be repaired. Click Repair Disk.

I then run Repair Disk, and it tells me the same thing! So Repair Disk can’t repair the disk!

I bought DiskWarrior (for $109, I’ll have you know) but it can’t repair a disk that isn’t mounted. They’ll ship me a physical CD-ROM of my purchase, so I can try booting from it. Oh, but wait, my MacBook Pro/Retina doesn’t have a CD-ROM drive!

I am not a happy camper.


We license a vendor’s services for corporate information, like annual revenue and office locations. Their name shall be kept confidential in this story.

We access their API via http calls. They call it a REST API. But like 95% of the “REST” APIs in the world, it’s not REST at all, and in fact nowhere near REST. The term “REST” has been corrupted to be become synonymous with, “web API”.

But whatever. It’s an API accessed with http calls.

One of service calls has a parameter called, “countryCode”, which was documented as an ISO 3166 country code.

Read More


I’m not doing much blogging lately. Obviously.

I’ve spent lots of time at work. We’re doing a big release in January, and there’s no end of bugs to fix, features to tweak, and QA logs through which to grep. It’s not a death march by any means, but it is, I admit, a bit of a grind. Far more time is being spent on technology integration than is ideal, and I had expected.

It’ll be good to get it behind us. I’m looking forward to being able to make some strategic technology and process choices afterward.

I’m looking forward to replacing my 2008-vintage MBP at home with a new model, probably in February.

End of report.


Boy, what a roller coaster! Shortly after opening a position for a Senior Devops engineer, we had a funding “event” and now the opening’s gone. What’s worse, I had to lay off one of my developers, right before before the end-of-year holidays. It was stressful for all involved.

We’re doing some interesting things with name relationships at work, and these present fun development challenges. I’m trying to spend as much time as possible in Emacs, because the less-fun work issues always occur when I’m not coding.

I upgraded our codebase to version 3 of Celery, just to get us off version 2. I’m still hankering to replace Celery, but it must have known it was living on borrowed time because it’s been behaving lately, so I’ve decided to fry some bigger fish. But the moment Celery starts acting up again…

I just turned 55. How the hell did that happen?!?

Follow

Get every new post delivered to your Inbox.

Join 1,588 other followers