locked
Data Drive Missing RRS feed

  • Question

  • This is an old problem which I'm finally getting around to trying to fix.  Any thoughts would be appreciated.

    I've been using WHS since January 2008.  Sometime around April, I had approximately 8 hard drives in my system.  I needed one of the hard drives in another computer, so after using the "remove hard drive" tool, I pulled it out of the system.  Let's call that "Drive 1"  Later, I added it back, using the appropriate procedure.   No problem.  Then about a month later, I added another hard drive (let's call that one Drive 0) back into the pool (one that had also been in previously, but which I had removed using the proper procedures).  At this point, Drive 1 started showing up in the console as not part of my storage pool, even though the total amount of storage clearly reflected that it was included.  At some point, even though it didn't seem to be causing any problems, I got annoyed with it showing up as not part of the pool, so used the "add drive" commands to add it back.  This appears to have been a mistake.  Immediately, the Drive 0 flipped into "missing" status and I started getting a bunch of file conflict errors.  Of course, Drive 0 isn't really missing.  When I remote into the WHS, disk manager shows it as healthy.  It has been this way since maybe July.  I upgraded to PP1, thiking that might fix the problem, but no luck.

    Before posting this question, I spent some time browsing this forum and I think my problem is similar to one reported in this thread: http://social.microsoft.com/forums/en-US/whssoftware/thread/d322ea2a-e056-45c6-ac20-e4d170ceadb8/

    But I think my problem is different enough that I'm not sure how to fix it without breaking something else.  I'm pretty sure it has something to do with the entries under c:/fs/, but I'm a bit lost with what do now.  I've tried moving the "missing" hard drive to a different controller, but to no avail.  I've also tried disconnecting the "missing" drive, running the server for a while, and then later re-connecting it.

    Here is my current config:
    AthlonXP 3000+
    1 GB RAM
    EPoX 8RDA6+ Pro motherboard (nForce2 Ultra 400 chipset) w/ onboard SI 3114 SATA controller
    Silicone Image 3114-based PCI SATA controller card
    Drives (listed/numberd as they are in diskmgmt.msc):
    #       model          size   type       /fs/?        notes
    Disk 0  ST3500630A     500    DATA       1C       <-- this is the one that was previously out of the pool
    Disk 1  ST3320620AS    320    DATA       1A       <-- this is the one currently showing "missing"
    Disk 2  WD7500AACS     750    DATA       14
    Disk 3  WD2500JB       250    SYS/DATA            <-- 20gb SYS partion, the rest is DATA
    Disk 4  WD1600JD       160    DATA       R
    Disk 5  ST3320620AS    320    DATA       E
    Disk 6  ST3320620AS    320    DATA       L
    Disk 7  ST3320620AS    320    DATA       G
    Disk 8  ST3200822AS    200    DATA       X


    In the list above, I've also indicated the c:/fs/ path as best as I can determine by looking at the "shadow copies" information tab under the volume properties.  In addition to the paths listed above, there is another entry under c:/fs/ that shows with a folder icon rather than a drive icon, and when I click on it I get an error message.  That one is c:/fs/11.

    Based on that earlier thread, I'm thinking this whole problem is coming from some bad entries in the registry, but I'm not sure how to fix them.  Any thoughts anyone has would be appreciated.  THANKS!!!

    I'm attaching the Registry Storage Manager disks and volumes sections (seems to be quite a few extra entries???):

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\00000001-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk "
    "SystemName"="5b577a6a-0000-0000-0000-000000000000"
    "Size"="320071851520"
    "ObjectID"=dword:0000002d

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\00000001-0000-0000-0000-000000000000\Attributes]
    "DevicePath"="\\\\?\\PhysicalDrive4"
    "BusType"="SCSI"
    "ManufactureName"="ST332062 0AS SCSI Disk Device"
    "External"=dword:00000000
    "QRole"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\16381637-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk WDC WD16 00JD-00FYB0 SCSI Disk Device"
    "SystemName"="30bba0a2-0000-0000-0000-000000000000"
    "Size"="160041885696"
    "ObjectID"=dword:0000001a

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\16381637-0000-0000-0000-000000000000\Attributes]
    "DevicePath"="\\\\?\\PhysicalDrive3"
    "BusType"="SCSI"
    "ManufactureName"="WDC WD16 00JD-00FYB0 SCSI Disk Device"
    "External"=dword:00000000
    "QRole"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\30bba0a7-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk ST320082 2AS SCSI Disk Device"
    "SystemName"="410d3bf2-0000-0000-0000-000000000000"
    "Size"="200049647616"
    "ObjectID"=dword:00000020

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\30bba0a7-0000-0000-0000-000000000000\Attributes]
    "QRole"=dword:00000002
    "External"=dword:00000000
    "ManufactureName"="ST320082 2AS SCSI Disk Device"
    "BusType"="SCSI"
    "DevicePath"="\\\\?\\PhysicalDrive8"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\4c1ec00b-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk "
    "SystemName"="cf36a1e1-0000-0000-0000-000000000000"
    "Size"="320072933376"
    "ObjectID"=dword:00000014

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\4c1ec00b-0000-0000-0000-000000000000\Attributes]
    "QRole"=dword:00000002
    "External"=dword:00000000
    "ManufactureName"="ST332062 0AS SCSI Disk Device"
    "BusType"="SCSI"
    "DevicePath"="\\\\?\\PhysicalDrive6"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\5a9e5282-0000-0000-0000-000000000000]
    "FriendlyName"="System disk"
    "SystemName"="5a9e5282-0000-0000-0000-000000000000"
    "Size"="250059350016"
    "ObjectID"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\5a9e5282-0000-0000-0000-000000000000\Attributes]
    "DevicePath"="\\\\?\\PhysicalDrive2"
    "BusType"="ATA"
    "ManufactureName"="WDC WD2500JB-00GVC0"
    "External"=dword:00000000
    "QRole"=dword:00000001
    "ReadOnly"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\7cc8b174-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk ST3500630A"
    "SystemName"="88f643cf-0000-0000-0000-000000000000"
    "Size"="500107862016"
    "ObjectID"=dword:0000002f

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\7cc8b174-0000-0000-0000-000000000000\Attributes]
    "QRole"=dword:00000002
    "External"=dword:00000000
    "ManufactureName"="ST3500630A"
    "BusType"="ATA"
    "DevicePath"="\\\\?\\PhysicalDrive0"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\812f086a-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk ST3320620AS"
    "SystemName"="812f0853-0000-0000-0000-000000000000"
    "Size"="320072933376"
    "ObjectID"=dword:0000000d

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\812f086a-0000-0000-0000-000000000000\Attributes]
    "DevicePath"="\\\\?\\PhysicalDrive5"
    "BusType"="SCSI"
    "ManufactureName"="ST332062 0AS SCSI Disk Device"
    "External"=dword:00000000
    "QRole"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\812f086b-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk ST332062 0AS SCSI Disk Device"
    "SystemName"="812f0856-0000-0000-0000-000000000000"
    "Size"="320072933376"
    "ObjectID"=dword:0000000f

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\812f086b-0000-0000-0000-000000000000\Attributes]
    "DevicePath"="\\\\?\\PhysicalDrive7"
    "BusType"="SCSI"
    "ManufactureName"="ST332062 0AS SCSI Disk Device"
    "External"=dword:00000000
    "QRole"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\d3422bf4-0000-0000-0000-000000000000]
    "FriendlyName"="Unknown disk "
    "SystemName"="d3422bf7-0000-0000-0000-000000000000"
    "Size"="750156374016"
    "ObjectID"=dword:00000027

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Disks\d3422bf4-0000-0000-0000-000000000000\Attributes]
    "QRole"=dword:00000002
    "External"=dword:00000000
    "ManufactureName"="WDC WD7500AACS-00ZJB0"
    "BusType"="ATA"
    "DevicePath"="\\\\?\\PhysicalDrive1"

    And here are the volumes:
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e3b7e8d-3946-4375-96db-69d119f2e92b]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\E\\"
    "SystemName"="\\\\?\\Volume{0ed70123-b9b1-11dc-a3da-0004616a249a}\\"
    "Size"="320062063104"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:0000000e

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e3b7e8d-3946-4375-96db-69d119f2e92b\812f086a-0000-0000-0000-000000000000]
    "32256"="320062063104"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e3b7e8d-3946-4375-96db-69d119f2e92b\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{0ed70123-b9b1-11dc-a3da-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e8b624b-c60a-490d-8b5a-4d7fcda86281]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\X\\"
    "SystemName"="\\\\?\\Volume{cef558b3-fe9b-11dc-b8f7-0004616a249a}\\"
    "Size"="200038777344"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000021

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e8b624b-c60a-490d-8b5a-4d7fcda86281\30bba0a7-0000-0000-0000-000000000000]
    "32256"="200038777344"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\2e8b624b-c60a-490d-8b5a-4d7fcda86281\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{cef558b3-fe9b-11dc-b8f7-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\460f3579-202c-4ed1-a6d7-e335fd06820b]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\R\\"
    "SystemName"="\\\\?\\Volume{bf439805-c155-11dc-9493-0004616a249a}\\"
    "Size"="160031015424"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:0000001b

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\460f3579-202c-4ed1-a6d7-e335fd06820b\16381637-0000-0000-0000-000000000000]
    "32256"="160031015424"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\460f3579-202c-4ed1-a6d7-e335fd06820b\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{bf439805-c155-11dc-9493-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\50c77046-a5ad-41c9-88d0-05aa97b6ee6d]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\G\\"
    "SystemName"="\\\\?\\Volume{0ed70128-b9b1-11dc-a3da-0004616a249a}\\"
    "Size"="320062063104"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\50c77046-a5ad-41c9-88d0-05aa97b6ee6d\812f086b-0000-0000-0000-000000000000]
    "32256"="320062063104"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\50c77046-a5ad-41c9-88d0-05aa97b6ee6d\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{0ed70128-b9b1-11dc-a3da-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\56112f64-7a3f-4564-8ece-d7407ad576f4]
    "FriendlyName"="SYS"
    "MountPoint"="C:\\"
    "SystemName"="\\\\?\\Volume{b474ec9d-b96e-11dc-9e1c-806e6f6e6963}\\"
    "Size"="21476173824"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\56112f64-7a3f-4564-8ece-d7407ad576f4\5a9e5282-0000-0000-0000-000000000000]
    "32256"="21476173824"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\56112f64-7a3f-4564-8ece-d7407ad576f4\Attributes]
    "ReadOnly"=dword:00000001
    "DevicePath"="\\\\?\\Volume{b474ec9d-b96e-11dc-9e1c-806e6f6e6963}\\"
    "VolumeType"=dword:00000003

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\79e171c9-577b-4969-b079-0fec16ac1efc]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\1C\\"
    "SystemName"="\\\\?\\Volume{070f0898-3999-11dd-a218-0004616a249a}\\"
    "Size"="500096991744"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000030

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\79e171c9-577b-4969-b079-0fec16ac1efc\7cc8b174-0000-0000-0000-000000000000]
    "32256"="500096991744"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\79e171c9-577b-4969-b079-0fec16ac1efc\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{070f0898-3999-11dd-a218-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\11\\"
    "SystemName"="\\\\?\\Volume{f330c60f-ff87-11dc-9ee2-0004616a249a}\\"
    "Size"="500096991744"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000025

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\00000001-0000-0000-0000-000000000000]
    "32256"="500096991744"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\Attributes]
    "QRole"=dword:00000002
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a7c3dcaf-b6b5-44d3-9856-95e32282c906]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\1A\\"
    "SystemName"="\\\\?\\Volume{d4ae2f5d-38f4-11dd-a507-0004616a249a}\\"
    "Size"="320062063104"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:0000002e

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a7c3dcaf-b6b5-44d3-9856-95e32282c906\00000001-0000-0000-0000-000000000000]
    "32256"="320062063104"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a7c3dcaf-b6b5-44d3-9856-95e32282c906\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{d4ae2f5d-38f4-11dd-a507-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a8c94999-5e83-4fb3-92da-00dac4a1a2a3]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\14\\"
    "SystemName"="\\\\?\\Volume{5cbb45c9-08c2-11dd-920c-0004616a249a}\\"
    "Size"="750145503744"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000028

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a8c94999-5e83-4fb3-92da-00dac4a1a2a3\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{5cbb45c9-08c2-11dd-920c-0004616a249a}\\"
    "VolumeType"=dword:00000010

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\a8c94999-5e83-4fb3-92da-00dac4a1a2a3\d3422bf4-0000-0000-0000-000000000000]
    "32256"="750145503744"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\b0a56225-2cc9-4ab4-b565-16810599b7c5]
    "FriendlyName"="Primary Volume"
    "MountPoint"="D:\\"
    "SystemName"="\\\\?\\Volume{0058d2b9-b9b5-11dc-8c7c-92bc1f220c38}\\"
    "Size"="228572305920"
    "SnapPeriod"=dword:02932e00
    "ObjectID"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\b0a56225-2cc9-4ab4-b565-16810599b7c5\5a9e5282-0000-0000-0000-000000000000]
    "21476206080"="228572305920"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\b0a56225-2cc9-4ab4-b565-16810599b7c5\Attributes]
    "IsPrimary"=dword:00000001
    "DevicePath"="\\\\?\\Volume{0058d2b9-b9b5-11dc-8c7c-92bc1f220c38}\\"
    "VolumeType"=dword:00000008

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\d5e31ed8-ee51-4c51-9652-bf8310f72387]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\L\\"
    "SystemName"="\\\\?\\Volume{40ce2a08-bb34-11dc-b15a-0004616a249a}\\"
    "Size"="320062063104"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000015

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\d5e31ed8-ee51-4c51-9652-bf8310f72387\4c1ec00b-0000-0000-0000-000000000000]
    "32256"="320062063104"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\d5e31ed8-ee51-4c51-9652-bf8310f72387\Attributes]
    "QRole"=dword:00000002
    "DevicePath"="\\\\?\\Volume{40ce2a08-bb34-11dc-b15a-0004616a249a}\\"
    "VolumeType"=dword:00000010


    Saturday, December 20, 2008 7:44 PM

