lubuntu focal install; existing partition (upgrade via re-install; 18.04 -> 20.04)

Bug #1927928 reported by Chris Guiver
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

static CalamaresUtils::ProcessResult CalamaresUtils::System::runCommand(CalamaresUtils::System::RunLocation, const QStringList&, const QString&, const QString&, std::chrono::seconds)
     Target output:
systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-245.so: cannot open shared object file: No such file or directory
---

Lubuntu focal daily QA-test install on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

System had a Lubuntu 18.04 install on it
- sda6 for /
- sda7 for /home
- sda8 for /susehome (actually Lubuntu hirsute; used to access only other files on dual boot system)

No partitions were formatted, all selected and re-used

(note: this box has had issues before.. but these are partitions not used before for a lubuntu calamares install.. [it was bionic])

---
     - message: "External command finished with errors."
2021-05-10 - 18:20:06 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
     - details: "Command <i>systemd-machine-id-setup</i> finished with exit code 127.\nOutput:\nsystemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-245.so: cannot open shared object file: No such file or directory"
---
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: calamares 3.2.20-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-52.59~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-52-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.partition.conf:
 efiSystemPartition: "/boot/efi"
 enableLuksAutomatedPartitioning: true
 userSwapChoices: none
 drawNestedPartitions: true
 defaultFileSystemType: "ext4"
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper @@ROOT@@
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: LXQt
Date: Mon May 10 18:29:31 2021
LiveMediaBuild: Lubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210509)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:20.04.2
 calamares-settings-lubuntu 1:20.04.2
 xfsprogs 5.3.0-1ubuntu2
 btrfs-progs 5.4.1-2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
description: updated
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/1927928

tags: added: iso-testing
Chris Guiver (guiverc)
description: updated
Revision history for this message
Chris Guiver (guiverc) wrote :

Box failed to boot; just gave errors (mostly read-only file-system)

I rebooted; and re-attempted the install. Same box
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
- sda6 for /
- sda7 for /home
(skipped the other partition; it can be added later)

result was same error

Revision history for this message
Chris Guiver (guiverc) wrote :

FYI: I booted live system again and `fsck` partitions; no issues were detected (both times)

Likely obvious (installer didn't get far enough), but I think the failure to boot (same error) is a red herring.. as grub still said 18.04.5 & kernel 5.4 not ....

Chris Guiver (guiverc)
description: updated
description: updated
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Focal is EOL etc etc :)

Changed in calamares (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.