locked
Unhealthy storage? RAID5 RRS feed

  • Question

  •  

    Yes I know that RAID is not supported by MS but it is the way that I would like to go, so any support will come here.

     

    I was able to install and use the RAID and from a BIOS and NVIDIA MediaShield standpoint it is a healthy set of drives. 

     

    The WHS Home Server Console Server Storage Tab

    Shows NVIDIA RAID5 Status Unhealthy, a right click gets to the Repair Hard Drive Wizard:

    The following tasks are recommended for this hard drive:

    Task Name: Task Details:

    Check Disk Scan Repairs files system errors

    Server Storage Rebuild Rebuilds the index of all Server Storage

     

    The Wizard runs for about 10 minutes and finishes without any indication of the results of the repair, but it is still shown as unhealthy.

    The motherboard is an ASUS M2NPV-VM.

     

    Two logs are below, thanks for any help and assistance:

    q_de.log

    MIGR:  01/06/2008 20:10:41:921: Beginning repair mode for all secondaries.

    MIGR:  01/06/2008 20:10:42:218: Beginning full migration pass. LazyPass is False.

    REBL:  01/06/2008 20:15:03:171: Handled exception in RebalanceSecondaries: \\.\Unmounted.

    System.IO.DirectoryNotFoundException

    Could not find a part of the path '\\.\Unmounted\DE'.

    mscorlib

       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

       at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)

       at System.IO.DirectoryInfo.GetFiles(String searchPattern, SearchOption searchOption)

       at System.IO.DirectoryInfo.GetFiles()

       at DriveExtender.Core.MigrationEngine.RebalanceDirectory(Volume volume, DirectoryInfo dir)

       at DriveExtender.Core.MigrationEngine.RebalanceSecondaries()

     

    HomeServerConsole.080106.2008369218.3880.log

    Created at 1/6/2008 8:08:36 PM

    ***** Started at 1/6/2008 8:08:36 PM ***

    ***** Started at 1/6/2008 8:08:36 PM ***

    [4]080106.200839.0156: Error: Cannot invoke RefreshData for HealthControl

    Music080106.200839.0156: Error: Backup percentage is -2147483648

    Music080106.200839.0156: Error: Cannot invoke RefreshData for HealthControl

    Music080106.200842.0156: Error: Backup percentage is -2147483648

    Music080106.200842.0156: Error: Cannot invoke RefreshData for HealthControl

    [1]080106.200843.3281: Error: Cannot invoke RefreshData for HealthControl

    [1]080106.200843.3593: Error: Error -2147023728 in SendMessage

    [13]080106.200850.0156: Error: Backup percentage is -2147483648

    [1]080106.200902.8593: Error: Error -2147023728 in SendMessage

    [11]080106.200910.5156: Error: Backup percentage is -2147483648

    [10]080106.201041.0156: Error: Backup percentage is -2147483648

    [10]080106.201120.7187: Error: Backup percentage is -2147483648

    [1]080106.201120.7343: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201120.7343: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [10]080106.201123.7343: Error: Backup percentage is -2147483648

    [1]080106.201123.7343: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201123.7343: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [12]080106.201131.0312: Error: Backup percentage is -2147483648

    [1]080106.201131.0312: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201131.0312: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [21]080106.201151.7343: Error: Backup percentage is -2147483648

    [1]080106.201151.7343: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201151.7343: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [22]080106.201322.0468: Error: Backup percentage is -2147483648

    [1]080106.201322.0468: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201322.0468: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [23]080106.201622.5468: Error: Backup percentage is -2147483648

    [23]080106.201750.0781: Error: Backup percentage is -2147483648

    [1]080106.201750.0781: Error: Client debb0cab-e96e-49ad-a3f5-dd896c9c3cf1 not found by BackupHelpers.FindClient

    [1]080106.201750.0781: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: debb0cab-e96e-49ad-a3f5-dd896c9c3cf1

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)

       at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient

    [23]080106.201753.0781: Error: Backup percentage is -2147483648

    [12]080106.201800.5000: Error: Backup percentage is -2147483648

    [24]080106.201821.0000: Error: Backup percentage is -2147483648

    [25]080106.201951.5312: Error: Backup percentage is -2147483648

    [26]080106.202252.0156: Error: Backup percentage is -2147483648

     

     

     

     

     

     

    Monday, January 7, 2008 4:38 PM

