Calamares fails in UEFI mode after external command in Lubuntu Cosmic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| calamares-settings-ubuntu (Ubuntu) |
Critical
|
Simon Quigley |
Bug Description
Error
Installation Failed
External command failed to finish.
Command [ -d /sys/firmware/efi ] && chroot /tmp/calamares-
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: calamares 3.2.1-1
ProcVersionSign
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu5
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: LXQt
Date: Tue Jul 10 12:56:59 2018
LiveMediaBuild: Lubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180710)
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
sudodus (nio-wiklund) wrote : | #1 |
sudodus (nio-wiklund) wrote : | #2 |
sudodus (nio-wiklund) wrote : | #3 |
Changed in calamares (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Simon Quigley (tsimonq2) |
Simon Quigley (tsimonq2) wrote : | #4 |
affects: | calamares (Ubuntu) → calamares-settings-ubuntu (Ubuntu) |
Launchpad Janitor (janitor) wrote : | #5 |
This bug was fixed in the package calamares-
---------------
calamares-
* Add translations support for the desktop file and the installer slideshow.
* Increase the timeout for the shellprocess commands (LP: #1781015).
* Remove the rm line of the shellprocess command (LP: #1780977).
-- Simon Quigley <email address hidden> Tue, 10 Jul 2018 19:17:43 -0500
Changed in calamares-settings-ubuntu (Ubuntu): | |
status: | In Progress → Fix Released |
sudodus (nio-wiklund) wrote : | #6 |
This bug is still alive with the daily iso file dated July 11 2018 :-(
When the installer was at 78%, it did not get any further, and the error window appeared (this time after 300 seconds).
sudodus (nio-wiklund) wrote : | #7 |
sudodus (nio-wiklund) wrote : | #8 |
@Simon,
But I want to add that in BIOS mode (alias CSM in this Toshiba laptop) it is possible to install Lubuntu Cosmic from the cosmic-
This is a great step forward :-)
So now we can focus on UEFI mode and in the next step secure boot.
Simon Quigley (tsimonq2) wrote : | #9 |
Hello Nio, thanks for the testing!
Could you please replace /etc/calamares/
The weird part is, I can't reproduce this.
Changed in calamares-settings-ubuntu (Ubuntu): | |
status: | Fix Released → New |
sudodus (nio-wiklund) wrote : | #10 |
@Simon,
Is it enough with this feedback? I started Calamares from the desktop icon and got the following output to an 'error window'.
---
External command failed to finish.
Command [ -d /sys/firmware/efi ] && chroot /tmp/calamares-
---
sudodus (nio-wiklund) wrote : | #11 |
I can add
- There is a working DVD drive in my Toshiba laptop. But it is empty (no disk inserted) during these tests.
- This is still tested with the daily iso file dated July 11 2018 (zsynced yesterday).
- I cloned the iso file to a USB pendrive. There is no problem to run it live in my Toshiba; it works in UEFI mode as well as in BIOS mode. (But Calamares works only in BIOS mode.)
Simon Quigley (tsimonq2) wrote : | #12 |
Ahh, that makes sense. The working DVD drive is a dead giveaway.
Playing with potential solutions now.
Thanks!
Simon Quigley (tsimonq2) wrote : | #13 |
Actually, since I can't actually reproduce this, one more thing.
Could you try this config file now?
sudodus (nio-wiklund) wrote : | #14 |
@Simon,
Before it stopped at 78%, but with this config file, it reached 82%, so '-m' made a difference.
---Boost.Python error in job "bootloader".
Command 'grub-install --target=x86_64-efi --efi-directory
grub-install: error: /usr/lib/
Traceback:
File "/usr/lib/
prepare_
File "/usr/lib/
install_
File "/usr/lib/
"--force"])
File "<string>", line 4, in <module>
---
Simon Quigley (tsimonq2) wrote : | #15 |
Hi Nio,
The attached *should* fix the problem. It would be great if you could try it.
Thanks.
sudodus (nio-wiklund) wrote : | #16 |
I'm sorry Simon,
But it fails too :-(
This bug is still alive with the daily iso file dated July 11 2018 :-(
When the installer was at 78%, it did not get any further, and the error window appeared.
---
External command failed to finish.
Command [ -d /sys/firmware/efi ] && chroot /tmp/calamares-
---
sudodus (nio-wiklund) wrote : | #17 |
Hi again Simon,
I zsynced to get the current daily iso file cosmic-
This time the system selected Stockholm (no longer New York), and I continued with this default setting (Swedish time and language) and selected 'Erase disk' as before. I also installed your new custom shellprocess.conf before starting Calamares.
It failed in the same way at 78% and with the same message as reported in comment #16 (for the iso file dated July 11 2018).
Simon Quigley (tsimonq2) wrote : | #18 |
20180714 should fix this.
Launchpad Janitor (janitor) wrote : | #19 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in calamares-settings-ubuntu (Ubuntu): | |
status: | New → Confirmed |
sudodus (nio-wiklund) wrote : | #20 |
Hi again Simon,
I zsynced to get the current daily iso file cosmic-
I used the system as it was cloned from the iso file and with default settings as much as possible, and with 'Erase disk'.
It reached 82% and failed with the following error message.
---
Error
Installation failed
Command 'grub-install --target=x86_64-efi --efi-directory
grub-install: error: /usr/lib/
Traceback:
File "/usr/lib/
prepare_
File "/usr/lib/
install_
File "/usr/lib/
"--force"])
File "<string>", line 4, in <module>
---
sudodus (nio-wiklund) wrote : | #21 |
I swapped off 'everything', in this case the zram, and tried again in the Toshiba laptop like in the previous comment. The error [message] was exactly the same, so we should *not* blame zram.
sudodus (nio-wiklund) wrote : | #22 |
I tested in the Intel NUC, described in the duplicate bug report
https:/
I swapped off an existing swap partition in the target drive (but not the zram), and tried like in the previous comments (# 20-21).
The error [message] was exactly the same, so we should *not* blame the DVD drive or some unique hardware component or unique UEFI-BIOS system.
@Simon,
Something goes wrong when trying to install the bootloader in UEFI mode and it does not find a file. Have you tried according to the 'built-in tip' to specify --target or --directory?
Simon Quigley (tsimonq2) wrote : | #23 |
How about 20180715.1?
The underlying problem is that the CD sources aren't being added correctly to pull in the package. That's why /usr/lib/
sudodus (nio-wiklund) wrote : | #24 |
Hi again Simon,
I zsynced to get the current daily iso file cosmic-
The test in my Toshiba failed:
---
Error
Installation Failed
External command failed to finish.
Command [ -d /sys/firmware/efi ] && chroot /tmp/calamares-
---
sudodus (nio-wiklund) wrote : | #25 |
... and it is back getting stuck at 78% where it is timing out.
sudodus (nio-wiklund) wrote : | #26 |
Installation fails the same way in the NUC.
Simon Quigley (tsimonq2) wrote : | #27 |
I'll get my hands on real hardware later this week to test it.
Thanks for your help Nio, and I'll let you know if I can't reproduce it on any of my hardware.
Simon Quigley (tsimonq2) wrote : | #28 |
After getting my hands on some real hardware, I was able to properly reproduce this, hunt down the problem, and get a fix.
Uploading nowish, and the fix should be included in 20180719. Later today I'll play with getting Secure Boot working.
Thanks for all your help Nio, it's very much appreciated. :)
Launchpad Janitor (janitor) wrote : | #29 |
This bug was fixed in the package calamares-
---------------
calamares-
* Fix non-secureboot UEFI installs on real hardware (LP: #1781015).
-- Simon Quigley <email address hidden> Wed, 18 Jul 2018 23:20:42 -0500
Changed in calamares-settings-ubuntu (Ubuntu): | |
status: | Confirmed → Fix Released |
sudodus (nio-wiklund) wrote : | #30 |
Congratulations and thanks Simon,
I tested in the NUC, and Calamares installed Lubuntu Cosmic in UEFI mode. You have squashed this bug :-)
(I will do some more tests, but I'm sure that you have solved the main problem.)
Simon Quigley (tsimonq2) wrote : | #31 |
Please, do more tests :)
sudodus (nio-wiklund) wrote : | #32 |
I tested in my Toshiba laptop from 2013 with Intel i5 (generation 3),
http://
I selected Swedish language and Stockholm time (and 'Erase disk' and of course in UEFI mode).
Calamares worked all the way, and the installed system works.
There was only a minor glitch: When rebooting after the installation, the system was stuck at the plymouth '5 dots' until I did 'SysRq REISUB'. This glitch is often said to be caused by a race condition and affects some computers with some versions of operating systems.
I tested in a Toshiba laptop from 2013 with Intel i5 (generation 3),
http:// www.toshiba. se/laptops/ satellite- pro/c850/ satellite- pro-c850- 19w/
and using the default location (New York and US English)
- in UEFI mode (not secure boot)
- 'Erase disk' (to check with an MSDOS partition table, if Calamares can create an EFI system partition etc). It 'says' that it will create a GPT, an ESP and a root partition ...
Indeed it did that:
---
lubuntu@lubuntu:~$ sudo parted /dev/sda p
Model: ATA KINGSTON SUV400S (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2098kB 317MB 315MB fat32 boot, esp
2 317MB 120GB 120GB ext4
lubuntu@lubuntu:~$
---
But when the installer was at 78%, it did not get any further, and the error window appeared.