As is the case with my problems with the Xbox 360's Fall 2007 Dashboard Update, where I am having many issues that no one else seems to be having, I'm sort of hoping that what I'm seeing on Windows Home Server (WHS) lately is just me. But I'm concerned enough about these issues to at least just throw them out there and see what happens. Here's what's up. First, I've literally just completed my switch-over to WHS and have taken down my previous Windows Server 2003-based server. I'm using HP's Media Smart Server and have added two 512 GB drives for a total of 2 TB of storage. I really only need 1 TB but I do use WHS's data duplication functionality extensively, so what the heck. Plus it's backing up several PCs regularly. The point of all this is that I'm really using this thing. It's not a best test or an experiment. My data is all on this server.
The HP has had a troubling number of hard drive corruption issues. These issues seem to be occurring mostly on a single disk, but that's not necessarily true, so I will keep watching this. Occasionally, I will logon to Vista in the morning, see a red WHS icon and click it to discover that something's wrong with a hard disk. WHS lets you repair these problems, and it takes a long time but always seems to work. I don't have any offsite backup so this is troubling. I am experimenting with backing up to my old Firewire 800-based BiggerDisks over the network, but it's slow, and if the WHS-based data is corrupted, I'm screwed anyway. I'm not sure if it's my router or my home server, but three times now I've gotten an alert that the remote access feature had stopped working. Just navigating to the Remote Access tab of the Settings dialog triggers a re-configuration, and that does work each time. But what if I'm away when this stops working and thus can't access my files remotely? It sort of renders the feature moot, doesn't it?
View: Full Story @ Paul's SuperSite blog