Dynamic disks on SCSI controller fail to start automatically in Hyper-V
Dynamic disks on SCSI controller fail to start automatically in Hyper-V
RAPID PUBLISHING
Symptom
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://vkbexternal/VKBWebService/ViewContent.aspx?scid=kb;EN-US;256986&PortalId=1) Description of the Microsoft Windows registry
ÂÂ
In a Hyper-V guest operating system, dynamic disks attached to SCSI controllers will fail to show as available after a reboot. Only after activating the dynamic disk in disk management will it and any other dynamic disks come online.  When you restart, the same issue reoccurs again.
ÂÂ
This behavior is not seen with basic disks attached to a SCSI Controller or with basic or dynamic disks attached to the IDE controller.
ÂÂ
ÂÂ
ÂÂ
In disk management the disks are shown as Dynamic and Online, but where you should see the partition type (NTFS/FAT) the drive shows as FAILED. You may receive an error similar to the following:
ÂÂ
Event Type:     Error
Event Source:  dmboot
Event Category:           None
Event ID:         3
Date:               18-07-2008
Time:              17:03:17
User:               N/A
Computer:       W2K3SP2X64
Description:
dmboot: Failed to start volume Volume3 (G:)
ÂÂ
For more information, see Help and Support Center at: http://go.microsoft.com/fwlink/events.asp (http://go.microsoft.com/fwlink/events.asp)
Data:
0000: 00000000 004e0003 00000000 c0500003
0010: 00000000 00000000 00000001 00000000
0020: 00000000 00000000
ÂÂ
Resolution
To workaround this issue do the following:
In disk management right click on one of the failed dynamic disks, select ‘Reactivate Volume’
You’ll be prompted with the following: Warning: We recommend that you run chkdsk on the volume after it becomes available for use Click on [OK]. After disk management refreshes, you’ll be able to access the previously failed dynamic disks.
ÂÂ
To resolve this issue do the following:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Edit the registry of the child virtual machine:
ÂÂ
Under HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services storvsc
Change Start value from 3 to 0.
DISCLAIMER
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Back to the top
Leave a Reply