Lubuntu 22.04 fails to install onto a >2TB disk on legacy BIOS systems

Bug #2054601 reported by Aaron Rainbolt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
New
Medium
Unassigned

Bug Description

Hardware: Dell Optiplex 9020, i5-4570, 32GB, Intel HD Graphics, Intel Corporation Ethernet Connection I217-LM, 6TB HDD
Operating system: Lubuntu 22.04.4 Release Candidate

Steps to reproduce:

1: Get a legacy BIOS system with a disk larger than 2TiB. (I have a 6TB spinning HDD.)
2: Boot the Lubuntu ISO in legacy BIOS mode.
3: Attempt to do an "Erase disk" installation.

Expected result: The installation should succeed.

Actual result: The installation crashes while trying to create partitions.

Additional information: Calamares is making an MBR partition table. This is the default behavior for BIOS systems. MBR partition tables only support 2TiB and smaller disks. When Calamares tries to create an over-2TiB partition during installation (in my case an over 5.4 TiB partition), it fails most likely because MBR can't handle that.

Note: This is not a regression. Older versions of Lubuntu 22.04 also defaulted to MBR as the partition table type for BIOS systems.

Tags: iso-testing
description: updated
description: updated
Changed in calamares (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Chris Guiver (guiverc) wrote :

Couldn't this be resolved via me mention in release notes.

To me an install on >2TB on MBR wouldn't be expected to succeed (I may not expect it to succeed either; but failure>success in my expectation)

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2054601

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.