locked
File Corruption on Static Data RRS feed

  • Question

  • Over the few months that I have had WHS there has been a slow trickle of files getting corrupted. These files are on a duplicated share.

     

    These files are files that I have dumped on the server. They are not being actively accessed by any application on any of the client PCs. The only process that should be accessing them should be the WHS balancing and the Avast Anti-virus.

     

    The problem is first reported as a 'Network at Risk', with the storage status as 'Duplication is failing for shared folder: Tim. There are file sysem problems.' The details then states 'Server Storage Failure Details' and goes on to the list the files with the pre-fix FAILURE.

     

    That's it. No further information!

     

    Anyway, opening the file share reveals that most of the files can still be accessed, so presumably it is only the duplication that has failed.

     

    Occasionally, however, the files can not be opened, reporting an Invalid File Handle. The only way to then delete it is to create a file of the same name and copy it over.

     

    Some observations:

    • I am aware that there are other posts regarding this, and I have checked the length of the path and this seems OK (211 characters - I believe the limit is 260).
    • These files have been sitting happily on the share for some weeks.
    • When I rectify the situation the problem goes away for a bit then re-occurs, generally in a similar area.
    • I have run the Toolkit Sever-Storage Diagnostics but the logs show no problems (just an empty dialogue, which itself is not very useful. Why doesn't it report 'all clear' or list the tests it has performed?).

    My questions:

    • Why does WHS allow me to put these files onto a share if it is unable to duplicate them?
    • Why can the files sit there happily for weeks (presumably duplicated) and then start getting corrupted?
    • Are there any tools that give a better level of feedback when things go wrong?
      • This seems to be a major failing of WHS. It is very poor at giving accurate and useful information when things go wrong.
    • Is this issue distinct form the know corruptions that arise when accessing particular file types using applications on a client PC?
    • Why are Network at Risk failures not shown in the WHS event logs (I view these using the Event Viewer Add-In)?

    I have a number of Add-Ins installed, including Duplication Information.

     

    Appreciate any feedback.

     

    Tim

    Friday, January 25, 2008 9:23 AM

Answers

  • Froglet, you're taking my statements out of context, thanks to CPTBeaker who did likewise. I don't personally think that Avast is causing any problems, as it shouldn't be attempting to rewrite any files in your shares. (I use Avast on my server, for example, and have never seen any of the errors he reports.) I told him that if he thinks Avast is causing a problem (which he implied), he should check with the publisher. Which is common sense; maybe they know something about his specific situation, or maybe they want to investigate to see if it's their software.

    How do you get Microsoft interested in solving these problems? The Windows Home Server team's only priority is solving this problem. They're already as "interested" as they can be. If you believe you are having file corruption issues, and think that they may be a result of the bug first mentioned in KB946676, you can send email to whsforum at microsoft dot com and let them know your situation. Various Microsoft representatives have requested (repeatedly) that people do this, so that they can get a better picture of the scope of the problem, and so that they can gain a level of comfort that the eventual patch will really be a global fix. So please avail yourself of the opportunity; I'm assured that your email will not simply vanish into the bit bucket.

    Until the patch is available, Microsoft has already given you the best advice available: Don't edit files on your server, if you have more than a single disk. Edit in this case include opening a file with software that immediately writes to the file, which is what I think the software that I was talking about in that quote that CPTbeaker posted above is doing.

    As for when the patch will be available, I'm sorry, but Microsoft has not provided me with a time line that I can share with you. They know that everyone wants to know when this bug will be fixed, but for now, the only answer is "When it's ready for release".


    Thursday, February 7, 2008 5:08 PM
    Moderator
  • Matt

     

    The Windows Home Server toolkit includes the error reporting tool to create diagnostic data for submission to Microsoft. The tool provides a CAB number that can be included in your e-mails.

     

    The toolkit can be found here:

     

    http://go.microsoft.com/fwlink/?LinkId=98601

     

    The manual for the toolkit can be found here:

     

    http://www.microsoft.com/downloads/details.aspx?FamilyID=d6b60e67-4cc8-49f0-beff-a2556881e4bf&DisplayLang=en

     

    Tim

    Friday, February 22, 2008 8:22 AM
  • Mike, the problem is serious. Microsoft realizes that. And they realize that WHS users are committing their families' digital lives to this software. That's why the original KB article was published back in December, before they even had a real handle on the cause of the issue. They continue to update the KB article in the face of continuing bad press for the same reason: concern for customers' data.

    I can't give you any details on the cause of the bug, I'm afraid. Microsoft says that simply copying a file to your server won't cause file corruption, but that editing a file may. Editing includes many file operations that people don't normally think of, though; some programs rewrite parts of a file just by opening them, and that would probably be enough to trigger the issue.

    So the best advice available right now is what Microsoft has been saying right along: maintain copies of your essential data elsewhere, and don't edit files while they'r stored on the server.

    All of this has been said before. (Repeatedly, by me Smile ) Microsoft knows that WHS purchasers are very anxious to get a patch for this issue, but they are determined to deliver one that doesn't cause more problems than it solves, so it's taking a long time. And if Microsoft were to announce tomorrow that they have found the cause and have a patch in testing, it would still be no sooner than a couple of months from now (at best) before that patch would be released.

    Saturday, February 23, 2008 1:14 AM
    Moderator

All replies

  • Tim

     

    Have you checked that you have no problems with the drives?

     

    Also, what version of Avast are you running? I know that during the beta of Avast there were occasionally problems.

     

    How are you copying the files to the server? Are you using the \\servername\sharename method or are you doing something else?

     

    Why does WHS allow me to put these files onto a share if it is unable to duplicate them? - because you put the files in the share then WHS starts the duplication process. It cannot predict as your are putting them there that there might be a problem duplicating them and tell you so.

     

    Why can the files sit there happily for weeks (presumably duplicated) and then start getting corrupted? - they shouldnt. If they were fine, and you are not using them or accessing them, then they shouldnt suddenly corrupt on their own. Thats why I asked about the version of Avast you are using. Also, what other add-ins are you running?

     

    Are there any tools that give a better level of feedback when things go wrong? - at the moment what is there is what you get unfortunately.

     

    Is this issue distinct form the know corruptions that arise when accessing particular file types using applications on a client PC? - I would say yes, because the known issue is about accessing and editig files on your WHS, not files that have been sitting there for weeks doing nothing and then suddenly become corrupt for no reason.

     

    Andrew

    Friday, January 25, 2008 9:58 AM
    Moderator
  •  Andrew Edney wrote:

    Tim

     

    Have you checked that you have no problems with the drives?

     

    Yes, all the drives are OK

     

    Also, what version of Avast are you running? I know that during the beta of Avast there were occasionally problems.

     

    Version 4.7 WHS - Build Dec2007 (4.7.59)

    This is the current downloadable version

     

    How are you copying the files to the server? Are you using the \\servername\sharename method or are you doing something else?

     

    I am using the share as \\servername\sharename

     

    Why does WHS allow me to put these files onto a share if it is unable to duplicate them? - because you put the files in the share then WHS starts the duplication process. It cannot predict as your are putting them there that there might be a problem duplicating them and tell you so.

     

    OK, but it should not then attempt to duplicate them if it knows it will be unable to do so. It certainly should not corrupt the original in trying to do so.

     

    Why can the files sit there happily for weeks (presumably duplicated) and then start getting corrupted? - they shouldnt. If they were fine, and you are not using them or accessing them, then they shouldnt suddenly corrupt on their own. Thats why I asked about the version of Avast you are using. Also, what other add-ins are you running?

     

    The Add-Ins I am running are:

    Avast Anti-virus V4.7.52

    Duplication Info V1.1.0.0 (although problem initially seen before this was installed)

    Event Viewer V1.0.0.0 (although problem initially seen before this was installed)

    WHS Event Monitor  V1.1.1.0 (although problem initially seen before this was installed)

    WHS Customizer V1.0.0

    WHS Toolkit V6.0.1639.0

     

    Are there any tools that give a better level of feedback when things go wrong? - at the moment what is there is what you get unfortunately.

     

    Is this issue distinct form the know corruptions that arise when accessing particular file types using applications on a client PC? - I would say yes, because the known issue is about accessing and editig files on your WHS, not files that have been sitting there for weeks doing nothing and then suddenly become corrupt for no reason.

     

    Andrew

    Sunday, January 27, 2008 10:33 AM
  • As a follow up to my problem I have the following extra detail:

     

    Running the Toolkit Server-Storage Diagnostics from the console always results in an empty window at the end. I have been assuming that this means the test passes but I would have expected a positive outcome note in the log.

     

    Running a Chkntfs /C: to set the dirty bit does not seem to force a CHKDSK at the next re-boot. Is it OK to run CHKDSK directly against the mount points and so force an unmount or should services such as the duplication be stopped first?

     

    Tim

    Tuesday, February 5, 2008 4:57 PM
  • I don't have time to follow every thread, so why is accessing the folders thusly "the way" to do it?

     

    \\servername\sharename

     

    Does this mean that you're not supposed to Map drives?  I try not to, but some programs don't allow it.

     

    Tuesday, February 5, 2008 5:15 PM
  • Drive mapping should be fine.

     

    I believe what you should not do is access the mount points directly (i.e. C:\fs\<mountpoint>)

    Tuesday, February 5, 2008 5:20 PM
  • I tried to access my turbotax save file from last year that I put on my server and the new turbotax said invalid or currupt file. now Im not sure if this is a turbotax bug or a data corruption issue but this same process worked fine last year with my w2k server without data duplication. I had some .wma corruptions but solved it and turned of duplication of media files for now. This file had been unchanged for a year but has become a dead file. this year  made a cd to file away. 

     

    Tuesday, February 5, 2008 5:55 PM
  • I too have begun to experience corruption on static data.  I have a share under my 'User' folder where I have begun to assemble applications I want to restore on clean OS installs.  I have multiple sub folders for each application.

     

    During December and thru mid Jan, I've been running Avast WHS v.4.7.52 and v.4.7.59 (the Jan 7, 08 update) in trial mode - and purchased a 2 year package in mid Jan.

     

    A couple of weeks ago I noticed the Avast Icon for my WHS machine in the Avast tab(in the connector) turned red - indicating some problems.  I started reading through the Avast logs and began to see entries stating that files were corrupted.  I've kept an eye on this for around two weeks and the list of files has slowly grown.

     

    These files were not accessed since I put them on my WHS machine (and no other users on my home network have either).  My entire user folder (and the sub folders where these reported corrupted files reside) is duplicated.

     

    I'm not seeing anything in the other logs on WHS indicating any hardware problems.  These same files/folders resided happily on the same hardware while running XP Pro as my server OS.

     

    I shut my WHS machine down last night because of some serious storms coming through the area and did not want to risk a power related shutdown while I was sleeping (I do have battery backup UPSs but there only good for 30-40min), since this causes problems with WHS also (my registry was trashed from a forced power cycle a while back). 

     

    Turned off is the way my WHS machine is going to stay until the 'Magic Fix' comes out.

     

    I can't risk letting my WHS machine sit idol while it's grinding up my files.

     

    Good Luck.

     

     

     

    Wednesday, February 6, 2008 2:41 PM
  • - duplicate post - (deleted)

    Wednesday, February 6, 2008 3:37 PM
  • CPTBeaker, if you suspect that Avast! for WHS is causing file corruption, you should check with the publisher to see if there's a known issue, and to make them aware of the issue for troubleshooting and correction.
    Wednesday, February 6, 2008 7:01 PM
    Moderator
  •  Ken Warren wrote:
    CPTBeaker, if you suspect that Avast! for WHS is causing file corruption, you should check with the publisher to see if there's a known issue, and to make them aware of the issue for troubleshooting and correction.

     

    I'll follow up with Avast for sure.  I may be incorrectly assuming that the problem is with WHS, but the frequent reports of corruption (with different software, outside the scope of the software listed in the KB article), have to make me wonder.

     

    Since Avast has to open the file to scan it, I guess the files are indeed being accessed daily for scanning, so I guess the data isn't really static.  Ken, in thread: http://forums.microsoft.com/WindowsHomeServer/AddPost.aspx?PostID=2795868&SiteID=50&Quote=True you said:

     

     Ken Warren wrote:
    No need to apologize, Chuck. I don't actually think the files are corrupted just by copying them to the WHS PC. I think it's the act of opening them that's causing the problem. Not that that will help you, as that question is academic; the best advice available right now is to not edit (which probably means don't open) the files while they're stored in the WHS shares. So you could either leave them on the Terastation for a while, or you could store them on a PC which is backed up to WHS regularly.

     

     

     

     

    Wednesday, February 6, 2008 7:07 PM
  • Ken,

     

    The assumption that avast is the culprit is a little rich. Given there are know problems with WHS and file corruption I know where my money is. In particular if avast has detected the files as corrupted this suggests it has attempted to access the file and found it to be already corrupted.

     

    So, taking your advice, how exactly do we get Microsoft interested in resolving these file corruption issues?

     

    I have been talking to Microsoft support now for over three weeks regarding my connector problem and have not got much further (although my support technician is now in touch with a 'connector specialist'). In that time the laptop in question has had no firewall/antivirus as the first thing they had me do was to uninstall it.

     

    My corruption problems seem to have got worse. Maybe I am being paranoid but I now suspect WHS for everything. This morning one of the 500GB disks in my WHS reported chkdsk errors. Running chkdsk from the GUI to force a reboot seemed to resolve the problem, but being able to do that is not something the end users WHS is targeted at are likely to be familiar with, especially as it has to be run against the mount point. Also my path environment variable on one of the laptops WHS backs-up has got wiped. I know this is unlikely to be WHS but suddenly I seem to be getting a lot of problems with machines that were previously very reliable.

     

    Seems like a little more testing would have gone a long way.

     

    Tim

    Thursday, February 7, 2008 2:03 PM
  •  Froglet. wrote:
    I have been talking to Microsoft support now for over three weeks regarding my connector problem and have not got much further (although my support technician is now in touch with a 'connector specialist'). In that time the laptop in question has had no firewall/antivirus as the first thing they had me do was to uninstall it.
    IMHO Uninstalling firewall/antivirus  should only be done for diagnostic purposes and NEVER with an active internet connection. If the support person advises anything else on this subject you know you're not talking to the right person. I hope this is free support, if not get back your money!
    Thursday, February 7, 2008 3:34 PM
    Moderator
  • Froglet, you're taking my statements out of context, thanks to CPTBeaker who did likewise. I don't personally think that Avast is causing any problems, as it shouldn't be attempting to rewrite any files in your shares. (I use Avast on my server, for example, and have never seen any of the errors he reports.) I told him that if he thinks Avast is causing a problem (which he implied), he should check with the publisher. Which is common sense; maybe they know something about his specific situation, or maybe they want to investigate to see if it's their software.

    How do you get Microsoft interested in solving these problems? The Windows Home Server team's only priority is solving this problem. They're already as "interested" as they can be. If you believe you are having file corruption issues, and think that they may be a result of the bug first mentioned in KB946676, you can send email to whsforum at microsoft dot com and let them know your situation. Various Microsoft representatives have requested (repeatedly) that people do this, so that they can get a better picture of the scope of the problem, and so that they can gain a level of comfort that the eventual patch will really be a global fix. So please avail yourself of the opportunity; I'm assured that your email will not simply vanish into the bit bucket.

    Until the patch is available, Microsoft has already given you the best advice available: Don't edit files on your server, if you have more than a single disk. Edit in this case include opening a file with software that immediately writes to the file, which is what I think the software that I was talking about in that quote that CPTbeaker posted above is doing.

    As for when the patch will be available, I'm sorry, but Microsoft has not provided me with a time line that I can share with you. They know that everyone wants to know when this bug will be fixed, but for now, the only answer is "When it's ready for release".


    Thursday, February 7, 2008 5:08 PM
    Moderator
  • Ken

     

    Thanks for your feedback.

     

    Firstly, this is the first time I have heard that we can send an e-mail to whsforum at microsoft dot com. Is this in the faq, and why is it different to posting in this forum?

     

    Secondly, this thread refers specifically to a form of data corruption that is distinctly different to that in KB946676, in that the data is only being stored on WHS, not directly accessed by applications.

     

    Tim

    Friday, February 8, 2008 8:29 AM
  • No this is a paid for support call to Microsoft.

     

    So far I have been through three support technicians and crossed the globe.

     

    Most of the things suggested to date are things that I told then I had already tried.

     

    Tim

    Friday, February 8, 2008 8:33 AM
  •  brubber wrote:
     Froglet. wrote:
    I have been talking to Microsoft support now for over three weeks regarding my connector problem and have not got much further (although my support technician is now in touch with a 'connector specialist'). In that time the laptop in question has had no firewall/antivirus as the first thing they had me do was to uninstall it.

    IMHO Uninstalling firewall/antivirus  should only be done for diagnostic purposes and NEVER with an active internet connection. If the support person advises anything else on this subject you know you're not talking to the right person. I hope this is free support, if not get back your money!

     

    No this is a paid for support call to Microsoft.

     

    So far I have been through three support technicians and crossed the globe.

     

    Most of the things suggested to date are things that I told then I had already tried.

     

    Tim

    Friday, February 8, 2008 8:36 AM
  •  Froglet. wrote:

    Ken

     

    Thanks for your feedback.

     

    Firstly, this is the first time I have heard that we can send an e-mail to whsforum at microsoft dot com. Is this in the faq, and why is it different to posting in this forum?

     

    Secondly, this thread refers specifically to a form of data corruption that is distinctly different to that in KB946676, in that the data is only being stored on WHS, not directly accessed by applications.

     

    Tim

     

    Sending an email to whsforum is not the same as posting in this forum. This forum is a "public" forum, where as the whsforum email is to be used for providing MS with specific information about corruption YOU might be having, and not to be used to just send support queries to. The more information MS has about the corruption bug (ie, what exactly is your set up and how it happens to you) then the more they can troubleshoot and eventually resolve it. Its very difficult for MS to do this when people just post on the forum "Im have the bug, etc, etc" so this way they can get specifics from you. They will contact you back and work with you to get this information. If you are experiecing the bug you should contact that address with as much information as possible.

     

    Andrew

    Friday, February 8, 2008 8:43 AM
    Moderator
  • Ok, thanks Andrew.

     

    Is this in the faq?

     

    Tim

    Friday, February 8, 2008 4:14 PM
  • Hi Tim

     

    No, this is something new, specifically for the data corruption bug.

     

    There will be an updated sticky post shortly.

     

    Andrew

     

    Friday, February 8, 2008 4:17 PM
    Moderator
  • I got a storage status error,
    =======
    "Duplication is failing for shared folder: <folder name deleted due to privacy> .  There are file system problems."
    FAILURE: D:\shares\Users\<folder>\My Documents\My Music\iTunes\iTunes Music Library.xml
    =======

    I just got done reading this entire thread and I would like to send an email to whsforum@microsoft.com but the only information I have is the error above.  Can anyone suggest where I could look on the whs server for any additional information/logs that whs team would find more helpful for troubleshooting?

    First thing I did after I powered my HP MediaSmart Server 475 (with 2 additional 500g Seagate drives, 4 total), after adding accounts, was download every addin I could find.  I decided to reboot later on that night and the server continually rebooted itself.  One restore later... The only addin I installed was Amazon Jungle disk.  I decided I'll test before I install any other WHS addons and my data backed up to AWS.

    Thanks,
    Matt



    Saturday, February 16, 2008 12:03 AM
  • Has anyone tried disabling duplication for a folder they are having duplication issues with?  I just tried it and after storage was balanced, I enabled duplication.  I'll provide updates and I've also emailed whsforum@microsoft.com.  We'll see what comes out of the enable/disable and the email.
    Saturday, February 16, 2008 4:58 PM
  • I am working on a second round of file corruption issues that I'm not sure is the original KB issue.
    In my System (Event Viewer) log I have hundreds of entries like this:

    "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA."

    and several entries that say:

    Application popup: Windows - Corrupt File : The file or directory D:\DE\shares\Music\filename.wma is corrupt and unreadable. Please run the Chkdsk utility.    (filename replaced)

    The Music share is not duplicated but I have duplication on.  The first time around the corruption did happen in duplicated folders and upon running chkdisk with repair the corrupted files were gone.  It did leave behind several corrupted files that are not deleteable.  I had to create a txt file with the same name, rename it with the files extension and copy over the corrupted file in order to get rid of it.

    What I'm currently doing.
    All my drives state they are healthy. 
    I've turned off duplication.
    I'm removing the extra drives I have in my WHS and will only run the single OS/Data drive for a while.  Maybe slowly add back the drives.

    This is a homemade server, not off the shelf.  I am considering an HP WHS but I wanted to use these drives as externals!
    I love the WHS but it seems I can only use it as a backup server as I'm scared to access any file directly from it on a share.

    3dog

    Monday, February 18, 2008 3:28 AM
  • Follow up on last post.

    Turned off duplication - Check
    Removing extra drives - Error.  The remove drive wizard stated I had enough room to procede and it chugged away for a few hours just to say that it did not complete.  The drive still lists as healthy.
    I rebooted and ran chkdsk.
    I am now deleting all my files off of WHS and finding many corrupt files that cannot be deleted.   I would like to keep it around for a little while because the backup service actually works.

    I know this is a MS forum but I see WHS in posts, magazines, newspaper articles, yet this phantom problem lingers while product goes out the door.  Tsk tsk.
    Tuesday, February 19, 2008 2:38 AM
  • Matt

     

    The Windows Home Server toolkit includes the error reporting tool to create diagnostic data for submission to Microsoft. The tool provides a CAB number that can be included in your e-mails.

     

    The toolkit can be found here:

     

    http://go.microsoft.com/fwlink/?LinkId=98601

     

    The manual for the toolkit can be found here:

     

    http://www.microsoft.com/downloads/details.aspx?FamilyID=d6b60e67-4cc8-49f0-beff-a2556881e4bf&DisplayLang=en

     

    Tim

    Friday, February 22, 2008 8:22 AM
  • 3dog

     

    Some of the corruption issues you describe sound similar to mine.

     

    Do you see any specific errors in the q_de.log?

     

    (C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs)

     

    I believe this is the DriveExtenderMigrator service.

     

    Tim

    Friday, February 22, 2008 8:30 AM
  • Ken: 

     

    This begins to sound a bit more serious than I'd thought.  I bought WHS months ago, and have been rearranging the hardware in my house for some time to set it up the "right way," following some good help from you and from other folks here about RAID etc. 

     

    I just learned about the data bug as I was about to finally set up my server, got worried, went looking for answers, and saw that -- if I'm understanding correctly -- we likely have some sort of DE-related issue that suggests that one should not open and work on files directly off of server drives from another PC until we have a fix.  Working files from the PC and storing them on WHS appears to be OK. 

     

    Further, the latest post a few days back suggests that MS can now duplicate the problem as is therefore on the way to a fix.  Fair enough -- and, notwithstanding the understandable (and inevitable) uproar, not really that big a problem in my case. 

     

    But this thread could suggest something more serious.  If any application (anti-virus, diskeeper's defrag?, etc.) opening (or moving?) files on the server from anywhere (including files opened by maintenance applications on the server itself) have the potential to cause data corruption, the problem is much more difficult to work around in the short term. 

     

    If we're sure that is NOT the case, I'll proceed with the build, and just watch my behavior until the fix is in, so to speak.  But if there's any real possibility of what this thread names "static data corruption," I think I'd be inclined to wait. 

     

    I try to keep my relationship with MS friendly, but objective.  I really like a good bit of what they've done (particularly WHS), and while I've been known to take the company to task on occasions, I'm inclined to cut'em a break this time.  This is new functionality in an OS that I find genuinely interesting, and Redmond had the good sense and generosity to build the product on a known code base with a good track record.  Although I'd rather the problem have been sorted out before the release, I'm sure they'll fix it.  And I'm certainly sure they're trying. 

     

    But if the problem is, or even may be, of the more serious variety that this thread suggests, a chagrined word of warning now may save a whole lot of heartache later. 

     

    If I've not read enough and am asking a silly question, apologies.  I surely don't want to mislead anyone into thinking the problem is more serious that is really is.  Thanks in advance for setting me straight. 

     

    Mike

     

     

    Friday, February 22, 2008 3:47 PM
  • Mike, the problem is serious. Microsoft realizes that. And they realize that WHS users are committing their families' digital lives to this software. That's why the original KB article was published back in December, before they even had a real handle on the cause of the issue. They continue to update the KB article in the face of continuing bad press for the same reason: concern for customers' data.

    I can't give you any details on the cause of the bug, I'm afraid. Microsoft says that simply copying a file to your server won't cause file corruption, but that editing a file may. Editing includes many file operations that people don't normally think of, though; some programs rewrite parts of a file just by opening them, and that would probably be enough to trigger the issue.

    So the best advice available right now is what Microsoft has been saying right along: maintain copies of your essential data elsewhere, and don't edit files while they'r stored on the server.

    All of this has been said before. (Repeatedly, by me Smile ) Microsoft knows that WHS purchasers are very anxious to get a patch for this issue, but they are determined to deliver one that doesn't cause more problems than it solves, so it's taking a long time. And if Microsoft were to announce tomorrow that they have found the cause and have a patch in testing, it would still be no sooner than a couple of months from now (at best) before that patch would be released.

    Saturday, February 23, 2008 1:14 AM
    Moderator
  • Thanks Ken: 

    Well, having waited this long, I think I'll just hang out a bit.  The fact that MS can duplicate the problem in the lab is encouraging, and I'm sure we'll have a fix soon. 

    Looking forward to it.  It's been a long road getting everything set up (not too much time lately), so it'll be fun to see the thing work once everything is ready.  But I'm sure glad this cropped up before data started going south. 

    Thanks for the reply.  I'll just watch and see what happens. 

    Regards,
    Mike
    Sunday, February 24, 2008 2:33 AM
  • I have about 150GB of recorded tv on my Home Server, all of which became corrupted about a week ago.  I was using the server to host a shard Excel spreadsheet to track some business activity for myself and my roomates (editable by multiple users simultaneously).  All 150GB of recordings are now corrupt and cannot be deleted, taking up a significant portion of the storage space on my computer.  I tried creating text files as mentioned earlier in this thread and copying over of them, but to no avail.  Is there any way I can reclaim that file space without reformatting (this is the same drive I have the operating system installed on)?
    Sunday, February 24, 2008 3:52 AM
  •  

    I don't know of any way that you can do that. The text file approach has always worked for me when it has been an invalid handle.

     

    I think it is a bit of a weak point in WHS that the data partition on the WHS install disk is the one that files are first landed to before being moved for either balancing or duplication. This means the data partition on the disk containing WHS is going to get the most hammer.

     

    Tim

    Monday, February 25, 2008 8:58 PM
  • I found out the cause of my file duplication error, my daughter's hard drive was full.  It would consistantly get the same error on the same file (itunes xml library file).  After cleared up space, its no longer occured.

    Thanks Frog for the toolkit links!
    Monday, February 25, 2008 10:44 PM