Monthly Archives: January 2004

More info…

Here's all I know now. Looks like I'll get some stuff back. They tell me no one has brought them this much data on a single drive before to try and restore… I guess only a lunatic puts critical data on a high-volume drive! Anyway, this is what's happening now:

When we attempted to "mirror" the drive (sector by sector cloning to one of our own devices), we found the drive to be unstable, allowing intermittent access. This means that the drive sometimes starts up and seems to operate normally for a short (possibly very brief) time, then fails. We encountered many read errors in the process, which indicates the permanent loss of information on some parts of the drive. These types of problems affect file information (where the parts of a file begin and end) and directory information (names and addresses of files) and could affect some data segments (the actual contents of files).

We feel that a degree of recovery in this case may be possible. At the end of the process, we will need to do a logical reassembly, which means to try to put the files and directories back together, attempting to get it as close as possible to its original configuration. If this succeeds, we then take a look to see what we have, and whether it matches the data required.

Fee If Data Required is Recovered: CAN $1600
Time Estimate: 4 days

Update

Now you know as much as I do on the subject.

Waiting for a phonecall

In a few hours I get the good or bad news about that drive. Until then I have a lot to drink*.

Since most people don't really know the history of how and why the US got itself involved in WWI, I thought it would be worth linking to this article on the subject. As you probably know, America came in after the Germans sunk the British passenger ship Lusitania, which was enough to break the US's neutrality.

As always, and as it still is today, the people of America didn't want war, but because they were good but uninformed people, hearing that civilians were being attacked by a warlike country got them engaged and millions of good Americans died in the war and subsequent ones doing what they thought was right.

But what the government didn't tell them is that the Lustiana was being used to secretly shuttle US-produced ammunition from Bethlehem Steel (the Haliburton of WWI) to Britain, using civilian passengers as a “shield” — note that this was a corporate action, not a government one (the government decried it, but even back then, corporations held more power than politicians). Not only that, but this was after they'd done a study to find out whether doing this would trick the public into backing war if the Germans attacked a passenger ship.

The rest is history, and Charles Schwab (owner of Bethlehem Steel) and his fellow warmongers went on to become the richest men in America (albeit some were felled by the depression). Given that WWI begat WWII which begat the Cold War, American corporate profiteering becomes a very bloody thing — and if you really want to upset yourself, start researching exactly what started the war and exactly what involvement American corporations had. If you really want to upset yourself even more, take a look at who these corporations have consistently sold military technology to — both sides. Haliburton as well sells to “the enemy” and doesn't hide it.

David Kay (Bush's WMD guy) has now said that nearly all WMD claims made by the US are wrong. Not only does US intelligence imagine WMDs in countries that they don't exist, but they've totally missed active manufacturing and distribution programs in other nations. Again look at who's walking away the winner (the corporation) and who's walking away the loser (the American people)… This has to end.

Finally, let me mention this tear-jerker: Girl salutes daddy killed in Iraq. Just brings back little JFK Jr. memories, doesn't it? But if you'd like to get especially sad, read how he died: another soldier tripped and shot him by accident.

Guess what that means?

The widow and family will probably be inelligible for full veterens benefits, since he didn't die in combat, it was just an unrelated accident….


* Not really

Toys

Since there's some confusion I'll just really quickly clarify: This error (entries below) poses no risk to any of the data on IAM, and IAM is always backed up in real time so this type of problem could never hurt your pictures, diaries, or forums here.

I did install some new gear today… Nothing too exciting, but stuff that was “on the list”. In the picture on the left you can see that my home network is now a gigabit network (it was 10/100 until now). I'm going to install a RAID NAS device to backup my files and Rachel's, and now that I'm on highspeed I might set up a decent automated archive/encrypt/upload tool so I can do secondary sourcecode backups on the other side of the planet from here in case America gets itself nuked as the prophet says will happen.

As you can see in the picture on the right, I added speakers to the computers that need them. The one in the shot (something or other by Logitech) has an external volume control which seems really useful although I'm sure it'll take a while to get over the instict to do it onscreen. Anyway, not particularly exotic or exciting technology but it makes my day a bit easier.

"Mr. [Class 100] Clean [Room]

INCOMING EMAIL (ie. @iam.bmezine.com) FUNCTIONS ARE OFFLINE UNTIL I CAN GET MY DRIVE REPAIRED. I will have more information on this and the other damage within 24 hours. @iam.bmezine.com email is currently the only publicly accessible system that has been damaged (all other damaged systems are internal).

Well, here's where I was this afternoon. Even though it's a zero-visibility blizzard here with snow blowing at 60 kph I had to drive out to Markham to deliver the seized up drive. Not fun. Given how much money I've invested in buying fully redundant hardware for IAM (because I know how many people would be hugely emotionally hit if everything here disappeared overnight), you'd think I'd invest the same amount of money on myself, wouldn't you?

I do have backups of course, but since all the moving around I've been both sloppy and doing aggressive development so on some projects I stand to lose a lot of data and code. Anyway, I'll have more info tomorrow… Keep your fingers crossed.

Oh — while I remember — I've got lots of space in my [internet] cage so for IAM we're probably just adding a second RAID rack (not cheap, but safe). This should allow me to upgrade IAM to the new drives with only an hour or two of downtime at the most (however long it takes to copy 60 gig of data). So at least that's some good news. However, if I can't recover that drive, it becomes difficult because to recompile for the new set up I'd have to “roll back” IAM to a stable backed up codebase, which would mean losing all of the the features I've added lately (and rebuilding them from scratch).

So like I said: fingers crossed please!