Wednesday, March 5, 2008
Windows Home Server Data Corruption Bug
Posted by Jason Dunn in "Digital Home News" @ 04:30 PM
"Microsoft today updated KB 946676 which is the Knowledge Base article covering the Windows Home Server data corruption bug. This bug causes data to be corrupted when you try to edit or save certain files directly on the home server within certain applications. As well as fixing the original publication date of the article, worrying, Microsoft states that customers have reported data corruption occurring with a growing list of applications. I guess they have a responsibility to report the full list of issues reported - however, according to the article Microsoft has only reproduced the bug on certain applications within that list."
This post over at We Got Served is bit over a week old, but I thought it was worth sharing for any of you who are running Windows Home Server. In a nutshell, the core technology that makes Windows Home Server so cool (the automatic data mirroring) is also what makes it dangerous in this instance. I was a huge fan of WHS when I was beta-testing it, but after getting the final version and using it full-time for a few months, my enthusiasm for the product has greatly waned.
Why? Well, to start with the stability and robustness of the product is lacking. Twice now I've had corruption problems with my backups, forcing me to Remote Desktop into the WHS and hack around to get it fixed (which involves nuking all past backups). I see regular error messages about something going wrong with the server, and usually a simple reboot fixes the problem - just this week I wasn't able to log into the server with the WHS Connector clients. Whenever I tried, from any computer, I was told that the password I was using wasn't correct. Rebooting the WHS machine fixed this problem. Bizarre! I also no longer play music off the server because the audio stream would sputter and stutter every few minutes. The worst problem was my inability to get the Connector software installed on all my computers, which meant that several of them weren't being backed up. I found a solution just yesterday, which I'll be posting about separately (because it's just too important not to).
Here's hoping that the forthcoming Power Pack 1 will make some serious improvements to the product...
This post over at We Got Served is bit over a week old, but I thought it was worth sharing for any of you who are running Windows Home Server. In a nutshell, the core technology that makes Windows Home Server so cool (the automatic data mirroring) is also what makes it dangerous in this instance. I was a huge fan of WHS when I was beta-testing it, but after getting the final version and using it full-time for a few months, my enthusiasm for the product has greatly waned.
Why? Well, to start with the stability and robustness of the product is lacking. Twice now I've had corruption problems with my backups, forcing me to Remote Desktop into the WHS and hack around to get it fixed (which involves nuking all past backups). I see regular error messages about something going wrong with the server, and usually a simple reboot fixes the problem - just this week I wasn't able to log into the server with the WHS Connector clients. Whenever I tried, from any computer, I was told that the password I was using wasn't correct. Rebooting the WHS machine fixed this problem. Bizarre! I also no longer play music off the server because the audio stream would sputter and stutter every few minutes. The worst problem was my inability to get the Connector software installed on all my computers, which meant that several of them weren't being backed up. I found a solution just yesterday, which I'll be posting about separately (because it's just too important not to).
Here's hoping that the forthcoming Power Pack 1 will make some serious improvements to the product...