Answers

  • That the repair wizard finishes quickly but doesn't actually fix your problem suggests that either something went wrong during your installation of Windows Home Server, or that there is a conflict between Windows Home Server and your hardware/drivers. Unfortunately, as you have already said, RAID isn't supported, so I don't think you will be able to get much (any) help from Microsoft. The first thing I would try is always a reinstallation of the software, to see if perhaps that will fix the problem.

    For what it's worth, during the public beta I was able to install Windows Home Server on a RAID array; the controller in that case was a Promise PATA controller, not the motherboard RAID controller you're using. However, if I recall correctly I had to install three times before I got an installation that would actually work for any length of time. At that point, I gave up and installed a separate drive for the system and primary data partition, and used the RAID array as secondary storage. So in limited circumstances it is possible.
    Monday, January 7, 2008 7:06 PM
    Moderator
  • WHS. When you install WHS using your array as your system drive, you must supply your drivers twice, no questions asked. You supply them the first time at the beginning of setup, during the initial graphical portion. Then after the first reboot, at the beginning of text-mode setup, you will need to supply them again at the "Press F6" prompt. For the second driver installation, you will need a floppy; nothing else will do. I have good luck with hitting F6 at the right time; I don't miss more than one in three attempts. Smile

    To use your RAID array as a "drive" in your storage pool, install WHS without RAID drivers, then install the drivers after the server itself is up and running on a single disk. That's the best way I ever found. I will warn you that you will likely have problems if you ever have to reinstall, because you'll have to supply those drivers during setup in that case, and it sounds like you're already having trouble with that.
    Monday, January 7, 2008 11:05 PM
    Moderator

All replies

  • That the repair wizard finishes quickly but doesn't actually fix your problem suggests that either something went wrong during your installation of Windows Home Server, or that there is a conflict between Windows Home Server and your hardware/drivers. Unfortunately, as you have already said, RAID isn't supported, so I don't think you will be able to get much (any) help from Microsoft. The first thing I would try is always a reinstallation of the software, to see if perhaps that will fix the problem.

    For what it's worth, during the public beta I was able to install Windows Home Server on a RAID array; the controller in that case was a Promise PATA controller, not the motherboard RAID controller you're using. However, if I recall correctly I had to install three times before I got an installation that would actually work for any length of time. At that point, I gave up and installed a separate drive for the system and primary data partition, and used the RAID array as secondary storage. So in limited circumstances it is possible.
    Monday, January 7, 2008 7:06 PM
    Moderator
  • Thanks Ken,

    I should have mentioned that I use a separate drive for the system and primary data partition. The RAID is only for secondary storage. I went this route based on what few posts were here on this subject, actually bought that specific motherboard to get the RAID.

     

    When you say multiple installs are you referring to WHS or the disk drivers?

     

    Monday, January 7, 2008 9:34 PM
  • WHS. When you install WHS using your array as your system drive, you must supply your drivers twice, no questions asked. You supply them the first time at the beginning of setup, during the initial graphical portion. Then after the first reboot, at the beginning of text-mode setup, you will need to supply them again at the "Press F6" prompt. For the second driver installation, you will need a floppy; nothing else will do. I have good luck with hitting F6 at the right time; I don't miss more than one in three attempts. Smile

    To use your RAID array as a "drive" in your storage pool, install WHS without RAID drivers, then install the drivers after the server itself is up and running on a single disk. That's the best way I ever found. I will warn you that you will likely have problems if you ever have to reinstall, because you'll have to supply those drivers during setup in that case, and it sounds like you're already having trouble with that.
    Monday, January 7, 2008 11:05 PM
    Moderator