attempting to install 20.04 LTS on older PC

Bug #1900361 reported by Hugo Becerra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Was merely going through the steps as usual to do a clean install of Ubuntu 20.04 on an older PC when I encountered this error at the select boot loader install stage and I tried doing another full erase/format then reinstall but this time it generated the option to send this trouble report. Seems to be an issue at the moment of formatting the selected drive. It is currently plugged in via internal SATA connections, it's a 280 GB SATA laptop drive. I'm thinking it may have possible bad sectors perhaps??

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 18 16:27:21 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Hugo Becerra (hugo-r-becerra) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more helpful in resolving your issue, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

FYI: I only quickly scanned, but didn't see any issues with bad sectors..

Paul White (paulw2u)
affects: ubuntu → ubiquity (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

Your partman log shows that your /dev/sda has two partitions. This is not the disk configuration expected for a 20.04 system by default. Did you choose manual partitioning from the installer?

Were you given an error message on your screen? That message doesn't appear to be included in the bug report, can you paste it?

Your logs also show a strange block device of /dev/mapper/ventoy, can you tell us what that is?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Hugo Becerra (hugo-r-becerra) wrote :

Thanks for looking into this bug guys. I'm not sure as to what was the actual problem. The partitions were established during the install. It said it would make 2 partitions in /dev/sda as /sda1=boot and /sda2=ext4 I believe. Since I couldn't fix the issue I did a clean install of Ubuntu 20.10 instead. Problem solved I supposed. Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.