Cannot access encrypted volume

Bug #1762307 reported by Howard Moreland on 2018-04-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
Undecided
Unassigned

Bug Description

At the screen preparing to install Kubuntu, I selected the button "Guided - use entire disk and set up encrypted LVM". System has two hard drives, sda with both Mint 18.3 and Bionic 18.04; sdb with Bionic 18.04. The installer graphic showed it would use all of sda for Kubuntu.

In Dolphin, trying to access the encrypted volume on sda returns:
An error occurred while accessing '58.9 GiB Encrypted Drive', the system responded: The requested operation has failed: Error unlocking /dev/sda5: The function 'bd_crypto_luks_open_blob' called, but not implemented!

Howard Moreland (hrm-temp) wrote :
Howard Moreland (hrm-temp) wrote :
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/1762307

tags: added: iso-testing
Howard Moreland (hrm-temp) wrote :

The workaround given in Bug #1757321 did not fix this. It did get a new error:
An error occurred while accessing 'Home', the system responded: An unspecified error has occurred: No such interface 'org.freedesktop.UDisks2.Filesystem' on object at path /org/freedesktop/UDisks2/block_devices/dm_2d0

Howard Moreland (hrm-temp) wrote :

After the workaround, KDE Partition Manager sees the encrypted partition as lvm2 rather than luks, and says lvm2 needs to be installed. After installing lvm2, KDE Partition Manager sees the drives correctly. Dolphin still gives error:
An error occurred while accessing '58.9 GiB Encrypted Drive', the system responded: An unspecified error has occurred: No such interface 'org.freedesktop.UDisks2.Filesystem' on object at path /org/freedesktop/UDisks2/block_devices/dm_2d0

Howard Moreland (hrm-temp) wrote :

This seems to not be a duplicate of bug #1757321. The workarounds for it do not help here. This is 32-bit, bug #1757321 is 64-bit.

affects: ubiquity (Ubuntu) → udisks2 (Ubuntu)
Glyn Davies (cheliosnz) wrote :

I have the same error occurring when trying to decrypt a removable USB drive. Though the same machine is running on a LUKS+LVM encrypted system disk without having any issues at all.

The actual error is:
Unable to access "64 GB Encrypted"
Error unlocking /dev/sdb1: The function 'bd_crypto_luks_open_blob' called, but not implemented

I have also confirmed that the USB drive in question is able to be unencrypted and read successfully on my 16.04 machine.

Current setup info:

                         ./+o+- glyndavies@riss
                  yyyyy- -yyyyyy+ OS: Ubuntu 18.04 bionic
               ://+//////-yyyyyyo Kernel: x86_64 Linux 4.15.0-15-generic
           .++ .:/++++++/-.+sss/` Uptime: 12m
         .:++o: /++++++++/:--:/- Packages: 1941
        o:+o+:++.`..```.-/oo+++++/ Shell: bash 4.4.19
       .:+o:+o/. `+sssoo+/ Resolution: 3840x2520
  .++/+:+oo+o:` /sssooo. DE: Budgie
 /+++//+:`oo+o /::--:. WM: BudgieWM
 \+/+o+++`o++o ++////. WM Theme: Adapta
  .++.o+++oo+:` /dddhhh. GTK Theme: Adapta [GTK2/3]
       .+.o+oo:. `oddhhhh+ Icon Theme: Papirus-Adapta
        \+.++o+o``-````.:ohdhhhhh+ Font: Noto Sans UI 11
         `:o+++ `ohhhhhhhhyo++os: CPU: Intel Core i7-5600U @ 4x 3.2GHz [77.0°C]
           .o:`.syhhhhhhh/.oo++o` GPU: intel
               /osyyyyyyo++ooo+++/ RAM: 1978MiB / 7661MiB
                   ````` +oo+++o\:
                          `oo++.

Glyn Davies (cheliosnz) wrote :

Apologies, let's try that again.

Current setup info:
OS: Ubuntu 18.04 bionic
Kernel: x86_64 Linux 4.15.0-15-generic
Uptime: 12m
Packages: 1941
Shell: bash 4.4.19
Resolution: 3840x2520
DE: Budgie
WM: BudgieWM
WM Theme: Adapta
GTK Theme: Adapta [GTK2/3]
Icon Theme: Papirus-Adapta
Font: Noto Sans UI 11
CPU: Intel Core i7-5600U @ 4x 3.2GHz [77.0°C]
GPU: intel
RAM: 1978MiB / 7661MiB

summary: - Cannot access enctypted volume
+ Cannot access encrypted volume
tags: added: bionic
Phillip Susi (psusi) wrote :

Glyn, your issue is Bug #1757321.

Howard, I'm not quite understanding you. Are you booting from the encrypted hard drive, or trying to access it from another system? If you are just booting from the encrypted drive then it is unlocked at boot time.

Changed in udisks2 (Ubuntu):
status: New → Incomplete
Howard Moreland (hrm-temp) wrote :

I booted the system from the encrypted hard drive, and it seemed to unlock, but Dolphin could not access it.

This is for version 20180408, 32-bit. I have since replaced it. Would it help to install that version again for testing?

Changed in udisks2 (Ubuntu):
status: Incomplete → New
Phillip Susi (psusi) wrote :

If you wish to reproduce it then yes, but it probably isn't necessary if it is no longer an issue for you.

Changed in udisks2 (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

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

Changed in udisks2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments