- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Partition size error 0 MB on DL 360 Gen 9
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2015 03:27 AM
08-18-2015 03:27 AM
Re: Partition size error 0 MB on DL 360 Gen 9
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2015 01:16 AM
08-26-2015 01:16 AM
Re: Partition size error 0 MB on DL 360 Gen 9
- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2015 03:58 AM
12-15-2015 03:58 AM
Re: Partition size error 0 MB on DL 360 Gen 9
Not using intelligent provisioning but another unattended sollution gives same issue.
OS tries to install on a disk with size 0 and fails :s.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2016 03:07 AM - edited 03-02-2016 03:10 AM
03-02-2016 03:07 AM - edited 03-02-2016 03:10 AM
Re: Partition size error 0 MB on DL 360 Gen 9
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2016 04:17 AM
03-02-2016 04:17 AM
Re: Partition size error 0 MB on DL 360 Gen 9
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04947312&sp4ts.oid=5177941
Advisory has been released a while back
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2016 04:31 AM
03-02-2016 04:31 AM
Re: Partition size error 0 MB on DL 360 Gen 9
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?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2016 04:40 AM
03-02-2016 04:40 AM
Re: Partition size error 0 MB on DL 360 Gen 9
Correct, thats the workaround, upgrading the Intelligent Provisioning is the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 07:00 AM
12-01-2016 07:00 AM
Re: Partition size error 0 MB on DL 360 Gen 9
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2017 06:13 PM
01-28-2017 06:13 PM
Re: Partition size error 0 MB on DL 360 Gen 9
Press F9
Select ->
Systems Options -> Controller SATA -> Change Smart Array to SATA
too Change the bios to legacy mode
and ready.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2017 04:18 AM
08-06-2017 04:18 AM
Re: Partition size error 0 MB on DL 360 Gen 9
I physically removed additional drives, and set the primary and secondary boot drives to NONE in array config.
Worked perfectly after that.