Author Archives: troll

RAID Sadness

In the world of high powered computing there are almost as many creative ways to squeak a little more out of your computer as there are people out there to think of them. Some people happily put their computer at risk by forcing its parts to operate faster than they were designed to in a method known as overclocking. Others take the road of simply spending huge amounts of money to stay on the bleeding edge of hardware. With the latest generation of CPUs running as high as $1500 a pop, that can become an expensive pattern to follow very quickly. Truly creative users see ways to stay within the bounds of reason financially and while maintaining some amount of hardware stability.

One way to go about that is to simply add a second video card, assuming you have a motherboard that allows it. Another is to upgrade your hard drives to some form of RAID array to make the load times of your games or your overall throughput of data way higher. A RAID array is basically just a collection of hard drives working together as one. An expensive alternative to RAID would be a relatively new device known as a solid state disk drive (SSD). They are way lower in capacity but make up for that shortcoming by being both way faster and way more expensive. To RAID some SSD’s together would be terrifyingly fast, but may exceed the national deficit in purchase price. Today’s story is about my RAID array.

Not feeling especially wealthy at the moment, and thus not inclined to run out and drop $800 on a wimpy 32GB of SSD even if it is way faster, I decided to pick up a pair of 750GB hard drives and build them into a nice RAID array. The goal was a single 1.5TB striped volume for only $240. My motherboard supports up to 6 SATA devices and has build in RAID support for those devices. Prior to adding the 2 new drives I was using only 3 of the 6 SATA devices I could support. This seemed to me to be the easiest and most cost effective way to beat a little more horse power out of my computer, with the added advantage of huge amounts of extra space.

Installing the drives was the typical pain in the butt that comes along with the process of trying to make all the wires in a computer lay in friendly places without being eaten by cooling fans. Once they were in though I figured I was only a few minutes away from enjoying my new speed and storage capacity. I fired up the BIOS, enabled RAID for the new drives, saved my settings, entered the RAID config, created a striped volume, saw on the screen a nice new striped 1.5TB array that was reported as healthy, exited the RAID program, and saw a gray blinking cursor.

That’s all I saw. Ever.

Wait for a while. Reboot over and over. Repeat every imaginable permutation of the configuration steps. It didn’t matter what I tried, my computer finished it’s power on self test (POST) and left me staring at a blandly colored short horizontal line blinking at regular intervals. The theory was that Windows itself was getting confused, but that was really hard to prove since I couldn’t even get the computer to boot.

Eventually, frustrated that I would never in fact stumble on to the pattern of configurations that would allow my computer to work like a computer again, I decided to turn off RAID and see how it all went. No problems, all the way into Windows, but with 2 extra 750GB hard drives. While this clearly worked at giving me more hard drive space, it failed miserably at getting the speed improvements I was looking for. So I began downloading improved drivers for Windows and new BIOS for my computer to attack the problem from as many sides as ended up being required. New drivers installed and BIOS tucked away on a USB thumb drive, I rebooted a few times to see if I could make Windows happy with RAID enabled.

More with the gray blinking cursor of extreme sadness. Well, at this point it was time to bring out the really big guns. Time to flash the BIOS to see if there was anything I could do from that perspective as far as making this project reach its finish line. Using the BIOS flash utility conveniently built right into the BIOS, I confirmed my BIOS, confirmed the BIOS I was about to install, let it install, successfully validated it, and watched happily as my computer rebooted. Except it didn’t come back.

Nothing happened. The computer didn’t POST, it didn’t beep, it didn’t show anything on the monitor, just nothing. I rebooted a bunch of times. I tried to turn off the power supply. I even popped out the battery. I was stuck, and my computer was now better at being a doorstop than a computer. This adventure in sadness had just taken an unexpected turn to downright terribleness. I was left with no choice. I called up Asus and waited on hold for over 30 minutes to ask them what to do. They provided me a specific pattern to follow involving the power supply, a jumper, and the battery. I followed it to the letter, and powered up my computer again. This time with it doing things it was supposed to do and the newly installed BIOS was there waiting for me.

Even with RAID enabled I no longer got stuck at the gray blinking cursor of death. This adventure however isn’t over just yet. Windows would boot up, but the RAIDed drives were simply missing. There were only a few unknown devices in the hardware manager to indicate that the computer knew they existed at all. Thus, the fancy new RAID drivers had proven to be somewhat useless, and entirely not fancy. More surfing the net, but on a computer that was unbelievably unstable thanks to a very confused SATA bus, more downloading of RAID drivers from other places, all to no avail. At the end of the day, I was forced to use the version of the drivers directly off the motherboard DVD, but I had to install them through Windows and find them on the disc manually instead of using the supplied driver install tools.

After a few more random reboots, a bit more instability, and some formatting of a drive that looked to be 1.5TB I decided to run a quick hard drive benchmark to see how I did. Thankfully, for comparison purposes, the hard drives I had in the computer before this experiment were almost identical to the ones I had just added so I had a solid basis for comparison. At the end of the day, the RAID array was almost exactly twice as fast as the drives were when not RAIDed together. I would call this a victory, even if a stressful and drawn out one.

Dumpster Fitness

In the on-going efforts of preparing my house to sell it, I’ve recently procured a fairly massive dumpster. I discovered that Home Depot offers dumpsters one day while wandering around at the Home Depot where I’ve spent thousands of dollars during this project. I ordered one while walking around in their parking lot from my cell phone and a couple of days later it arrived in my driveway. While placing the order I had a small flier with pictures of dumpsters in it and information about how big they are, but nothing more than that. Almost at random I chose the middle of the 5 sizes, a 15yd dumpster. It was $535.00 for 1 week, and the option to extend it for a second week at no extra charge if needed.

When it arrived I immediately began to think I had managed to get a dumpster that was way bigger than I could ever possibly fill. It sat in my driveway collecting bits of springtime tree pollen and other random dust on the wind for almost a whole week. By the time I was feeling dejected about having wasted $535.00 and decided to call for the extension by a week, I had only managed to place about 3 things in the dumpster. I was using about 1/50th of a cubic yard.

Over the course of the next week, I moved a bunch of other things into it which seemed to fill it very quickly due to poor arrangement. I was beginning to realize I would need help and tried to figure out what best to put into the dumpster in the time I had left. I called on my fiance, and the work began with me climbing into the dumpster to shuffle everything around. What was a nearly full dumpster once again become a dumpster with almost nothing in it. Then the fit hit the shan.

What followed was a bit of a blur honestly. It was an entire weekend of working on the house, cleaning out storage bins and trunks, throwing away everything that wasn’t important, chopping up furniture, tearing up carpet and padding, and carefully arranging new additions to the dumpster to optimize space usage. When it was over the dumpster was packed full, my fiance and I were exhausted, and my house was way emptier. This effort left both of us sore, tired, and frankly, feeling like we’d gotten a heck of a work out.  Imagine pushing a solid wood coffee table up over the edge of a dumpster that is as tall as you are if you can’t figure out why. It’s a work out I would recommend to anyone with a house to clean, but only if you own a Sawzall.

Development Environments

Imagine with me for a moment the simple pleasures of a kid learning to program his computer.  Using whatever language his brain can get around and only the least complicated parts of that language that are needed to “make the computer do his bidding” he sits around for hours programming silly little programs that output noise that imitates songs or draws pretty shapes on the screen.  There are no concerns for code maintainability, there is no need to worry about his brother coding something that breaks his code, there is no concept of his programs running on any computer besides the one he’s sitting in front of.  Even such basic programming concepts as looping and conditionals are foreign.  It’s a care-free world of exploration, playing around, and experimentation.

Literally decades later, that same programming kid is still programming.  Instead of writing programs that live in a single file, and would eventually grow up to include multiple subroutines instead of line numbers, he spends his days and nights crafting massive projects that involve dozens, hundreds, or even thousands of files.  His tinkering has become his career and code that was once just his is now created by teams of people.  The ideas for projects are seldom his own and are often supplied by people that appear to have no idea how to even use a computer.  What was once a passion has become a job.  What once held the amazing mark of “I can’t believe someone is paying me to do what I enjoy doing” has become “They don’t pay me enough.”

With the passage of time the glorified dreams of programming games for a living has gone by the wayside and have been replaced with the life of a web developer.  Code has become a chore for a paycheck, and the motivation to work on side projects is low due to the old stand-by excuse of “I just spent all day in front of a computer, why would I want to continue that now that I’m at home.”  Well, the simple reason is to try to keep some form of the passion for development alive and kicking in the rough world of a paycheck earning geek.  To that end I’ve managed to eek out a couple of partially completed pet projects that almost no one has ever even heard of, and even fewer care about.

To all my programming fellows out there, keep plugging along, keep earning that paycheck, and the the love of all that’s holy…  Don’t stop your pet projects.  Leave them unfinished if you must, but don’t let the spacing between them get too great or you may just find that you have lost the passion.  Without that passion these funny little boxes full of ones and zeros would stop being interesting, and that I fear, would suck indeed.

1 14 15 16 17 18 20