Ubuntu
ubiquity package

Ubuntu MATE 20.04.3 installer crashed

Bug #1942955 reported by Robert Pearson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Opinion
Undecided
I-Cat

Bug Description

Where to start. Apparently the .iso (ubuntu-mate-20.04.3-desktop-amd64.iso) assumes every computer runs Windows and has small disks (2 TB or smaller). The "Disk Image Writer" formats the jump drive as MBR with a bootable partition, a EFI partition for Windows compatibility and the rest of the drive (59GB) as unusable.

I purchased a 1TB WD Blue SATA SSD and tried to install in it. The first five times failed. The drive was initially blank and the installer disabled the Install button. I used 18.04 to create the GUID partition table and create the UEFI System Partition, the Ubuntu MATE partition, the Linux swap partition, and a NTFS data partition.

I was at least able to start the installation. Then the installer crashed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
Date: Tue Sep 7 21:28:16 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Robert Pearson (rpearsonii) wrote :
Revision history for this message
Robert Pearson (rpearsonii) wrote :

Also tried Ubuntu MATE 21.04 four times. Failed each time. Continuing to use 18.04.

I-Cat (i-cat)
description: updated
Changed in ubiquity (Ubuntu):
assignee: nobody → I-Cat (i-cat)
Revision history for this message
I-Cat (i-cat) wrote :

There is 5 People in charge of Ubuntu mate

https://github.com/orgs/ubuntu-mate/people

It took me a few hours to read this log.
I Do suspect a driver issue.
I Would like to know What Your System is as it is saying Two Different things.
I also Know that the Partition setup is Wrong.

---------------
/dev/sda1
partType W95Fat32
Should be Marked as Bootable
------------------------

Fill dis =>

OS:
Desktop: ?
Laptop: ?
ripi: ?
Other:
Brand: ?

tnx

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Robert Pearson (rpearsonii) wrote : Re: [Bug 1942955] Re: Ubuntu MATE 20.04.3 installer crashed
Download full text (4.2 KiB)

After it crashed, I shut down the system and then restarted. Enough had
been installed to boot and then I updated and reinstalled my apps. The
reason the first partition is W95Fat32 is that the drive was originally
blank (no partition table). The installer could not handle a blank drive. I
know that the UEFI System Partition has to be a FAT file system, but
neither gparted now Disks has a "Bootable" partition type.

 I do know that Disk Image Writer created Windows type media for small
