Tuesday, October 14, 2014

Windows Server 2012 R2 – Couldn’t Create A New Partition

I have spent a couple hours this weekend to troubleshoot a partition creation issue during the Windows Server 2012 R2 installation.  I was getting the infamous “We couldn’t create a new partition or locate an existing one.  Fore more information, see the Setup log files” error message.

image

I have tried all the DISKPART recommendations on the following TechNet blogs:

http://blogs.technet.com/b/mempson/archive/2012/12/13/windows-8-and-the-dreaded-couldn-t-create-a-new-partition.aspx

http://blogs.technet.com/b/asiasupp/archive/2012/03/06/error-quot-we-couldn-t-create-a-new-partition-or-locate-an-existing-one-for-more-information-see-the-setup-log-files-quot-when-you-try-to-install-windows-8-cp.aspx

In my case, the issue was related to the boot order or sequence in the BIOS.   I was trying to install OS on to an SSD drive.  It was the first boot device configured in the BIOS.  Once I change the SSD drive to the 2nd place, everything start working! 

12 comments:

This comment has been removed by the author.

Thanks! Had to do opposite on a Poweredge 1900 but you put me on the right track. I had to configure the SATA A attached device to boot order #1. I tried #2 and #3 and got the above error. When I moved it to #1 it worked fine.

followed all the directions on the web and apparently my problem was I was using a usb 3.0 thumb drive switched to a 2.0 and it worked like a champ. here is the info tha pushed me to the usb 2.0 stick. http://jermsmit.com/server-2012-we-couldnt-create-a-new-partition-or-locate-an-existing-one/

followed all the directions on the web and apparently my problem was I was using a usb 3.0 thumb drive switched to a 2.0 and it worked like a champ. here is the info tha pushed me to the usb 2.0 stick. http://jermsmit.com/server-2012-we-couldnt-create-a-new-partition-or-locate-an-existing-one/

I had the exact same error message when installing Windows Svr 2012 90 day evaluation on a DIY PC with an Asus P5Q SE R mobo. It was resolved when I moved up the order of the hard disk inside the “hard disk” section of my bios. - bruce tong

Our Dell 620 came with the Internal SD:Internal Dual SD and it's Hard-Disk Drive Sequence was on top in the System BIOS. I moved it down 1 position which moved the Integrated Raid Controller up one and We were able to load Server 2012. Dell said the server was shipped ESXi ready with the ESXi softare pre-installed on that SD drive.

I gotten bitten by the USB 3.0 to 2.0 as well. As soon as I put it on a 2.0 thumb drive everything was fine!

In my case the genius at the factory named both raid volumes as volume0. install was confused, even though I know I tried both options in BIOS (set as boot device). after killing one and renaming the volume, I could suddenly install :)

In my case, one of two things worked: moving the USB pen drive from the front to the rear motherboard board sockets or unplugging a USB 3 hard drive that I happened to also have plugged in (had just taken image of old server)

I moved my SSD Raid Array out of the first position in the Boot Order and had no luck. It wasn't until I moved the USB Drive that I was booting from to a position BEFORE the SSD Raid Array that it worked for me.

When You have an USB attached, this error occurs...just disable USB in BIOS an try again. I got install after that.

Post a Comment

Popular Posts

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More