When Windows PE fails to set up disk partitions

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 fin

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Windows Hardware Strategies 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 64-bit Windows – help or hype? How to install low-voltage wiring such as Ethernet or coax cable Bluetooth card reader/USB hub reads files from offbeat media Windows Systems and Network Administration Common causes of Windows server security vulnerabilities Cutting the cost of Windows identity and access management Using NTFS on a non-Windows OS with NTFS-3G Group Policy Object modeling simplifies network security Implementing simple Network Access Protection for Windows Server 2008 Immediate steps for Windows disaster recovery Tips for Windows domain controller optimization Quick hits: Troubleshooting service account failure, batch job execution Case Study: Troubleshooting Windows service dependency failures Troubleshooting common Windows service failures

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

d 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.

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. 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.