@juliank, the install was done on a nearby test box (near my primary system) simulating a usual install which really will be a MBR/legacy partition table
the GPT was automatically created when I selected new (I'd have chosen MBR if given a choice); the systems where this matters are all MBR and have all four primary partitions already utilized
If a message had shown, I'd likely have realized it was GPT & gone back and created MBR (or pre-prepared as I'd done in most prior QA-test installs in hirsute/this cycle using gparted) as that is my actual intended install case (ie. upgrade an existing/prior Ubuntu install from long ago).
The simple 'install' strategy was used ONLY to make it easier to re-produce the problem.
Reports made duplicate of this include my actual install boxes with systems I do care about (d755-5, d780 etc). All are multi-boot with all primary partitions already utilized.
@juliank, the install was done on a nearby test box (near my primary system) simulating a usual install which really will be a MBR/legacy partition table
the GPT was automatically created when I selected new (I'd have chosen MBR if given a choice); the systems where this matters are all MBR and have all four primary partitions already utilized
No warning messages were shown I'm sure !. http:// iso.qa. ubuntu. com/qatracker/ milestones/ 419/builds/ 229694/ testcases/ 1302/results is the QA-test report.
If a message had shown, I'd likely have realized it was GPT & gone back and created MBR (or pre-prepared as I'd done in most prior QA-test installs in hirsute/this cycle using gparted) as that is my actual intended install case (ie. upgrade an existing/prior Ubuntu install from long ago).
The simple 'install' strategy was used ONLY to make it easier to re-produce the problem.
Reports made duplicate of this include my actual install boxes with systems I do care about (d755-5, d780 etc). All are multi-boot with all primary partitions already utilized.