locked
Missing a drive... but I'm not! RRS feed

  • Question

  • Hi there,

    Been running Home Server since the beta days and it's been fine for the most part.  However, I've just run into something very odd:

    • Console is reporting that a drive is not added (been added for years now)
    • No new drives have been added for a few months
    • The mountpoint is there under C:\fs\L
    • I can access all of the data through said mountpoint
    • Disk Management plugin is saying that the drive (Disk 0) is Healthy
    • I have one non-duplicated folder; I can get to the files on this drive on the non-duplicated folder from other machines on the network!
    • Console is going nuts saying the majority of my shares are failing
    • Saying there are tons of file conflicts

    Any idea what is going on here?

     

    Thanks

    Thursday, June 17, 2010 5:57 AM

All replies

  • Just found this in the QSM.log:

     

    Attribute [InstanceID] is added to the attributesList and the value is [\\?\ide#diskwdc_wd5000aaks-00tma0___________________12.01c01#2020202057202d44435750413257323133323837#{53f56307-b6bf-11d0-94f2-]
    Attribute [DevicePath] is added to the attributesList and the value is [\\?\PhysicalDrive0]
    Attribute [BusType] is added to the attributesList and the value is [ATA]
    Attribute [ManufactureName] is added to the attributesList and the value is [WDC WD5000AAKS-00TMA0]
    Attribute [External] is added to the attributesList and the value is [0]
    Attribute [QRole] is added to the attributesList and the value is [2]
    INIT: Created disk object from registry.
          Name:          c73e02fa-0000-0000-0000-000000000000
          Friendly Name: Unknown disk WDC WD5000AAKS-00TMA0
          System Name:   3efe1f19-0000-0000-0000-000000000000
          Size:          500107862016
          ObjectID:      20
    End reading disk state from registry
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk WDC WD5000AAKS-00TMA0) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (System disk) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk ST3500630AS) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk WDC WD5000AAKS-00TMA0) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (System disk) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk ST3500630AS) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (Unknown disk ) QSM_OS_INITIALIZED => QSM_OS_MISSING
    [6/16/2010 7:23:45 PM  aac] LoadDisk: Found disk \\?\PhysicalDrive0
    Disk a9cdc6e6-a5a5-47af-b273-f77b94d59afa
        Name: \\?\PhysicalDrive0
        Friendly Name: ST31000340AS
        Device Name:  ST31000340AS 2020202020202020202020205133304A4A303841
        Address: Port3Path0Target2Lun0
        Device path: \\?\ide#diskst31000340as____________________________sd1a____#2020202020202020202020205133304a4a303841#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
        Adaptor: NVIDIA MCP51 Serial ATA Controller
        Status: ONLINE
        Health: HEALTHY
        Device type: DISK
        Media type: 0x0000000c
        Size: 1000204886016
        Bytes per sector: 512
        Sectors per track: 63
        Tracks per cylinder: 255
        Flags: 0x00000000
        Bus type: VDSBusTypeAta
        Partition style: MBR
        Signature: 0x6a3abfd4
    Disk 6a3abfd4-0000-0000-0000-000000000000 already exists in system (as System disk).
    Attribute [DevicePath] is found in the attributesList and its value is changed to [\\?\PhysicalDrive0]
    Attribute [BusType] is found in the attributesList and its value is changed to [ATA]
    Attribute [InstanceID] is found in the attributesList and its value is changed to [\\?\ide#diskst31000340as____________________________sd1a____#2020202020202020202020205133304a4a303841#{53f56307-b6bf-11d0-94f2-]
    Attribute [External] is found in the attributesList and its value is changed to [0]
    [6/16/2010 7:23:45 PM  aac] SetObjectSelfHealth (System disk) QSM_OS_MISSING => QSM_OS_HEALTHY
    [6/16/2010 7:23:45 PM  aac] SetObjectHealth (System disk) QSM_OS_MISSING => QSM_OS_HEALTHY
    DiskEvent started
    ComputeAdviseArray started
    ComputeAdviseArray ended (0)
    DiskEvent ended

    Thursday, June 17, 2010 6:14 AM
  • So, in the Disk Management plugin, DISK0 is the disk that Home Server is reporting missing.  Looking at the log file, it looks like it's moving my system drive (C & D) to PHYSICALDRIVE0 over top of the the other drive.  (I'm assuming that PhysicalDrive0 in the QSM log file is the equivalent to the name of the drive in the Disk Manager plugin).

     

    Am I on the right path here?

    Thursday, June 17, 2010 6:19 AM
  • Last one for the night...

     

    In HKLM\Software\Microsoft\Windows Home Server\Storage Manager\Disks\

     

    My system disk has a device path of \\?\PhysicalDisk3 and the disk that is reported as missing is \\?\PhysicalDisk0.

     

    So if I grok what's going down, WHS is saying my storage drive does not deserve the PhysicalDisk0 name, booting it out of the club and giving that name to my system drive?

    Thursday, June 17, 2010 6:28 AM