Project

General

Profile

Bug #14755

Feature #9005: Improve Tails Installer UX: phase 1

Tails Installer treats drives differently depending on when they are plugged

Added by anonym 15 days ago. Updated 15 days ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Start date:
10/02/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Easy:
Affected tool:
Installer

Description

E.g. it matters if the drive is plugged before or after Tails installer is started.

It was reported on Reddit that if the drive was plugged before starting Tails Installer, installation failed with:

Partitioning device /dev/sdc1

GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error creating file system: Command-line `parted --script "/dev/sdc1" mktable gpt' exited with a non-zero exit status 1: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Tails installation failed!

udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error creating file system: Command-line `parted --script "/dev/sdc1" mktable gpt' exited with a non-zero exit status 1: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

(0)

It was resolved when they "[started] Utilities -> Disks, reformatted the drive, unplugged it, started the Tails installer, then plugged it back in".

This is a regression introduced in Tails Installer 4.4.19 and Tails 3.2~rc1. It certainly sounds like an inconsistency on how the installer is initialized vs how it reacts to changes (of plugging/unplugging drives).

History

#1 Updated by anonym 15 days ago

  • Priority changed from Normal to Elevated
  • Parent task set to #9005

Reparenting to #9005 since it must be a regression introduced in that work. Also raising priority vs the other children of #9005, since this is an actual regression affecting users out there.

Also available in: Atom PDF