Partition size error 0 MB on DL 360 Gen 9

[MJIT]

Hello there, 

we have a DL 360 Gen 9 configured with 3 x 600 GB HDDs, Array is Raid1 ADM. When I use Intelligent Provisionig the system tells me that my configured partition with 0 MB is smaller than recommended bla bla bla.

Any ideas what is wrong?

Attached pic is in german, but shows the error

[Mke]

Try removing the raid but this will only allow you to install the O/S on one drive. I have had the issues.

[Sondni]

Got the same error, pressed OK and continued on.(3 Drives in RAID 5)

Drives got partitioned to 0 MB and the innstallation continued.

Everything was innstalled and Windows shows the drive at the size of the logical drive.

[Jimmy Vance]

So it appears the workaround is to just click continue?

I have reported this issue to the Intelligent PRovisioning team and they are going to look into it.

Hopefully this is just an issue with the text being displayed incorrectly. Regardless, it should be corrected in the next release.

[shang1983]

I have the same issues. It display 0MB disk size.

I changed the bios to legacy mode and i'm able to see the disk space and able to adjust the size.

With UEFI mode, it display 0MB and not able to install window OS on intelligent provisioning and manual installation

[LogicalStep]

You need to go back the the raid configuration

& scroll down & select the boot drive

it will then work

[MOosterbeek]

Any progress on this matter?  We're experiencing the same issue here.

Unfortanately, none of the helpfull suggestions posted here seem to work for me. 

Went back to the RAID config, scrolled down, selected boot device.  Then went ahead and simply pressed OK despite the "0 mb message". 

At first it seemed to install just fine. No errors, nothing. But then at first boot it hangs...

Help would be most welcome!

[FaizalSalih]

Below fixed the issue  in my scenario.

Go to BIOS and change to legacy mode (for once) option. Please note that in legacy Bios you will not find intellegent Provisioning option.  Proceed to load the legacy bios option once it is loaded reset the server. On reset it will go back  to UEFI BIOS , choose intellegent provisining  now you can see the actual disk size.

[MatrixKev]

Hi, I've come up against the same problem today - switching to legacy mode in BIOS and then back to UEFI didn't work, and although I can skip past the 0MB partition size and the OS will install and boot fine, I then can't resize the partition to an acceptable size as it fills the logical drive up and then Windows writes data to the middle of the partition.

I spoke to HP support and they indicated that they're aware of this issue and their developers are currently looking into it, and at present the only guaranteed workaround is to do a manual install without Intelligent Provisioning.

They also acknowledged that their developers are still looking into the issue whereby Intelligent Provisioning doesn't install any of the HP management tools (System Management Homepage, Smart Storage Administrator, iLO Configuration Utility etc), I reported that to them a couple of months ago.

[StephaneB]

Hi

Same problem, but after 2 hours spent with french support (not aware of the problem) an idea which seems working and making less problem with system partition resizing in Windows.

- Creates an array with a logical drive of 120 Gb size

- Make installation with Intelligent Provisioning, choose customize, partition size is O Mb size, choose continue

- After Operating systeme setup, you can resize the logical drive in SSA to the full size of the array.

- Windows now see th full disk array size and you can manage your partition in windows.

You need to create a small logical drive first because instead Windows did not allow reducing the system partition less than the half of the nitial size (some unmouvable file are written in the middle of the partition).

Intelligent Provisioning 2.20 is full of bug :

- Problem with partition size using UEFI bios (works fine with legacy)

- Can't use French keyboard in IP screen

- Most of HP tools are not copy during setup (no array tools, no homepage...) as no cd provided we need to download the old SPP which is 5Gb size .

Please HP developpers wake up and make all your tools working fine as it was before. Price is not less but quality is not present and we spend more and more time preparing new server by finding solution to work with your tools.

[LarchComputers]

The "Go to BIOS and change to legacy mode (for once) option" worked.  If I had come here first, I could have saved 4 or 5 hours going round in circles.  That's all the margin on the server hardware blown!

[Anonymous]

- Problem with partition size using UEFI bios (works fine with legacy)

>we are aware and will be fixing this asap

>try and disable the onboard controller b140 first and then do the install, we only have been able to reproduce this in dual controller setups

- Can't use French keyboard in IP screen

>ellaborate this please, with screens etc, also steps for us to reproduce

- Most of HP tools are not copy during setup (no array tools, no homepage...) as no cd provided we need to download the old SPP which is 5Gb size .

> I will get on this one

[Wesley Elsen]

Not using intelligent provisioning but another unattended sollution gives same issue. 

OS tries to install on a disk with size 0 and fails :s. 

[ODuste]

‎"" 06-19-2015 10:23 PM

Re: Partition size error 0 MB on DL 360 Gen 9
You need to go back the the raid configuration

& scroll down & select the boot drive

it will then work""

Thank you so much for the solution. This one worked like a charm :)

Appreciate your correct and specific solution.

[Anonymous]

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04947312&sp4ts.oid=5177941

Advisory has been released a while back

[Torsten.]

The advisory says:

This issue may be observed on any HP ProLiant Gen8 or ProLiant Gen9 servers with multiple Smart Array controllers enabled, such as the embedded HP Dynamic Smart Array (Software RAID) controller without hard disk drives configured and HP Smart Array P44ar or other (Hardware RAID) Controller configured with SAS hard disk drives in a RAID Array logical boot drive.

Usually, if you have all disks connected to an additional controller and no disks on the built-in, disable the built-in should solve the issue too, right?

[Anonymous]

Correct, thats the workaround, upgrading the Intelligent Provisioning is the solution.

[NickSousa]

I fixed this issue by going into the array manager and selecting "clear configuration", and reconfiguring the raid array. I also set the logical volume as the boot device, and then reran the f10 intelligent provisioning.

[AlanDraco]

Press F9

Select ->

Systems Options  -> Controller SATA -> Change  Smart Array  to  SATA 

too Change the bios to legacy mode

and ready.

[Troozaz]

I physically removed additional drives, and set the primary and secondary boot drives to NONE in array config.

Worked perfectly after that.

[Michael Ridenour]

April 2018 and the issue still exists, at least it does on a DL20 Gen 9 manufactured in Sept 2017. The solution offered by LogicalStep to go back the the raid configuration and select the array to be the boot drive is what worked for me.  With this being a known issue for three years one would think that it should be fixed by now.

[UnhappyDoug]

seriously! cannot believe this cr*p ins't sorted! Just installing a DL360Gen10 and there is no where to adjust to partition size?! AND no software installed when using IP!! Borked up the IP when I tried to flash it using the built in f/w update! What a waste of space this rubbish is! Wasting my whole Friday evening. Ended up following suggestion above of creating smaller logical drive in SSA, then expanding from within windows later. thinking of moving to Dell