Planned outage for BOS and ESEA
19 Jan 2007 15:40:44 UTC
Topic 192335
(moderation:
For those who haven't read the BOS RSS feed, the BOS message boards or the ESEA message boards, here some info:
The hard drive containing the databases has been giving trouble these last few days. It is close to give up. I have two hard drives which was planned to be used as a replacement for the boot/system drive, but this is more important right now. So this weekend I will spend some time replacing the database drive. I will try to build a RAID with these two new hard drives, but this may take some time, as it is the first RAID I've ever made. Keeping all data/programs completely intact during the process is an extra task, and may make it take a bit longer, as I don't have a third clean hard drive to save things on. But I'll do my best to do this as fast as possible. If all things go wrong I have back-ups.
So, just so you know, the BOS site and services and the ESEA site will be down for a while this weekend.
Planned outage for BOS and ESEA
)
I've spent the last few days checking everything was working correctly, and it seems so. This is what happened Sunday:
Around 10 am local time, the database drive stalled once again, and I shut down the system, knowing I was going to correct things later.
Around 3 pm local time, I had moved everything to my work area, and wanted to start up to test everything would work fine when attempting to do the drive switch. But now the database drive box didn't start at all - no fan, no light, nothing. The other one seemed to start as usual. I thought it might be the power supply, so I switch to the other power supply - this time the box started, but I really didn't like the sound, so I turned it off quickly. The other box didn't like the power supply from the database drive box.
So, now I had two drives that I didn't know if I could even get working. Anyway, with two drives to switch and only two drives to replace them, I could wave goodbye to my RAID plans. The only hope I had was that it was the external boxes that were failing, not the hard drives themselves. And it turned out to be just that. So after I had copied the database drive successfully, I made the sites available again while copying the other drives - before moving things back where they belong.