none
NTFS Disk Error 55 RRS feed

  • Question

  • I woke up this morning and had several email alerts from my WHS box.

    This started with only ONE instance of:

    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.

    Followed by a ton of these for several hours....then they eventually went away....

    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.

    I logged into the WHS console and under shares, and disk management all disk read as healthy and everything appears just fine.  Everything is green. 

    I saved the system event log, cleared it and then rebooted the box.     It came back up and everything is healthy\green in the WHS console and the system event log is free of errors.

    This WHS install is connected to a Smart UPS and has been rock solid for months with 0 issues.    These are the first real errors I have been notified of via alerts.

    I am thinking I should just leave things alone since everything appears ok?     Any suggestions would be appreciated.

    UPDATE:   The errors have come back since the reboot.   This is the entire snippet and then it goes away:

    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.

    I am kinda freaking out now.    HELP!!!!



    Flad




    Sunday, March 22, 2009 1:53 PM

Answers

  • fladtheimpaler said:

    The chkdsk finished with the following.   

    I would appreciate it if somebody could give me some thoughts on where I stand with this.   My biggest concern is that I have orhpaned files or that the C: drive is messed up.  

    Your primary drive is fine.  C:\fs\17 is one of your secondary drives (which is obviously showing early warning signs of failure).

    fladtheimpaler said:

    Am I ok to leave this alone (Provided the errors do not come back) or am I better off deleting the partitions of C: and doing a server reinstallation?

    If it was me, I would start by figuring out which drive that is and start shopping for a new hard drive to replace the failing one ASAP.

    fladtheimpaler said:

    Additionally if i browse to C:\fs\17\DE\shares\MEDIA I do not see all the folders files in the MEDIA Share.   If I go to the MEDIA share normally all the files are there and I can access files which I do not see under C:\fs\17\DE\shares\MEDIA.

    That's normal.  You only need to worry when you try to open a file through the share and you get an error message.

    fladtheimpaler said:

    C:\>chkdsk /r C:\fs\17
    The type of the file system is NTFS.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    5872 file records processed.
    File verification completed.
    0 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)...
    Correcting error in index $I30 for file 378.
    Correcting error in index $I30 for file 378.
    Sorting index $I30 in file 378.
    23284 index entries processed.
    Index verification completed.
    CHKDSK is recovering lost files.
    10 percent complete. (1 of 12 unindexed files processed)
    Recovering orphaned file 1-01SU~1.M4A (379) into directory file 378.
    Recovering orphaned file 1-01 Superman.m4a (379) into directory file 378.
    Recovering orphaned file 1-02DO~1.M4A (380) into directory file 378.
    Recovering orphaned file 1-02 Doorman.m4a (380) into directory file 378.
    Recovering orphaned file 1-03AT~1.M4A (381) into directory file 378.
    Recovering orphaned file 1-03 A Thousand Trees.m4a (381) into directory file 378
    .
    Recovering orphaned file 1-04DE~1.M4A (382) into directory file 378.
    Recovering orphaned file 1-04 Devil.m4a (382) into directory file 378.
    Recovering orphaned file 1-05MR~1.M4A (383) into directory file 378.
    Recovering orphaned file 1-05 Mr. Writer.m4a (383) into directory file 378.
    Recovering orphaned file 1-06PE~1.M4A (384) into directory file 378.
    Recovering orphaned file 1-06 Pedalpusher.m4a (384) into directory file 378.
    Recovering orphaned file 1-07DE~1.M4A (385) into directory file 378.
    Recovering orphaned file 1-07 Deadhead.m4a (385) into directory file 378.
    Recovering orphaned file 1-08MA~1.M4A (386) into directory file 378.
    Recovering orphaned file 1-08 Maybe Tomorrow.m4a (386) into directory file 378.
    13 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    5872 security descriptors processed.
    Security descriptor verification completed.
    1329 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    5856 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    204096943 free clusters processed.
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

     976751968 KB total disk space.
     160260604 KB in 4470 files.
          1948 KB in 1331 indexes.
             4 KB in bad sectors.
        101644 KB in use by the system.
         65536 KB occupied by the log file.
     816387768 KB available on disk.

          4096 bytes in each allocation unit.
     244187992 total allocation units on disk.
     204096942 allocation units available on disk.



    Monday, March 23, 2009 12:23 AM
    Moderator

