none
c:\fs\<drive>\DE is a file, not a folder - what can be wrong? RRS feed

  • Question

  • Hello,

     

    I'm having a strange problem which I think relates to the way WHS maps drives to c:\fs. My setup is a plain HP495 box with an old 500GB disk and a new 1TB disk. Some time ago the 500GB disk had problems, but now shows up as healthy. Both of these disks show up under c:\fs\. There is a directory in the new drive (c:\fs\1J0) called DE, and in this directory I can find my physical files. On the old disk however, (c:\fs\1TX), DE is s file of 0 kb.

    [IMG]http://i55.tinypic.com/mhg574.png[/IMG]

    I suppose this explains why many of the files in my shares are not accessible to the network, and  why the DEmigrator process is producing apx 500-1000mb of logfiles every day. Here is an example of the data from the log files:

     

    [10/9/2010 12:01:30 PM  e28] OpenedFile::Open: Error 31 opening {2620D31F-2896-449E-B175-78EE82D95A5A},\DE\shares\Temp\Software\Software\GPS
    
    [10/9/2010 12:01:30 PM 1efc] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 2620d31f-2896-449e-b175-78ee82d95a5a
    
    

    Disk manager and chkdisk seems to think that there are lot's of files on the drive though. Here is the latest log file from chkdisk (chkdsk_c__fs_1IX.log):

     

     

    23679 data files processed.                                    
    
    Windows has checked the file system and found no problems.
    
     488375968 KB total disk space.
     404608036 KB in 226929 files.
         97900 KB in 23681 indexes.
            16 KB in bad sectors.
        331728 KB in use by the system.
         65536 KB occupied by the log file.
      83338288 KB available on disk.
          4096 bytes in each allocation unit.
     122093992 total allocation units on disk.
      20834572 allocation units available on disk.
    
    

    I have also tried to remove the disk from Disk Manager, but I only get a warning saying that I don't have enough space. This can't be right since I have 1,2 TB free space on the other disks.

     

    Any ideas what could be wrong or what steps I could could try to fix it?


     

    Best regards,
    Magnus

     

    Saturday, October 9, 2010 12:57 PM

All replies

  • Hello,

    I'm having a strange problem which I think relates to the way WHS maps drives to c:\fs. My setup is a plain HP495 box with an old 500GB disk and a new 1TB disk. Some time ago the 500GB disk had problems, but now shows up as healthy. Both of these disks show up under c:\fs\. There is a directory in the new drive (c:\fs\1J0) called DE, and in this directory I can find my physical files. On the old disk however, (c:\fs\1TX), DE is s file of 0 kb.

    [IMG]http://i55.tinypic.com/mhg574.png[/IMG]

    I suppose this explains why many of the files in my shares are not accessible to the network, and  why the DEmigrator process is producing apx 500-1000mb of logfiles every day. Here is an example of the data from the log files:

    [10/9/2010 12:01:30 PM  e28] OpenedFile::Open: Error 31 opening {2620D31F-2896-449E-B175-78EE82D95A5A},\DE\shares\Temp\Software\Software\GPS

    [10/9/2010 12:01:30 PM 1efc] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 2620d31f-2896-449e-b175-78ee82d95a5a

    Disk manager and chkdisk seems to think that there are lot's of files on the drive though. Here is the latest log file from chkdisk (chkdsk_c__fs_1IX.log):

    23679 data files processed.
    Windows has checked the file system and found no problems.

    488375968 KB total disk space.
    404608036 KB in 226929 files.
    97900 KB in 23681 indexes.
    16 KB in bad sectors.
    331728 KB in use by the system.
    65536 KB occupied by the log file.
    83338288 KB available on disk.
    4096 bytes in each allocation unit.
    122093992 total allocation units on disk.
    20834572 allocation units available on disk.

    I have also tried to remove the disk from Disk Manager, but I only get a warning saying that I don't have enough space. This can't be right since I have 1,2 TB free space on the other disks.

    Any ideas what could be wrong or what steps I could could try to fix it?

    Best regards,
    Magnus
    You might have to treat it as a failed drive (meaning power down the server, disconnect the drive, power up the server, then remove the now-missing drive through the Console).  Just make sure you disconnect the correct drive.
    Saturday, October 9, 2010 10:38 PM
    Moderator
  • Thanks for your reply kariiya21. It looks like the Master File Table of the disk was corrupted somehow, and that this had nothing to do with WHS or the way the drive was mounted. 

    I managed to find and restore the files from the broken disk with an old copy of PowerDataRecovery. I restored these files to another disk, so the next steps now are to remove the broken disk, let WHS sort out the bad tombstones and then copy the restored files back to their original paths.



    Best regards,

    Magnus
    Monday, October 11, 2010 7:16 PM