Installation error with Ununty Server 18.04 LTS - curthooks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
efibootmgr (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I get the following error when I try to install Ubuntu Server 18.04 LTS:
Running command ['unmount', '/target/dev'] with allowed return codes [0] (capture=False)
finish: cmd-install/
Traceback (most recent call last):
File "/snap/
File "/snap/
File "/snap/
File "/snap/
File "/snap/
File "/snap/
File "/snap/
File "/snap/
File "/snap/
curtin.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'efibootmgr', '-v']
Exit code: 18
Reason: -
Stdout: ** Warning ** : please recreate these using efibootmgr to remove this warning.
Timeout: 1 seconds
BootOrder: 000A,000B,0008
Boot0008* TOSHIBA MQ01ABD100?
Stderr: ** Warning ** : Boot000b is not UEFI Spec compliant (lowercase hex in name)
** Warning ** : Bootffff is not UEFI Spec compliant (lowercase hex in name)
Could not parse device path: No such file or directory
Unexpected error while running commaned.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'efibootmgr', '-v']
Exit code: 18
Reason: -
Stdout: ** Warning ** : please recreate these using efibootmgr to remove this warning.
Timeout: 1 seconds
BootOrder: 000A,000B,0008
Boot0008* TOSHIBA MQ01ABD100?
Stderr: ** Warning ** : Boot000b is not UEFI Spec compliant (lowercase hex in name)
** Warning ** : Bootffff is not UEFI Spec compliant (lowercase hex in name)
Could not parse device path: No such file or directory
This is a clean installation.
affects: | shim-signed (Ubuntu) → efibootmgr (Ubuntu) |
Thanks for reporting the error.
Curtin is attempting to extract BootOrder and BootCurrent. A non-zero return code from running efibootmgr -v is unexpected.
It's not clear to me if this is a fatal error; it doesn't appear that way to me. If it isn't then ideally we'll need to determine the set of error codes that efibootmgr returns that aren't fatal to obtaining BootOrder and BootCurrent.
It may be the case that accepting non-zero exits from the --verbose command could hint that
attempting to change BootOrder may fail.