All replies

  • fladtheimpaler said:

    I woke up this morning and had several email alerts from my WHS box.

    This started with only ONE instance of:

    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.

    Followed by a ton of these for several hours....then they eventually went away....

    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    1:45:35 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.

    I logged into the WHS console and under shares, and disk management all disk read as healthy and everything appears just fine.  Everything is green. 

    I saved the system event log, cleared it and then rebooted the box.     It came back up and everything is healthy\green in the WHS console and the system event log is free of errors.

    This WHS install is connected to a Smart UPS and has been rock solid for months with 0 issues.    These are the first real errors I have been notified of via alerts.

    I am thinking I should just leave things alone since everything appears ok?     Any suggestions would be appreciated.

    UPDATE:   The errors have come back since the reboot.   This is the entire snippet and then it goes away:

    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:44:06 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\17.
    3/22/2009    10:42:49 AM    Ntfs    Error    Disk     55    N/A    WHS    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.

    I am kinda freaking out now.    HELP!!!!



    Flad






    Currently Network Health does not flag a drive when these errors first show up in the event log. We've changed how this works in a later version of the product. The original thinking was that minor errors could cause Network Health to incorrectly flag a drive as unhealthy.

    To resolve the EVENT ID 55s, please run chkdsk /r on C:\fs\17

    You will need to do this from a cmd prompt on the administrator's desktop on the server i.e. RDP/TS into the server. While this is running, the system will indicate file conflicts until you reboot. This is normal.

    I would keep an eye on this drive. If this continues to happen, you may need to consider replacing the drive.

    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
    Sunday, March 22, 2009 5:28 PM
    Moderator
  • Lara,

    Thanks for the response!    I will run this chkdsk now and report back how it goes.

    FLAD

    Sunday, March 22, 2009 5:32 PM
  • The chkdsk finished with the following.   

    I would appreciate it if somebody could give me some thoughts on where I stand with this.   My biggest concern is that I have orhpaned files or that the C: drive is messed up.  

    Am I ok to leave this alone (Provided the errors do not come back) or am I better off deleting the partitions of C: and doing a server reinstallation?

    Additionally if i browse to C:\fs\17\DE\shares\MEDIA I do not see all the folders files in the MEDIA Share.   If I go to the MEDIA share normally all the files are there and I can access files which I do not see under C:\fs\17\DE\shares\MEDIA.

    C:\>chkdsk /r C:\fs\17
    The type of the file system is NTFS.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    5872 file records processed.
    File verification completed.
    0 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)...
    Correcting error in index $I30 for file 378.
    Correcting error in index $I30 for file 378.
    Sorting index $I30 in file 378.
    23284 index entries processed.
    Index verification completed.
    CHKDSK is recovering lost files.
    10 percent complete. (1 of 12 unindexed files processed)
    Recovering orphaned file 1-01SU~1.M4A (379) into directory file 378.
    Recovering orphaned file 1-01 Superman.m4a (379) into directory file 378.
    Recovering orphaned file 1-02DO~1.M4A (380) into directory file 378.
    Recovering orphaned file 1-02 Doorman.m4a (380) into directory file 378.
    Recovering orphaned file 1-03AT~1.M4A (381) into directory file 378.
    Recovering orphaned file 1-03 A Thousand Trees.m4a (381) into directory file 378
    .
    Recovering orphaned file 1-04DE~1.M4A (382) into directory file 378.
    Recovering orphaned file 1-04 Devil.m4a (382) into directory file 378.
    Recovering orphaned file 1-05MR~1.M4A (383) into directory file 378.
    Recovering orphaned file 1-05 Mr. Writer.m4a (383) into directory file 378.
    Recovering orphaned file 1-06PE~1.M4A (384) into directory file 378.
    Recovering orphaned file 1-06 Pedalpusher.m4a (384) into directory file 378.
    Recovering orphaned file 1-07DE~1.M4A (385) into directory file 378.
    Recovering orphaned file 1-07 Deadhead.m4a (385) into directory file 378.
    Recovering orphaned file 1-08MA~1.M4A (386) into directory file 378.
    Recovering orphaned file 1-08 Maybe Tomorrow.m4a (386) into directory file 378.
    13 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    5872 security descriptors processed.
    Security descriptor verification completed.
    1329 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    5856 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    204096943 free clusters processed.
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

     976751968 KB total disk space.
     160260604 KB in 4470 files.
          1948 KB in 1331 indexes.
             4 KB in bad sectors.
        101644 KB in use by the system.
         65536 KB occupied by the log file.
     816387768 KB available on disk.

          4096 bytes in each allocation unit.
     244187992 total allocation units on disk.
     204096942 allocation units available on disk.
    Monday, March 23, 2009 12:08 AM
  • fladtheimpaler said:

    The chkdsk finished with the following.   

    I would appreciate it if somebody could give me some thoughts on where I stand with this.   My biggest concern is that I have orhpaned files or that the C: drive is messed up.  

    Your primary drive is fine.  C:\fs\17 is one of your secondary drives (which is obviously showing early warning signs of failure).

    fladtheimpaler said:

    Am I ok to leave this alone (Provided the errors do not come back) or am I better off deleting the partitions of C: and doing a server reinstallation?

    If it was me, I would start by figuring out which drive that is and start shopping for a new hard drive to replace the failing one ASAP.

    fladtheimpaler said:

    Additionally if i browse to C:\fs\17\DE\shares\MEDIA I do not see all the folders files in the MEDIA Share.   If I go to the MEDIA share normally all the files are there and I can access files which I do not see under C:\fs\17\DE\shares\MEDIA.

    That's normal.  You only need to worry when you try to open a file through the share and you get an error message.

    fladtheimpaler said:

    C:\>chkdsk /r C:\fs\17
    The type of the file system is NTFS.
    Volume label is DATA.

    CHKDSK is verifying files (stage 1 of 5)...
    5872 file records processed.
    File verification completed.
    0 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)...
    Correcting error in index $I30 for file 378.
    Correcting error in index $I30 for file 378.
    Sorting index $I30 in file 378.
    23284 index entries processed.
    Index verification completed.
    CHKDSK is recovering lost files.
    10 percent complete. (1 of 12 unindexed files processed)
    Recovering orphaned file 1-01SU~1.M4A (379) into directory file 378.
    Recovering orphaned file 1-01 Superman.m4a (379) into directory file 378.
    Recovering orphaned file 1-02DO~1.M4A (380) into directory file 378.
    Recovering orphaned file 1-02 Doorman.m4a (380) into directory file 378.
    Recovering orphaned file 1-03AT~1.M4A (381) into directory file 378.
    Recovering orphaned file 1-03 A Thousand Trees.m4a (381) into directory file 378
    .
    Recovering orphaned file 1-04DE~1.M4A (382) into directory file 378.
    Recovering orphaned file 1-04 Devil.m4a (382) into directory file 378.
    Recovering orphaned file 1-05MR~1.M4A (383) into directory file 378.
    Recovering orphaned file 1-05 Mr. Writer.m4a (383) into directory file 378.
    Recovering orphaned file 1-06PE~1.M4A (384) into directory file 378.
    Recovering orphaned file 1-06 Pedalpusher.m4a (384) into directory file 378.
    Recovering orphaned file 1-07DE~1.M4A (385) into directory file 378.
    Recovering orphaned file 1-07 Deadhead.m4a (385) into directory file 378.
    Recovering orphaned file 1-08MA~1.M4A (386) into directory file 378.
    Recovering orphaned file 1-08 Maybe Tomorrow.m4a (386) into directory file 378.
    13 unindexed files processed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    5872 security descriptors processed.
    Security descriptor verification completed.
    1329 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
    5856 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    204096943 free clusters processed.
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

     976751968 KB total disk space.
     160260604 KB in 4470 files.
          1948 KB in 1331 indexes.
             4 KB in bad sectors.
        101644 KB in use by the system.
         65536 KB occupied by the log file.
     816387768 KB available on disk.

          4096 bytes in each allocation unit.
     244187992 total allocation units on disk.
     204096942 allocation units available on disk.



    Monday, March 23, 2009 12:23 AM
    Moderator
  • Kariya, thanks for the reply...     

    When I go to the C:\fs folder 17 is the only item that shows up as a folder.  

    Everything else shows up as a drive letter (19,D,I,M,O,Q,S,U).

    I have duplication enabled for all my shares so I guess I am relatively covered.

    How do I figure out which drive is the problem drive??
    Monday, March 23, 2009 12:33 AM
  • fladtheimpaler said:

    Kariya, thanks for the reply...     

    When I go to the C:\fs folder 17 is the only item that shows up as a folder.  

    Have you physically removed the drive from the server yet?  Have you rebooted the server after running chkdsk?  It should have a pic of a hard drive, not a folder.

    fladtheimpaler said:

    Everything else shows up as a drive letter (19,D,I,M,O,Q,S,U).

    I have duplication enabled for all my shares so I guess I am relatively covered.

    Yep. :)

    fladtheimpaler said:

    How do I figure out which drive is the problem drive??



    Have you ever mapped your drives (using either pen and paper or the Disk Management add-in)?  If not, that could be a problem. First thing to do is get that to show up again as a hard drive, not a folder. Once you do that, you can see the size of that hard drive by right clicking on it and selecting Properties, then clicking the Properties button. If that is the only drive of that size, then it's easy to determine. If it's not, you will probably have to start guessing by shutting down the server, disconnecting one drive of the same size, then boot it back up and see which one shows as a folder in C:\fs. (And frankly, I would strongly recommend mapping all of your drives now while you're at it so you won't have this problem again in the future.)
    Monday, March 23, 2009 1:10 AM
    Moderator
  • I havent touched anything in the system.   I didn't remove any drives.   I did reboot after chkdsk completed.

    When I go to C:\fs folder and do a properties in 17 (folder) or any of the Drives that have drive icons they all say the same thing:

    Type: Mounted Volume
    Location: C:\fs
    Target: DATA

    None of them mention a size and the Size column is empty for all drives.

    I do have disk management add-in installed and all disks show up fine in there and all read as Healthy.


    Monday, March 23, 2009 1:17 AM
  • fladtheimpaler said:

    I havent touched anything in the system.   I didn't remove any drives.   I did reboot after chkdsk completed.

    Then there is definitely something wrong if 17 still looks like a folder.

    fladtheimpaler said:

    When I go to C:\fs folder and do a properties in 17 (folder) or any of the Drives that have drive icons they all say the same thing:

    Type: Mounted Volume
    Location: C:\fs
    Target: DATA

    None of them mention a size and the Size column is empty for all drives.

    I think you missed the step where I said you need to click the Properties button afterward. ;)

    fladtheimpaler said:

    I do have disk management add-in installed and all disks show up fine in there and all read as Healthy.

    Did you ever use it to physically map your drives?  IMO, that's by far the best feature of that add-in (drive temp being second).
    Monday, March 23, 2009 2:15 AM
    Moderator
  • Haha!   How did i miss the giant properties button?    

    Ok Well it still shows up like a folder, but when i do t properties I can tell it is one of my 1TB WD Drives.  Problem is there are 4 of them in the box.   At least it narrows things down some.   

    Now that I see that the C:\FS folder is a mapping to my secondary drives I am not all that cocerned since duplication is enabled.

    The System event log is clean since i ran the chkdsk and rebooted so I will keep my eye on it for errors.

    I will have to look at that option within disk management.   It shows me the drive numbers as mapped in the OS disk management but not mapped to the Drive Letters within C:\FS I will have to look into that!

    Thanks for all the help Kariya I appreciate it!!!!




    Monday, March 23, 2009 2:35 AM
  • fladtheimpaler said:

    Haha!   How did i miss the giant properties button?    

    Ok Well it still shows up like a folder, but when i do t properties I can tell it is one of my 1TB WD Drives.  Problem is there are 4 of them in the box.   At least it narrows things down some.   

    Now that I see that the C:\FS folder is a mapping to my secondary drives I am not all that cocerned since duplication is enabled.

    The System event log is clean since i ran the chkdsk and rebooted so I will keep my eye on it for errors.

    I will have to look at that option within disk management.   It shows me the drive numbers as mapped in the OS disk management but not mapped to the Drive Letters within C:\FS I will have to look into that!

    Yeah, you have to create your own wireframe of your server, create the location of the drives, then point each drive to the correct location in the pic.  It's a little bit of work, but once it's done, you'll be happy you have it in situations like this. :)

    fladtheimpaler said:

    Thanks for all the help Kariya I appreciate it!!!!




    Monday, March 23, 2009 4:34 AM
    Moderator
  • OK well all the Chkdsks completed last night without error and the event logs are clean so I think I may be ok for now.

    Is there any way to figure out what physical drives map to what drive letters within C:\fs?  

    I would think this info need to be in the registry somewhere.

    Also any reason why 2 drives have numbers (17,19) and the rest have Letters?
    Monday, March 23, 2009 2:08 PM
  • fladtheimpaler said:

    Is there any way to figure out what physical drives map to what drive letters within C:\fs?  

    Not in the general case, I'm afraid. Usually some digging through the Disk Management MMC snap-in along with registry research will let you figure it out, for internal drives. Identifying external drives is even harder.

    If you have an OEM Windows Home Server device, it will have drive lights that will help you identify the internal drives when you work with them. If you have a home-built server, the best advice I can give you is to label the drives as you install them. I would probably just stick some tape on the side of the drive that's visible when you have the case open and identify it there. 


    I'm not on the WHS team, I just post a lot. :)
    Monday, March 23, 2009 3:37 PM
    Moderator
  • fladtheimpaler said:

    OK well all the Chkdsks completed last night without error and the event logs are clean so I think I may be ok for now.

    Is there any way to figure out what physical drives map to what drive letters within C:\fs?   

    As Ken said, keeping track of them as you go along is the best method (although I still prefer the add-in myself).  In your case (drives already installed), the only way to know is to shut down your server, disconnect one drive, power it back up and find out which drive is missing in the Console.  Then power down your server again, reconnect that drive, and repeat the process.  (If you decide to do this, make sure you only have one drive disconnected at any one time and also make sure your server is 100% up-to-date before you start.)

    fladtheimpaler said:

    I would think this info need to be in the registry somewhere.

    Also any reason why 2 drives have numbers (17,19) and the rest have Letters?

    Luck of the draw. :)
    Tuesday, March 24, 2009 3:02 AM
    Moderator
  • Yo Kariya.   I rebooted again and now "17" is showing up like a drive again and not as a folder.   
    Tuesday, March 24, 2009 10:06 PM
  • Hey I was able to figure out my Drive Mappings.

    I went into the C:\FS folder and did a properties on the DE folder within each drive.    

    I was then able to match up the size of that folder to the disk ammount used for a given disk.   

    I then updated the drive label for each drive within Disk Management Add In to reflect the Drive letter it correlates to within C:\FS.


    Tuesday, March 24, 2009 10:27 PM
  • fladtheimpaler said:

    Hey I was able to figure out my Drive Mappings.

    I went into the C:\FS folder and did a properties on the DE folder within each drive.    

    I was then able to match up the size of that folder to the disk ammount used for a given disk.   

    Pretty sneaky.  I never thought of comparing used space. :)

    fladtheimpaler said:

    I then updated the drive label for each drive within Disk Management Add In to reflect the Drive letter it correlates to within C:\FS.



    Tuesday, March 24, 2009 11:59 PM
    Moderator
  • A trick that worked for me:

    Start Disk Management, select drive, properties and check the "Shadow Copies" tab:
    It will highlight the associated volume ....

    Theo


    No home server like Home Server
    Friday, March 27, 2009 10:33 PM
    Moderator