Tuesday, March 30, 2010

Drobo Pro, Mac OS X, and Firewire

Aargh.

I spent parts of several days diagnosing a problem connect a Mac XServe and a Drobo Pro. The Mac is running OS X Server, Snow Leopard, and the Drobo is up to date on firmware.

The problem is that there's an error with Fast Start firewire packets. The problem occurs when we're using FW 800, but not USB. I swapped cable, ports, etc; problem remained unsolved. I tried with a MacBook Pro (no error).

Now, after several days, Apple admits this is a known issue. It's happened with at least two different types of Mac hardware, and may be related to high amounts of RAM (we have 32GB in the XServe).

What's frustrating is that there is no public information about this. This is not an issue I could have known about, and Apple is not informing people inside enterprise tech support properly. This has also not been put in Apple's bugtracker (and AFAIK, Drobo doesn't have a public bugtracker).

Maybe, just maybe, someone will find this post and save some time. I can only hope.

Obviously, I will post more info if it becomes available. For now, as great as the Drobo is (and it was pretty much effortless to set up), it's not working with Firewire 800.

Wednesday, March 24, 2010

Counterfeit Intel Processors

This is just funny. This has a decent writeup of the story about Newegg selling counterfeit Intel Core i7 processors, but this story has the pics. It's actually not that surprising; these chips are heavily in demand. The retail market simply won't get them as quickly as the OEMs will. Apple is apparently not happy with the number they have received, and this is delaying the introduction of new the MacBook Pro. At least, that's the rumor.

Just to add to the trend, let's be clear that D & H was not NOT the source of the counterfeit chips.

Tuesday, March 23, 2010

Giving Up on Email Sorting

So I've gone from filer to piler, officially. I've just given up entirely on sorting emails. I can't keep up. OK, email, you win.

Drive Recovery

If you are reading this, which would surprise me, you probably know that I work in digital forensics. Now, that doesn't mean that I know how to recover a drive if it has physically failed. Give me the bits, and I can probably do something with it.

So I recently received a drive that, in transit (probably), had a head crash. Now, this shouldn't, in theory, happen, as the heads are physically parked (moved to a non-data area of the disk) when powered down. Who knows what happened? The disk might have not been powered down properly, or a normal fault could have happened at another time, or maybe I screwed up something.

Anyway, for the low, low price of about $2500, I'm having data recovered. I'm not going to say the name of the service until I have more info about how they work. If they are successful, I'm happy to promote them, but I don't want to say anything yet.

Ultimately, if they can recover the data, it's a surprisingly positive (or ominous, depending on who you are) sign, actually. A head crash is pretty severe when it comes to media failure.

I had a discussion with my boss the other day, leading to my statement about the HDD equivalent of Yucca Mountain. The comparison is not really fair, but here goes:

Somewhere, actually manywheres, there are thousands, tens of thousands, and more, hard drives. These hard drives have been pulled from computers in governments, corporations, and even computer manufacturers. These drives may or may not have sensitive data on them, but no one knows, or will really ever know. Because of the risk involved, they can't be disposed of properly. They contain both valuable elements (gold) and toxic elements (some of them). And no one really knows what to do with them.

There are, of course, several options:
* You could melt (slag) or grind the drive down. This is definitely the safest route, data-wise, but dangerous to be around, and expensive.
* You can physically erase each bit one or more times - this is pretty safe, as it's never been proven that you can recover much data (no given bit with much more than 50%). For old drives, this had to be done multiple times because each bit was actually quite a large space, and a more modern, precise head could potentially pull data, but newer drives (say, less than 10 years old), a single pass is sufficient. This is less safe, very time-consuming, but overall sufficient to erase a drive. If I were in a corporation, I would do this to all drives. Wiebetech makes a hard drive eraser; I'm waiting on mine, but they are one of the better manufacturers of forensic equipment, so if they say it works, I would generally trust them. I do wish they had digital displays, though, especially for problems. Old drives tend to fail.
* You can degauss the drive. This is environmentally safe, and despite dire predictions, probably safe. However, you need a moving magnetic field to do this, and it's not cheap. I've never seen this in action, nor seen a test of reliability.
* You could getting this really cool hard drive hole punch, which is what my boss recommends.

Ultimately, though, the interesting question is, can you destroy the data on hard drives cheaply, effectively, and without danger? Now, for an individual drive, this isn't an issue, but when an organization literally casts aside thousands of drives a year, it's an important issue.

NOTE: DO NOT TRY THIS AT HOME (except for DBAN)

Tuesday, March 2, 2010

Waiting on Apple Blues

So a short post, not really a post so much as a rant. Unheard of in blog-world. I really need a new computer, and for a variety of reasons that are not really of interest here, I decided to go with a Mac. Yay. Well, it serves my needs, except for one thing. I want a better processor than the ones they put in any of the current line of Macs (well, sorta-kinda-except for the Xeon in the Pro). The new Intel i5 has, in the common laptop mode, two Nehalem cores. Current technology? In a Mac? So, as of this date, I'm twiddling my thumbs, not so much because I like thumb-twiddling, but because I'm waiting for my personal Mac to finish, say, opening up a browser.