Ubuntu
calamares package

command systemd-machine-id-setup finished with exist code 127 : lubuntu calamares install with existing partition:

Bug #1923128 reported by Chris Guiver
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Lubuntu hirsute daily QA-test install on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
Testcase: install with existing partition (ie. replace sda1 which was 18.04 with 21.04)

Calamares reported at "Finish" step of QA-test install

---
"Installation Failed"
External command finished with errors.
Command systemd-machine-id-setup finished with exit code 127.
Output:
systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory
---

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: calamares 3.2.37-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.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-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: LXQt
Date: Fri Apr 9 14:37:02 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:21.04.2
 calamares-settings-lubuntu 1:21.04.2
 xfsprogs 5.10.0-2ubuntu3
 btrfs-progs 5.10.1-1build1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Chris Guiver (guiverc) wrote :
description: updated
Revision history for this message
Chris Guiver (guiverc) wrote :

Rebooted & system failed to boot..

Reboot the daily & repeated the install, this time using `sudo -E calamares -d`

same error, but session.log maybe more useful

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/1923128

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

this won't impact new users, but it will existing GNU/Linux users, as these are options beloved by distro hoppers, or people who broke their system & want to reinstall to fix the issue (without having to recover all data from backups, esp. if they don't have any). data in this case is NOT lost, but the 'quick re-install to fix' failed to work :(

it's also a quick way of UPGRADE via RE-INSTALL; where partitions are KEPT and not formatted.. allowing files to remain & ideally packages that were installed to be re-installed again..

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

Update (the following day)

This install (existing partition) was attempted & failed TWICE on the same sda1 partition using Lubuntu daily.

It was then used to attempt to install UBUNTU hirsute (daily; ubiquity) which failed with a different grub-install related issue (no efi partition from memory).

Post these; I RE-ATTEMPTED THE INSTALL (same exact parameters in calamares) and this time the INSTALL WAS FLAWLESS !!

refer http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/229234/testcases/1701/results

(Packages weren't exactly as I expected (ie. matching original lubuntu bionic install); but I'm blaming that on the multiple attempts & esp. ubuntu attempted install and I'd verified what was installed during that stage as it didn't boot... Anyway as a end-user I'd be fully happy with this last install result)

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in calamares (Ubuntu):
status: New → Confirmed
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Please let us know if this is still an issue, or an old bug.

Changed in calamares (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in calamares (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.