Over the next few days (or maybe weeks, but I hope not), my server will be down from time to time. I am in the process of upgrading from 13+60 GB hard drives to a single 200GB HD. I’m also upgrading from Debian Woody (stable) to Debian Sarge (testing). I really didn’t realize how far behind Woody is until I loaded Sarge on a server for my dad. Sarge was so much better that I decided I had to upgrade.
I got the basic operating system loaded, as well as a few programs. I haven’t gotten much further yet. I need to copy over all of the files for my blog and get apache configured right. Until I get that going, I’ll have to take the site down, swap hard drives, work on the upgrade, and swap back so I can bring the blog back up while I’m away from the computer for work or sleep, etc.
You won’t see much, if any difference in the site from this upgrade, but it will be good on my end.
So if you get errors that you can’t connect, or a “site down” page, that is why. I am trying to divert traffic to another machine to at least give the “site down” message, but I’m never sure if it is working right.
Good luck — those sorts of things always take me 2-3 times longer than I plan for…
That’s pretty standard for me too. That’s why I’ve decided to just swap the drives, work on it for a while, and swap back when I’m done to get the blog back up while I’m away from it. I have no expectations for when I’ll be done.
Just getting the thing booted took several tries. It didn’t like a single, 200GB partition. It would install, but not boot. When I broke it into two partitions, it worked fine, but I had to try it about 5 times before I figured out how to make it work.