locked
Storage Status error - USB drive and backups - Critical Health warning RRS feed

  • Question

  • Does anyone have an idea how to correct this self-inflicted error?

    I was RDP'd to the WHS (installing a printer on my machine at the time) and running a server backup to a USB drive (70Gb free - plenty of space for the incremental backup) when I discovered I had to power off the PC due to a driver error.

    Not thinking I doubled clicked the icon in the tool tray to start the console up forgetting it was running on the server in the RDP session.  This killed the backup stone dead but left me with two problems:

    1) The backup states it had finished - I know it did not as the folder with the printer software was not on the drive.  I deleted that backup from the console.

    2) The server status is now red due to a Storage Status critical error stating:

    Volume with name Unformatted Volume  \\?\Volume{GUID}\ has failed.  Please check hard drives and try to run Repair to fix errors for that disk

    All the drives are fine in server storage and do not show any option for repair.
    All drives have passed the basic chkdsk with no issues
    The server is running fine

    The only error I can find in the logs are:

    Two Event Type: Warning
    Event Source: Ftdisk
    Event Category: Disk
    Event ID: 57
    Date:  11/03/2009
    Time:  12:39:40
    User:  N/A
    Computer: KERMIT
    Description:
    The system failed to flush data to the transaction log. Corruption may occur.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 01 00 be 00   ......¾.
    0008: 02 00 00 00 39 00 04 80   ....9..€
    0010: 00 00 00 00 0e 00 00 c0   .......À
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........

    Five Event Type: Warning
    Event Source: Disk
    Event Category: None
    Event ID: 51
    Date:  11/03/2009
    Time:  12:40:03
    User:  N/A
    Computer: KERMIT
    Description:
    An error was detected on device \Device\Harddisk2 during a paging operation.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 03 01 68 00 01 00 ba 00   ..h...º.
    0008: 00 00 00 00 33 00 04 80   ....3..€
    0010: 2d 01 00 00 0e 00 00 c0   -......À
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 0b 9e 8d 04 00 00 00 00   .ž.....
    0030: ff ff ff ff 01 00 00 00   ÿÿÿÿ....
    0038: 40 00 00 08 00 00 00 00   @.......
    0040: 00 20 0a 12 40 03 20 40   . ..@. @
    0048: 00 00 00 00 0a 00 00 00   ........
    0050: 00 f0 20 d0 78 b8 45 88   .ð Ðx¸Eˆ
    0058: 00 00 00 00 70 a5 94 87   ....p¥”‡
    0060: 00 00 00 00 3f 58 77 11   ....?Xw.
    0068: 28 00 11 77 58 3f 00 00   (..wX?..
    0070: 08 00 00 00 00 00 00 00   ........
    0078: 00 00 00 00 00 00 00 00   ........
    0080: 00 00 00 00 00 00 00 00   ........
    0088: 00 00 00 00 00 00 00 00   ........

    One Event Type: Error
    Event Source: Virtual Disk Service
    Event Category: None
    Event ID: 10
    Date:  11/03/2009
    Time:  12:40:03
    User:  N/A
    Computer: KERMIT
    Description:
    Unexpected provider failure. Restarting the service may fix the problem. Error code: 8000FFFF@020A0008

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    And two Event Type: Information
    Event Source: PlugPlayManager
    Event Category: None
    Event ID: 271
    Date:  11/03/2009
    Time:  12:40:35
    User:  N/A
    Computer: KERMIT
    Description:
    The Plug and Play operation cannot be completed because a device driver is preventing the device from stopping. The name of the device driver is listed as the vetoing service name below.

     Vetoed device: USBSTOR\DISK&VEN_GENERIC&PROD_USB_DISK&REV_9.02\6&25444D1C&0
     Vetoing device: STORAGE\Volume\1&30a96598&0&Signature19FC437DOffset7E00Length45DCDC8200
     Vetoing service name: FileSystem\Ntfs
     Veto type 6: PNP_VetoDevice

     When Windows attempts to install, upgrade, remove, or reconfigure a device, it queries the driver responsible for that device to confirm that the operation can be performed. If any of these drivers denies permission (query-removal veto), then the computer must be restarted in order to complete the operation.

     User Action
     Restart your computer.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Following the advice to restart has not helped and the only other thread I came across is here did not get resolved.  The toolkit version 1.1 does not have anything for looking at disks (ChkDE seems to have been removed) even having 'pushed' it to the server and installed the add-on.

    I am on PP1 currently at:
    Windows Home Server Console: 6.0.1800.0
    Windows Home Server Backup & Restore: 6.0.1800.36
    Windows Home Server Drive Extender: 6.0.1800.24
    Windows Home Server Remote Access: 6.0.1800.0
    Windows Home Server Storage Manager: 6.0.1800.24

    Andrew
    http://kings-sleep.blogspot.com

    Wednesday, March 11, 2009 2:46 PM

All replies

  • Have you rebooted your server?
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, March 11, 2009 3:11 PM
    Moderator
  • Ive done a soft reboot and a full power off but to no avail.

    I have also tried removing the two fixes mentioned in this http://www.mediasmartserver.net/forums/viewtopic.php?f=5&t=3660 and http://www.mediasmartserver.net/forums/viewtopic.php?f=5&t=3635&start=30 as the server started to report the backup service was not running (even though it was)

    To make matters wrse the server is now logging QSM errors:

    Event Type: Error
    Event Source: HomeServer
    Event Category: QSM
    Event ID: 129
    Date:  12/03/2009
    Time:  22:27:08
    User:  N/A
    Computer: KERMIT
    Description:
    Assertion failure at d:\wssg_src\whs_pp1\qhs\src\storage\qsm\qsm.cxx(18621): pVolRunner->vdf.nDisks > 0

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    and I have no ideas on this one.

    Between this and the three lots of backup data I have lost my faith in the reliability of this box is about zero now.  I do not mind being on a beta but this has gone on too long - servers should be reliable and these are not.

    Thursday, March 12, 2009 11:02 PM
  • I would suggest that you submit a bug report on Connect. Include logs gathered from the server using the server portion of the Windows Home toolkit. If Microsoft needs more than that, they'll ask you for it. :)

    That said, two things jump out at me in the information you provided. First, as I think you recognize, access to your server through Remote Desktop is unsupported. Further, there are warnings in a number of places that actually working on your server in a Remote Desktop session has the potential to cause significant issues on your server. So in my opinion it's not reasonable to blame Microsoft for the issue you're experiencing, which can be traced back to using Remote Desktop in an unsupported fashion.

    The solution I would recommend is a server reinstallation. This will preserve the data in your shares, and your backup database. But please hold off on that for a few days so Microsoft can respond to your bug report.

    I'm not on the WHS team, I just post a lot. :)
    Friday, March 13, 2009 4:31 AM
    Moderator
  • No disrespect but if RDP is not to be used why did they not take it out like the rest of the items?

    Given that I was in the console program which uses RDP in a limited mode I think MS is on shakey ground...

    I'll open a bug report and update this thread if I get anywhere.
    Friday, March 13, 2009 7:20 AM
  • I can think of several reasons not to take Remote Desktop out. 
    1. The console uses Remote Desktop Protocol to remote the application to the client.
    2. The server supports Remote Desktop proxy services to access your home computers.
    3. Researching/solving certain issues requires access to the server desktop.
    4. Desktop access may be needed for people (developers and enthusiasts) to be able to extend their servers.
    Even given those reasons, access to the server desktop is still unsupported for the end user. Windows Home Server is intended to be easy to use for a non-technical person. The tools on a server desktop are not easy for most people to use.

    I'm not saying that you did something wrong, by the way. Just that you did something in an unsupported fashion. It's possible that Microsoft will determine that there's a bug in the way the console handles the situation you created. It's also possible that Microsoft will determine that the scenario you created is intentionally going to remain unsupported. I don't know, but I know that a bug report is the place to start. :)

    I'm not on the WHS team, I just post a lot. :)
    Friday, March 13, 2009 5:09 PM
    Moderator
  • Ive now uploaded the bug report (427867) and will give it a few days.

    Feeling is still that I cannot trust this with my backups but we will see.

    Andrew
    http://kings-sleep.blogspot.com
    Saturday, March 28, 2009 9:44 AM