Home > Windows Server Tips > Windows Hardware Strategies > When Windows PE fails to set up disk partitions
Windows Server Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

WINDOWS HARDWARE STRATEGIES

When Windows PE fails to set up disk partitions


Rick Cook, Contributor
02.09.2006
Rating: --- (out of 5)


Expert advice on Windows-based systems and hardware
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


Windows Preinstallation (PE) Environment makes life easier for administrators who must configure and manage large numbers of Windows XP Professional and Windows Server 2003 systems. PE works with Remote Installation Server (RIS) to let admins set up and install standard configurations for Windows systems across a network. This is much easier than having to visit each system to install the same configuration over and over.

But the process sometimes goes awry. When you use the Diskpart.exe tool to create partitions on a RAID set that includes raw disks, the system may fail to create the disk partitions. After about three minutes, you will get this error message: "The disk management services could not complete the operation."

If you quit Diskpart.exe and try again, you'll get the same error message. But if you restart the system in Windows PE and run Diskpart.exe again, the process will complete successfully.

What is happening is that the Volsnap.sys driver doesn't have any device object associated with it when Windows PE starts from a RIS server on a system that includes raw disks. In these circumstances, when Diskpart.exe creates a volume, the system can't find the Volsnap.sys driver, so the I/O Manager attempts to unload the Volsnap.sys driver. However, this operation fails because of an outstanding reference to the driver object. Unfortunately the failure doesn't remove Volsnap.sys from loaded modules list. This leaves things in a confused state and the confusion escalates when Diskpart.exe tries to create a volume.

As part of the volume creation process, Diskpart.exe searches the driver list for Volsnap.sys. When it doesn't find it, the system tries to load Volsnap.sys, but that fails because according to the loaded modules list, Volsnap.sys is already loaded.

Microsoft has introduced a hotfix for this problem. To use the hotfix on 32-bit systems you must have Service Pack 1 installed on Windows Server 2003. The 64-bit versions of Windows already contain the SP1 fixes.


Rick Cook has been writing about mass storage since the days when the term meant an 80K floppy disk. The computers he learned on used ferrite cores and magnetic drums. For the last 20 years he has been a freelance writer specializing in issues related to storage and storage management.

More information from SearchWinSystems.com


Rate this Tip
To rate tips, you must be a member of SearchWindowsServer.com.
Register now to start rating these tips. Log in if you are already a member.




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



RELATED CONTENT
Windows Hardware Strategies
Availability in the virtualized Windows server
Hardware considerations for Windows server virtualization
Scaling Windows server resources for virtualization
Troubleshooting your toughest Windows server crashes
High-tech solutions for monitoring computer heat
Server virtualization at the hardware level with Hyper-V
Virtualization and 64-bit: A match made in Windows heaven
How to use the g4u network-based hard disk cloning utility
Multi-core processors on the desktop offer major boost
When and how to migrate to a 64-bit platform

Windows Systems and Network Administration
How to use Group Policy to centralize system configurations
Troubleshooting Windows application crashes or hangs
Converting VMware ESX machines to Hyper-V format
Using DFSR for SYSVOL replication in Windows Server 2008
Top 25 Windows PowerShell commands for administrators
Key DFS improvements in Windows Server 2008 R2
Free Windows security tools every admin must have
Group Policy makes strides in Windows Server 2008 R2
Quick tips for troubleshooting NTFS permissions
Common causes of Windows server security vulnerabilities

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Server Room Design - Planning, Cooling, Maintenance
HomeTopicsBlogsITKnowledge ExchangeTipsNewsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts