Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 931
    • Issues 931
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #14755

Closed
Open
Created Oct 02, 2017 by anonym@anonymMaintainer

Tails Installer treats drives differently depending on when they are plugged

Originally created by @anonym on #14755 (Redmine)

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).

Feature Branch: tails:bugfix/14755-installer-consistent-drive-plugging-state

Attachments

  • output.txt

Parent Task: #9005 (closed)

Edited May 21, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking