So some of you (heh... like I actually have any readers) might've noticed that my blog has been down for the past couple of days. Well, I got it in my head to setup a RAID1 array on my server here at home over the weekend, and the fun seems to be just starting.
Setting up the array was exceedingly easy (too easy I think... an omen of what was to come). After configuring the drives and formatting, I promptly dumped about 200gb of data from my existing, non-mirrored, drives onto them. All was well until Tuesday when I noticed I couldn't connect to the server from work. Upon returning home I found that the RAID controller was having problems accessing one of the drives in the new mirrored array. I rebooted, re-seated cables, and tried to rebuild the disk... it failed at 76% (after about 3 hours of churning away). I have another RAID controller coming in the mail that should let me run more than 1 array (I'd like to mirror my existing 120GB drives as well), and am hoping this is a controller problem, not a disk one.
The latest development is that I was greeted with a "delayed write failure" error on one of the non-mirrored disks when I turned on the computer to check my e-mail before work today. As I didn't want to lose any data, I promptly shut it back down and left it off for the duration of the workday. I once again hope that all of this is controller-related (both drives that were having problems were on the same IDE channel), and that things will improve when I get my Adaptec stand-alone controller tomorrow or Friday. I have just booted (you're reading this, aren't you) the machine again, disabled write caching, and am waiting to see what happens.
There's a lot of other fun things I'd like to write about right now (like a rather irritating eBay experience I'm going through), but I'll save them for later, once I get my machine working more reliably (or maybe a real webhost).
-
-
Link
|
