none
File Corruption on Shared Folder RRS feed

  • Question

  • Hi all,

    I just added another drive and now I am getting file conflicts.  The files are MP3 music files.  When I go to the directory/files in question and try to play them I can not.  I cannot delete the files.  When I try to delete the files I get the following message "Cannot delete <filename>: The name of the file cannot be resolved by the system".

    Any idea's why this has happened?  How can I resolve this issue? 

    Friday, January 30, 2009 6:44 PM

Answers

  • Okay. Could you please submit a bug report on Connect? Include logs collected from your server and uploadedvia the WHS toolkit.

    I'm not on the WHS team, I just post a lot. :)
    Saturday, January 31, 2009 5:12 PM
    Moderator

All replies

  • Hi,

    I think Lara recently posted a very good FAQ about how to resolve file conflicts - it might contain all the information you need.

    Best greetings from Germany
    Olaf

    Friday, January 30, 2009 6:52 PM
    Moderator
  • Thanks for the pointer Olaf.

    I tried a couple of the suggestions but still can't delete the files.  It's strange it happened after the new drive install and only a few files are affected.

    Friday, January 30, 2009 8:53 PM
  • SBMoore said:

    Thanks for the pointer Olaf.

    I tried a couple of the suggestions but still can't delete the files.  It's strange it happened after the new drive install and only a few files are affected.



    What error message did you receive when you attempted to delete the files from a cmd prompt?

    Thanks


    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Friday, January 30, 2009 9:28 PM
    Moderator
  • Actual message is "Cannot delete <filename>: The name of the file cannot be resolved by the system".

    What brought this to my attention is the "Network At Risk" icon on the top bar of the Windows Home Server Console.  When I click on this it tells me there are file conflicks.  When I click on the details it it shows "Accessed is denied" on three files and the files are in two different folders.  One in one folder and the other two in another folder.  When I go to either of the folders all files are inaccessible.  I can't play or delete on of the files.
    • Marked as answer by SBMoore Saturday, January 31, 2009 5:45 AM
    • Unmarked as answer by SBMoore Saturday, January 31, 2009 5:48 AM
    Saturday, January 31, 2009 5:43 AM
  • Sorry, from a cmd prompt I get the same errror message ... "The name of the file cannot be resolved by the system".  I get the same response for both the full filename and the 8.3 filename.
    Saturday, January 31, 2009 5:48 AM
  • There is a limit on the maximum length of the path (including file name) in all versions of Windows. The limit per NTFS varies from version to version, but (I think) is usually 32,767 bytes. However, many WIN32 API calls that deal with file and folder manipulation have a much smaller limit, usually MAX_PATH: 260 characters. The error that you're seeing is really a standard windows error, defined in Winerror.h: ERROR_CANT_RESOLVE_FILENAME, just filtered in various ways and usually related to path length. Media files are frequent offenders, because we all want to sort our music by artis, albom, genre, etc, and sometimes that can lead to a really long folder name or two. :)

    Windows Home Server used to have an issue with files that were stored in paths longer than 260 characters (i.e. it used to use some of those API calls for file manipulation), but I thought that had been corrected. Can you give us the version infromation from the Resources tab in the WHS console? And an example of a file that's failing, with complete path (in your shares)?

    I'm not on the WHS team, I just post a lot. :)
    Saturday, January 31, 2009 12:55 PM
    Moderator
  • I don't think this is the problem.  This issue just start when I installed and then added the new drive.  Everything was fine before I did this.  Also, I can see and access the files in the DE directory just fine.  I was able to copy the files to another system and play them.
    Saturday, January 31, 2009 4:12 PM
  • Okay. Could you please submit a bug report on Connect? Include logs collected from your server and uploadedvia the WHS toolkit.

    I'm not on the WHS team, I just post a lot. :)
    Saturday, January 31, 2009 5:12 PM
    Moderator
  • Did you ever solve this?  I am getting the exact same problem with a handfull of files on my Music share, but I've have not recently installed a new drive.
    Monday, July 6, 2009 12:44 AM
  • Did you ever solve this?  I am getting the exact same problem with a handfull of files on my Music share, but I've have not recently installed a new drive.


    Hi,

    Have you tried to run chkdsk on all the drives in the server?
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Monday, July 6, 2009 12:47 AM
    Moderator
  • Have you tried to run chkdsk on all the drives in the server?

    I originally ran chkdsk on c: and d: with no issue.  But then I ran the chkdsk in your link.  When this line executed:

    for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1

    4 seperate chkdsk windows opened, and all but one finished.  It simply hung with the following:

    The type of the file system is NTFS.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    37712 file records processed.
    File verification completed.
    1 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
    133787 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    37712 security descriptors processed.
    Security descriptor verification completed.
    1905 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    10 percent complete. (30000 of 37696 files processed)

    In addition to the system drive, I have 4 other drives installed in the server.  Does this infer that one of them is failing?  Is so, how can I identify which one, and possibly repair it?


    Tuesday, July 7, 2009 11:32 AM
  • Have you tried to run chkdsk on all the drives in the server?

    I originally ran chkdsk on c: and d: with no issue.  But then I ran the chkdsk in your link.  When this line executed:

    for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1

    4 seperate chkdsk windows opened, and all but one finished.  It simply hung with the following:

    The type of the file system is NTFS.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    37712 file records processed.
    File verification completed.
    1 large file records processed.
    0 bad file records processed.
    0 EA records processed.
    0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
    133787 index entries processed.
    Index verification completed.
    5 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    37712 security descriptors processed.
    Security descriptor verification completed.
    1905 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    10 percent complete. (30000 of 37696 files processed)

    In addition to the system drive, I have 4 other drives installed in the server.  Does this infer that one of them is failing?  Is so, how can I identify which one, and possibly repair it?


    This didn't have a drive letter like c:\fs\X where X is a distinct letter or number assigned by Windows Home Server? If not, check the system event log on the server for events pointing to drive errors like event ID 55s, event ID 7s or event ID 26s.

    Once you find one or several that point to a specific drive letter (i.e. c:\fs\X), use the steps that Theo posted here: http://social.microsoft.com/Forums/en-US/whssoftware/thread/0f3bafbf-b0e2-42b2-a824-7a0c21fc549e  to indentify a bad HDD.

    Pull that drive from the server. Use the console to remove it if possible.
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Tuesday, July 7, 2009 9:37 PM
    Moderator