Kknd 2 Couldn't Create New Unit

'We couldn't create a new partition or locate an existing one' in Installation and Upgrade So I'm trying to install Windows 10 32-bit on a friend's laptop from a USB stick and it's giving me this error, no matter what I do. Self Repair (2) Gives the unit the ability to repair itself, so long as it is not moving or attacking. Radar Jam (2) Creates a field around itself, preventing the unit from showing up on radar. Destruct (2) Packs some mean explosives into your unit, so that when it does, it explodes in a nasty area-of-effect kinda way.

1. Kknd 2 Couldn't Create New Unit 1
2. Kknd 2 Couldn't Create New Unit Full

Long story short. Client's server went belly up. Trying to boot into Windows just started an endless loop of Windows trying to repair itself. Booting into safe mode or safe mode with networking didn't help.Trying to repair windows also didn't help.Now here's the rub.Server is a Gen8 Proliant ML360. The previous IT people set it up with 4 x 4TB drives in RAID 5, then created 2 logical drives. 1 of 80GB for the OS and the other is a data drive that has 10TB of files.The data drive is not backed up (because apparently it's not important). Apart from the fact that now all of a sudden it is.Our initial thought was to boot from a server 2012 R2 ISO and reinstall the OS, but it's having none of it.

We can still access the data drive via the CLI, so we know that's safe.Trying to install the OS gives an error of ' We couldn’t create a new partition or locate an existing one. For more information, see the Setup log files.' I've Googled this to hell and back.So far off the back of the results I've.1) Done the diskpart thing, cleared the disk, reformatted, set as primary and tried to reinstall2) Ensured that I'm not using a USB not formatted as NTFS for the install3) Set the RAID card as the first boot device4) NOT set the RAID card as the first boot device5) Ensured that I'm not using a USB 3.0 device6) Tried to do the setup via the HP ProvisioningAnyone else got any further ideas?At this point I'm at 'boot it from a Linux USB, get the data off, nuke from orbit'. Have you got a Linux Live CD/DVD laying around and try booting with that, if that works I would suggest re-burning your Windows DVD and try that.I've also had a DVD which had decided not to boot, so I just shredded DVD after creating new one which did boot, odd but trueJust a thought, you could always try and put ESXi and virtualise on this box and then it saves DBANing each time the eval is up, just delete VM and create new and install again (assuming of course it can read the DVD - as does not have to boot from it). Huw3481 wrote:DragonsRule wrote:Huw3481 wrote:Trying to install the OS gives an error of ' We couldn’t create a new partition or locate an existing one.

For more information, see the Setup log files.' That's almost always a RAID / SATA driver issue. The installer can't find the drive.That's what the Intelligent Provisioning route is supposed to avoid. The CLI can still see the drives.I've never used that. Does it have an option to Add Drivers during the install, like a normal Server install does? DragonsRule wrote:Huw3481 wrote:DragonsRule wrote:Huw3481 wrote:Trying to install the OS gives an error of ' We couldn’t create a new partition or locate an existing one.

Kknd 2 Couldn't Create New Unit 1

For more information, see the Setup log files.' That's almost always a RAID / SATA driver issue. The installer can't find the drive.That's what the Intelligent Provisioning route is supposed to avoid. The CLI can still see the drives.I've never used that. Does it have an option to Add Drivers during the install, like a normal Server install does?It usually contains all the drivers built-in to the FW of the server or it pulls them from HP if internet is available.

It used to be the SBS disc. DragonsRule wrote:Huw3481 wrote:Server is a Gen8 Proliant ML360. The previous IT people set it up with 4 x 4TB drives in RAID 5, then created 2 logical drives.

1 of 80GB for the OS and the other is a data drive that has 10TB of files.Have you considered starting clean so you can get them over to RAID10?-edit - ah, shit. 10TB of data? Sell them new drives and go to RAID10?If there was any money available, they'd have bought the storage to allow for the 10TB to be backed up and we wouldn't be having this conversation;). Rod-IT wrote:Huw3481 wrote:Rod-IT wrote:The data is still there after the clean though, usually clean hits the disk, not the partition, I assume this is one RAID broken in to partitionsI believe I made that point in the original post.4 x 4TB in RAID5, 2 logical disks - 80GB OS and the rest as a data drive.Clarification was all I was after.If your drives are set as GPT you need to install the OS a specific way, you should be able to tell from diskpart.Mmmm. Never considered that.Diskpart Convert MBR should work, right?

Ripper wrote:Huw3481 wrote:DragonsRule wrote:Huw3481 wrote:Trying to install the OS gives an error of ' We couldn’t create a new partition or locate an existing one. For more information, see the Setup log files.' That's almost always a RAID / SATA driver issue.

Kknd 2 Couldn't Create New Unit Full

The installer can't find the drive.That's what the Intelligent Provisioning route is supposed to avoid. The CLI can still see the drives.Load the RAID drivers on a USB and plug it in anyway.

Then, at least you can eliminate it as a possibility.That fixed it. Odd, as Intelligent Provisioning should do that.