Answers

  • Well, I decided that if I was going to have to re-install anyway, what was the harm in trying to hack at the registry first?  So I deleted the section indicated above and any other place where the volume "7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c" was in a key, and my storage now appears to be back -- or at least the disk is no longer showing as "missing".  I guess I got lucky there that I didn't screw anything else up in the process.

    The bummer is that I still have a ton of "file conflict" errors, probably because (back in April/May) I added back that 500gb drive that wasn't really missing in the first place, in the process I formatted it and I'm sure that's where all of the missing stuff went.  And I also still have a warning that my backup database is corrupt -- again, probably out of luck there (and with my dead laptop hdd), but I'll run the storage diagnostic from the WHS toolkit and see what happens.

    Not quite ready to mark this one resolved yet, but I'll come back later to do that if everything goes okay from the storage diagnostic.

    Thanks to everyone for your suggestions.  If it hadn't been for the responses to that earlier post (http://social.microsoft.com/forums/en-US/whssoftware/thread/d322ea2a-e056-45c6-ac20-e4d170ceadb8/), I probably wouldn't have had the inspiration to give this a try.
    • Marked as answer by Kerath Friday, December 26, 2008 4:20 PM
    Sunday, December 21, 2008 7:39 PM

All replies

  • Hi,
    since the disk is still visible in disk management - did it get also a drive letter assigned?
    In this case you can check for the content (after enabling Show hidden files and folders in Control Panel/Folder Options on the server) using Windows Explorer in a local session on the server. Since it is not detected in the WHS console, you could also assign a drive letter manually in disk management.
    Of special interest for you is the folder DE\shares, which could contain parts of the shared folders or duplicates.
    If you find files here you wish to keep, copy them off to another location.
    Install the remaining upgrades for Windows Home Server, if not already done (one of them solved also some difficulties, which could happen in the next step).
    After finishing this, try to remove the disk via console from the storage pool.
    If this fails, disconnect the disk physically and try to remove it again via console.

    After completing this hopefully successfully, you should check the disk for broken sectors with ckdsk /r /f.
    If nothing is found, you can reintegrate the disk, maybe you have to reinitialize it before as outlined here.

    Best greetings from Germany
    Olaf
    Saturday, December 20, 2008 11:26 PM
    Moderator
  • Thanks for the suggestion.  I actually think the disc itself is fine.  I just spent some time going thru the registry snipits I've posted above, and I think I've identified the problem.

    In the section under "volumes", both entries for Mount Point " c:\\fs\\11\\" and "c:\\fs\\1A\\" appear to be pointing at the disk with the identifier "00000001-0000-0000-0000-000000000000", and in the case of " c:\\fs\\11\\", the size is clearly incorrect.

    I'm thinking that what I need to do is remove the whole section of registry related to the " c:\\fs\\11\\" volume, but that is just a barely-educated guess.

    Any thoughts on what it might do if I surgically remove the following section out of the registry?

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\11\\"
    "SystemName"="\\\\?\\Volume{f330c60f-ff87-11dc-9ee2-0004616a249a}\\"
    "Size"="500096991744"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000025

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\00000001-0000-0000-0000-000000000000]
    "32256"="500096991744"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\Attributes]
    "QRole"=dword:00000002
    "VolumeType"=dword:00000010

    Any chance I'll get myself into an unbootable condition?  Is this likely to solve the problem?

    Also, any idea what caused this in the first place?  Did I stumble upon a bug?
    Sunday, December 21, 2008 3:02 AM
  • Kerath said:

    Thanks for the suggestion.  I actually think the disc itself is fine.  I just spent some time going thru the registry snipits I've posted above, and I think I've identified the problem.

    In the section under "volumes", both entries for Mount Point " c:\\fs\\11\\" and "c:\\fs\\1A\\" appear to be pointing at the disk with the identifier "00000001-0000-0000-0000-000000000000", and in the case of " c:\\fs\\11\\", the size is clearly incorrect.

    I'm thinking that what I need to do is remove the whole section of registry related to the " c:\\fs\\11\\" volume, but that is just a barely-educated guess.

    Any thoughts on what it might do if I surgically remove the following section out of the registry?

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c]
    "FriendlyName"="DE Secondary Volume"
    "MountPoint"="c:\\fs\\11\\"
    "SystemName"="\\\\?\\Volume{f330c60f-ff87-11dc-9ee2-0004616a249a}\\"
    "Size"="500096991744"
    "SnapPeriod"=dword:00000000
    "ObjectID"=dword:00000025

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\00000001-0000-0000-0000-000000000000]
    "32256"="500096991744"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c\Attributes]
    "QRole"=dword:00000002
    "VolumeType"=dword:00000010

    Any chance I'll get myself into an unbootable condition?  Is this likely to solve the problem?

    Also, any idea what caused this in the first place?  Did I stumble upon a bug?



    Before attempting such a drastic step, have you tried Server Reinstallation?
    Sunday, December 21, 2008 4:00 AM
    Moderator
  • I think I looked at re-installing at one point over the summer, but I wasn't confident based on the options the boot DVD was giving me that I wasn't about to hose the entire setup including all of my data.  Is there a guide to re-installation somewhere on this forum?  I looked around for it some, but there are so many posts where re-installation is suggested that it's hard to find a guide (if it exists) using the search facility.

    Thanks so much for your help and suggestions.  I'm a little anxious about getting this fixed because now I have a dead laptop hdd, and the backup restore to the new drive keeps failing -- I fear it's failing because of this disk issue.  I just hope it doesn't turn out that the restore needs a file that was on that borked volume.  I should've tried to fix this problem ages ago, but it really didn't seem to be hurting much of anything and I had other fish to fry.  But this is all probably another post/thread.
    Sunday, December 21, 2008 4:28 AM
  • Reinstallation:
    • You boot from your WHS installation media.
    • You supply storage drivers if needed at the hardware discovery screen, so that WHS will see all of your hard drives. (Note that if, without drivers, you see no drives at all, you will need to supply drivers on floppy, and twice; the seond time is just after the reboot into text mode, at the "Press F6" prompt).
    • If WHS sees all your drives, when you are asked what kind of installation you want to perform you should see an option for server reinstallation or server recovery, in addition to new installation.
    • You choose reinstallation, and walk away for a few hours.
    Your shares will be preserved, as will home computer backups (normally). You will lose users (but not their personal folders on the server), add-ins you've installed and other software or configuration changes you've made through the server desktop.

    I'm not on the WHS team, I just post a lot. :)
    Sunday, December 21, 2008 2:57 PM
    Moderator
  • Well, I decided that if I was going to have to re-install anyway, what was the harm in trying to hack at the registry first?  So I deleted the section indicated above and any other place where the volume "7fe0db45-8548-4bfd-b7e3-c8ab1a1f999c" was in a key, and my storage now appears to be back -- or at least the disk is no longer showing as "missing".  I guess I got lucky there that I didn't screw anything else up in the process.

    The bummer is that I still have a ton of "file conflict" errors, probably because (back in April/May) I added back that 500gb drive that wasn't really missing in the first place, in the process I formatted it and I'm sure that's where all of the missing stuff went.  And I also still have a warning that my backup database is corrupt -- again, probably out of luck there (and with my dead laptop hdd), but I'll run the storage diagnostic from the WHS toolkit and see what happens.

    Not quite ready to mark this one resolved yet, but I'll come back later to do that if everything goes okay from the storage diagnostic.

    Thanks to everyone for your suggestions.  If it hadn't been for the responses to that earlier post (http://social.microsoft.com/forums/en-US/whssoftware/thread/d322ea2a-e056-45c6-ac20-e4d170ceadb8/), I probably wouldn't have had the inspiration to give this a try.
    • Marked as answer by Kerath Friday, December 26, 2008 4:20 PM
    Sunday, December 21, 2008 7:39 PM
  • Hi,
    for getting rid of the broken tombstones you can try, if the tool WHSCleanup still works.

    Best greetings from Germany
    Olaf
    Sunday, December 21, 2008 7:46 PM
    Moderator