Well, after playing around with the RAID array throughout the wee hours of the morning, it’s pretty apparent that something went seriously wrong.  A massive power flux?  A dicey hard drive?  I really don’t know at this point.  S.M.A.R.T. status on all the drives shows that they’re running just fine.  So far 2 ideas are floating around in my head:

1. The system suffered a massive power fluctuation that totally ticked off the Mac, or the RAID unit, or both.
2. There is a major compatibility problem with the RAID unit and the HighPoint Technology card that I had to use in place of the bundled controller card.  The only thing I can think of is that there might be 2 different chipsets between the RAID unit and the controller that don’t like each other at all.

Either way, I’m glad this problem decided to rear its head NOW instead of later, when we’ve got the drive populated with irreplaceable data.

Speaking of which, it just so happens that most of the files that were on that RAID5 array are still sitting in other areas!  THAT is letting me breathe so much easier right now.  However, there were quite a few Final Cut project files that were only on that array, which is still a bummer.  I’m in the process of looking through data recovery software to see if there’s anything decent that I can try.

In the meantime, I’ve got a UPS set hook into that system immediately.  Plus, if I can’t make the array work after another rebuild, I’m doing to set a separate PC up there and connect it to the MacPro.  Since the PC has a PCI slot on it, I can use the Norco’s bundled controller card.  I’m not exactly thrilled about putting a PC up there JUST to act as a bridge between the editing system and the RAID, but I may find that I have no choice.

More updates as the plot unfolds.

This morning started with a phone call from Jeff in the editing room.  He was having trouble getting Final Cut to recognize our Sony MiniDV deck over FireWire.

I head upstairs and we begin tinkering around with it.  After a few unsuccessful attempts, we decide to reboot the machine and start from scratch.  No big deal, right?

Well, after rebooting, I get an error on the desktop saying that a disk is unreadable by OS X.  I’m used to seeing these when I insert DVDs, but the only thing in the DVD drive was an audio disc.  Then I noticed that the RAID5 array that we just put into production at the end of last week is missing from the desktop.  Oh no…this is not good.  This drive was working just fine with no signs of errors.  Now I can see it, but I can’t mount it.  Even a look at the RAID controller shows that there are no errors on the array.

As soon as I attempt to run a verify operation though, the event log shows that there are inconsistencies on the array, and the controller starts a rebuild.  For the moment, I was slightly relieved.  The array will rebuild and I’ll be able to remount the drive with no problems, right?

—

Well, here I am 12 hours later (rebuilding a 6.75TB array takes a LONG time!).  I’ve been at home monitoring the rebuild, and it finished just a few minutes ago.  After holding my breath and attempting to remount the array in OS X, I was a little surprised (and very disappointed) to get nothing but errors after attempting a verify and then a repair.

So now I begin the task of looking for a disk repair utility for the Mac.  I’m not sure if it will do any good, but I’m rapidly running out of ideas.

It’s going to be a long night.

>> I took some time earlier this week and upgraded my Wordpress installation to version 2.2.  I was expecting a possibly a small face lift and some more features, but there really isn’t much to note aside from my theme getting whacked and RSS icons getting plastered all over the top of the header.  I upgraded to the latest version of the theme and that seems to have fixed it, and all my plugins seem to be working as well.  Just for good measure, I added Digg icons at the bottom of the posts.

>> Has anyone else ever dealt with credit card readers on their network?  We’ve got one set up in our cafe area at the moment, and we are getting quite a few read errors during transactions.  It’s a pain because any read error totally voids the transaction and it has to be restarted.  We’ve tested this reader on various locations in our network with the same results (which actually makes me breathe easier).  The only thing I haven’t tried at this point is putting the reader on a separate VLAN, but I haven’t had time to get that far yet.  If anyone has any experience with credit card readers, I’d love to hear any advice you have.

>>  This Thursday the Video Department received some much-needed help!  Mr. Jeff Conn has come aboard for a summer internship and will be working mainly in video post-production.  Jeff has already lent quite a bit to the video team with his editing skills.  It’s going to be a tremendous blessing to have him around!

>>  On Friday I entered into some new territory (for me, anyway):  SSL certificates.  Though it’s a little embarrassing to admit, SSL implementation has been on my to-do list for some time now but had never made it to the front burner.  Between Friday and Saturday, I managed (with some how-to advice from John Dolan) to get a CA set up and get a certificate set up on our Exchange server for OWA and OMA.  OMA wasn’t a huge deal, because we only have 2 Windows Mobile devices checking mail on our server, but it’s still nice to know that it works.  Thanks for your help, John!

Next week my primary goal will be getting SSL-Explorer up and running for our non-notebook-toting staff.  I’ve been having some issues with the community edition, such as the WebDAV URLs not opening correcting on the client end.  Hopefully by the end of the week things can get smoothed out.