For the time being there are only 5 drives installed, two fewer than my old file server. I’ve deliberately left plenty of room for expansion though. One PCI slot has been used (for the video card), leaving two PCI-e 16x slots, two PCI-e 1x slots and two PCI slots empty. There’s plenty of free drive bays, and I’m trying to source another 6×3.5″ drive cage which will fit into the space above the PSU.

With the extra cage, there should be enough room to fit up to fifteen hard drives fairly comfortably, although I doubt I’ll ever use that many at once. Ten is more realistic. I’ll be installing two more 1TB drives in a few weeks, and from there I’ll just add more drives when I need more space/redundancy.

From the (albeit limited) testing I’ve done so far, performance seems to be a bit better than the old server, so I’m fairly happy with the result.

Memtest86+ showed no errors, so I threw in my Spinrite disk in hope it may save me from having to do a repair install of Windows. It found a bunch of bad blocks which it had to remap, and going by the SMART data, the drive looked to be on it’s last legs, but it managed to correct the problems, or at least enough to get it bootable again. At this point I decided to make an image of the drive before it completely failed, which I then copied up to my home file server.

While it was copying, I noticed a few of the drives on the server were getting a bit low on space. Not quite at critical levels, but low enough that I’d need to do something about it fairly soon. Normally I’d just use that as a reason to go buy another couple of drives to throw in it, but it’s at the stage where adding new, larger drives will require the removal of a couple of the older drives first. I’m actually currently in the process of piecing together and testing the hardware that will make up my new file server, which will address that problem (for the foreseeable future anyway), but that’s a few weeks away, so I thought I’d see if I could find a way to free up some space.

As you’d expect for most home servers, the majority of the total storage is taken up by media files, none of which I really want to get rid of, but I found I had a bunch of recorded HDTV programs that I’d just dumped in there in .ts format, which could be transcoded to h.264 or divx without significant quality loss.

Also taking up a fairly sizable chunk is my ’system build’ directory, which contains all the drivers, installers, patches and hotfixes I’ve downloaded over time. As I’d normally do a software rebuild on a system at least once a week, it’s a huge time saver having a local repository of that sort of stuff, especially given that I have limited bandwidth to the net.

The directory itself is fairly well organised, for example, if I need a driver for a nVidia video card, I know they’re stored in \drivers\nvidia\video\ or if I needed a patch for Quake 4 it’s in \games\quake4\patches\. Any time I download a new driver, installer or a new patch it gets added in with the rest, which is why it’s grown over time. I’m one of those people who find it hard to delete anything, but what I did start to wonder, is if it’s really necessary to have a triple redundant local backup of a dozen versions of the nVidia detonator drivers that were released back when I was running Windows 98SE, or all those patches for Windows XP that were later integrated into Service pack 1, 2 or 3.

That’s why I’m going to do a clean-up of that directory during the spare time I get over the next few days and move anything that seems unnecessary onto a spare external hard drive (just in case I do need it one day). I’ll probably only reclaim 20, maybe 25GB at most, but given that it’s on a RAID1 array which is also backed up externally it quickly adds up. It should also cut down the time needed for AV scanning, which will save wear and tear on the drives plus a bit of power.