ngraf Posted October 31, 2005 Share Posted October 31, 2005 I'm using WinPE 2004 but the same thing happens in at least one older version.I cannot assign an access path (mount point) to a newly created partition with diskpart. I try the following:select disk 5create partition primary size=2000select volume 6assign mount=K:\mntAnd get this error message:DiskPart could not assign the drive letter or mount point.Make sure the drive letter or mount point is valid.Assigning a drive letter to the partition works:select volume 6assign letter=GMounting an existing partition at the same point works:select volume 5assign mount=K:\mntIf I reboot WinPe, the previously failed command now succeeds:select volume 6assign mount=K:\mntIt seems that some discovery task occurs at boot that does not occur when the partition is created.Has anybody else seen this? Does anybody know how to fix it without a reboot?Thanks! Link to comment Share on other sites More sharing options...
staples Posted October 31, 2005 Share Posted October 31, 2005 Open a case with microsoft... there are issues with diskpart where not all the time after you create the partition you fail on assigning the drive letter.It seems that creating and assigning in the same file fails (at least for me) 25% - 50% of the time.Hotfix is almost fully regression tested. Link to comment Share on other sites More sharing options...
ngraf Posted October 31, 2005 Author Share Posted October 31, 2005 Thanks for the response. I'm in the process of contacting MS but was hoping this forum would be faster.I've seen the posts about drive letter assignments failing from scripts. But in my case, drive letter assignments work just fine. Also, this happens when entering the commands interactively and waiting for several minutes (sometimes hours) between creating the partition and attempting to mount it. Link to comment Share on other sites More sharing options...
staples Posted November 1, 2005 Share Posted November 1, 2005 Same issue.As soon as I get the result (kb article) I will probably post it.... it should be public with everyone experiencing the same issue. Link to comment Share on other sites More sharing options...
getwired Posted November 1, 2005 Share Posted November 1, 2005 (edited) You shouldn't ever have to reboot just to pick up a new partition - have you run rescan from diskpart after creating your new partition(s)? Edited November 1, 2005 by getwired Link to comment Share on other sites More sharing options...
ChrisBaksa Posted November 1, 2005 Share Posted November 1, 2005 This is due to how the OS discovers the Volume.Ever put a cd in XP and it never displays teh contents?You must actually "Kick" the OS awake and force it to discover the new volume. I do this by using a tool we wrote in house that Queries the drive partitions and writes out the Boot Record to to a file in the ram drive. This causes the OS to go thru it's motions which will discover the new voume. It has been Very reliable. Before that... It was a crap shoot. Chris Link to comment Share on other sites More sharing options...
ngraf Posted November 1, 2005 Author Share Posted November 1, 2005 I have tried to rescan the disks but it didn't help.I'm also trying to avoid doing anything to "Kick the OS awake" because I've done things like that plenty of times in the past and the OS always picks the worst moment to refuse to wake up. I think I'll wait for the hotfix. Link to comment Share on other sites More sharing options...
staples Posted February 8, 2006 Share Posted February 8, 2006 Hotfix is out to Fix Diskpart issues. It is actually the disk subsystem dlls.http://support.microsoft.com/?kbid=910380Have to contact support for the fix though. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now