drives (MBR not GUID PT, EFI Compatibility Partition for the code that
won't fit in the MBR). I believe that is because whoever created the iso
does not believe in UEFI.

When I boot, the ASUS A88MX-A firmware offers me a choice of UEFI or no
UEFI. The UEFI choice does not work. The no UEFI choice does.

I did have trouble with the Software Boutique. PlayOnLinux could not
install because the version in the Boutique relies on Python 2 which has
been discontinued instead of Python 3. VirtualBox could not install because
the version in Ubuntu requires that Ubuntu MUST be installed with a CD and
demands that the CD be inserted in /cdrom. I installed it from the Oracle
site.

I do thank you for responding. During the last 3 years, I have only gotten
4 responses. 1 really tried to help! I am still working on the issue.

I would like to help improve the Ubuntu and Ubuntu MATE installer. I am a
Unix System V expert, not Ubuntu. But at least I can help move from BIOS
booting (pre 1998) to UEFI booting. And the limited "Something else" can be
updated using gparted and Disks - and bootable partition type can be added
with the correct GUID.

Again. Thank you for responding.

Robert Pearson

On Wed, Sep 8, 2021 at 12:45 AM I-Cat <email address hidden> wrote:

> There is 5 People in charge of Ubuntu mate
>
> https://github.com/orgs/ubuntu-mate/people
>
> It took me a few hours to read this log.
> I Do suspect a driver issue.
> I Would like to know What Your System is as it is saying Two Different
> things.
> I also Know that the Partition setup is Wrong.
>
> ---------------
> /dev/sda1
> partType W95Fat32
> Should be Marked as Bootable
> ------------------------
>
> Fill dis =>
>
> OS:
> Desktop: ?
> Laptop: ?
> ripi: ?
> Other:
> Brand: ?
>
> tnx
>
> ** Changed in: ubiquity (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942955
>
> Title:
> Ubuntu MATE 20.04.3 installer crashed
>
> Status in ubiquity package in Ubuntu:
> Incomplete
>
> Bug description:
> Where to start. Apparently the .iso (ubuntu-mate-20.04.3-desktop-
> amd64.iso) assumes every computer runs Windows and has small disks (2
> TB or smaller). The "Disk Image Writer" formats the jump drive as MBR
> with a bootable partition, a EFI partition for Windows compatibility
> and the rest of the drive (59GB) as unusable.
>
> I purchased a 1TB WD Blue SATA SSD and tried to install in it. The
> first five times failed. The drive was initially blank and the
> installer disabled the Install button. I used 18.04 to create the GUID
> partition table and create the UEFI System...

Read more...

Revision history for this message
I-Cat (i-cat) wrote :

Yes I am Awsome... lol. j.k
UEFI booting looks like this its kinda :D =>

----
File Name = autorun.inf
txt in file =
[Autorun]
icon = autorun.ico
label = Ubuntu
----

You Could Use a bootable Usb Device To Format/Partition The Disk.

To install Python 2 version on Ubuntu open a terminal and enter one of the following commands: $ sudo apt install python2 OR $ sudo apt install python-minimal.

http://mirrors.cat.pdx.edu/ubuntu/pool/universe/p/python-defaults/python2-dev_2.7.17-2ubuntu4_amd64.deb

https://packages.ubuntu.com/focal/ppc64el/python2-dev/download

I Have a Bootable USB .zip over on archive.org

Changed in ubiquity (Ubuntu):
status: Incomplete → Opinion
Revision history for this message
Robert Pearson (rpearsonii) wrote :

I-Cat Now why would I want to install Python 2? Python is a dialect of C.
It split into Python 2 for those determined to program in C and Python 3
for those who want to "play/pretend" they are doing Object-Oriented
programming or Functional programming. As the C-ites aged out, Python 2
died. Why resurrect it?

On Wed, Sep 8, 2021 at 11:15 AM I-Cat <email address hidden> wrote:

> Yes I am Awsome... lol. j.k
> UEFI booting looks like this its kinda :D =>
>
> ----
> File Name = autorun.inf
> txt in file =
> [Autorun]
> icon = autorun.ico
> label = Ubuntu
> ----
>
> You Could Use a bootable Usb Device To Format/Partition The Disk.
>
> To install Python 2 version on Ubuntu open a terminal and enter one of
> the following commands: $ sudo apt install python2 OR $ sudo apt install
> python-minimal.
>
> http://mirrors.cat.pdx.edu/ubuntu/pool/universe/p/python-
> defaults/python2-dev_2.7.17-2ubuntu4_amd64.deb
>
> https://packages.ubuntu.com/focal/ppc64el/python2-dev/download
>
> I Have a Bootable USB .zip over on archive.org
>
> ** Changed in: ubiquity (Ubuntu)
> Status: Incomplete => Opinion
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942955
>
> Title:
> Ubuntu MATE 20.04.3 installer crashed
>
> Status in ubiquity package in Ubuntu:
> Opinion
>
> Bug description:
> Where to start. Apparently the .iso (ubuntu-mate-20.04.3-desktop-
> amd64.iso) assumes every computer runs Windows and has small disks (2
> TB or smaller). The "Disk Image Writer" formats the jump drive as MBR
> with a bootable partition, a EFI partition for Windows compatibility
> and the rest of the drive (59GB) as unusable.
>
> I purchased a 1TB WD Blue SATA SSD and tried to install in it. The
> first five times failed. The drive was initially blank and the
> installer disabled the Install button. I used 18.04 to create the GUID
> partition table and create the UEFI System Partition, the Ubuntu MATE
> partition, the Linux swap partition, and a NTFS data partition.
>
> I was at least able to start the installation. Then the installer
> crashed.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: ubiquity 20.04.15.17 [modified:
> lib/partman/automatically_partition/question]
> ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
> Uname: Linux 5.11.0-27-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> CasperMD5CheckResult: pass
> CasperVersion: 1.445.1
> Date: Tue Sep 7 21:28:16 2021
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
> LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64
> (20210819.1)
> SourcePackage: ubiquity
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1942955/+subscriptions
>
>

Revision history for this message
Robert Pearson (rpearsonii) wrote :

I-Cat

I already have a "bootable USB drive". That is what I used to try and install Ubuntu MATE 20.04.3. That will not change the fact that the partition editor in gparted, Disks, and the installer do not have a UEFI bootable partition type in their options. The only option is BIOS bootable (yeah! lets all go back to the way it was done in 1998). I do not even know the GUID for the UEFI bootable partition type.

For your questions about my system.
Currently Ubuntu MATE 18.04. I tried later versions but each one broke code that works in 18.04.
ASUS A88XM-A with 32 GB 1866 MHz DDR2 (4 Crucial DIMMs)
AMD A8-7600 Radeon R7 running at 3.1 GHz
4TB Seagate Iron Wolf SATA HDD (this has Ubuntu MATE 18.04 installed for UEFI booting)
(new) 1TB WD Blue SATA SSD (this is where I am attempting to install Ubuntu MATE 20.04.3 with UEFI booting)
I copied the contents of the UEFI System Partition from the 4TB HHD to the UEFI System Partition on the 1TB SSD.
I use HDMI to connect my computer to my Samsung SyncMate TA350 TV/Monitor.

During installation, I noticed many missing firmware errors. I believe that they were not included because the iso file is for BIOS booting only. I need an iso intended for UEFI or BIOS booting. Any drive > 2TB ( 4TB drives are now about $75) requires GUID Partition Table and UEFI booting.

New symptoms. No sound. I go to Control Center -> Sound -> Hardware and select "Built-in Audio 1 Output / 1 Input Digital Stereo (HDMI) Output. Test the speakers. Left and right pass. Profile: Digital Stereo (HDMI) Output. I click close. No sound. I reopen Sound -> Hardware and Ubuntu has reset it to (IEC958) output. Tried multiple times. Still no sount. Ran my Blu ray player through the monitor. Sound. 20.04.3 no sound. Rebooted to 18.04, Sound.

How do I fix a broken installation when the iso and Installer are so bad?

I would like to help improve the iso and Installer so they are up to 2021, not 1998. Who can I contact?

Robert Pearson

P.S. What is ripi?

Revision history for this message
Robert Pearson (rpearsonii) wrote :

The UEFI System Partition UUID: FD2AEA73-FC80-4871-A55A-B61F0ABA40A3
Flags: boot

I found this Example of an EFI system partition as shown by KDE Partition Manager (NOT gparted, DISKS, or the Ubuntu installer).

Robert Pearson

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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