[Bullseye] errors with encrypted partitions #266
Comments
|
big progress with using RasPi OS Bullseye! when plug in a BitlLocker encrypted partition now you get a Passphrase dialog instead of the Error above but without installing the additional package and there are also errors, when you choose remembering the passphrase: and en error ewhen you try to eject the mounted drive again:
|
beta-tester
changed the title
|
@spl237 Is this something that should be supported? |
|
It's not something we've ever tested or changed; any implementation is coming straight from upstream. So as far as I am concerned, we don't support it - if it doesn't work, blame Debian... ;) |
|
OP is saying it works in Debian running LXDE. |
|
In that case, pass - no idea why it would be working differently on us, as I have no idea where all the bitlocker stuff happens. I would guess that the dialogs above come from libfm, but none of the changes I have made should be affecting that. |
|
according the keyring error message PS.: not tested, but i think this is not BitLocker specific. other Linux specific filesystem encryption may have the same issue, at least that with the keyring and the one where the package |
|
Sounds like we should probably include those two packages in the desktop image then. libblockdev-crypto2 is a
@spl237 thoughts? |
|
i played a bit with the encrypted device and logged syslog and mount output... (maybe the File Manager was silently dropping the error or the eject option in the taskbar is mis-interpreting some return code) |
|
i also took a look to the output of |
|
i checked again some logs... |
|
I don't have appropriate devices to test with, but once the next image is release it would be interesting to hear whether it improves the situation. It should include a few of the packages you mentioned and some others, which may help, but there's no ETA yet. |
|
i will try it out as soon as i see the new released image and give you feedback. |
OFFTOPICthe packages |
|
Yup, good call. |
|
hi, i just tried the new release image "2022-01-28-raspios-bullseye-armhf.zip"
nice - thank you very much! 😄 what still is odd:
|
|
Great, thanks for testing! And you can still eject from pcmanfm without any issues? |
|
yes... at least it gives no error like the eject of the taskbar does. when device plugged, unlocked with password and mounted it shows like this in pcmanfm: when i click to the eject icon in pcmanfm, pcmanfm closes. so pcmanfm does not eject that device, it only unmount it. then i again test the behavior with Debian LXDE on a PC. it behaves the same. but Debian LXDE does not have an eject button on the taskbar so i could not see how it behaves with that. i did some tests on the RPi on the console and it seems the /dev/sda is in use by some other process, but i can't figure out which process it is. when the encrypter device is plugged, unlocked by password and mounted: pi@test:~ $ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,8T 0 disk
└─sda1 8:1 0 1,8T 0 part
└─bitlk-2049 254:0 0 1,8T 0 crypt /media/pi/USB-SSD#1
mmcblk0 179:0 0 29,7G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 29,5G 0 part /
pi@test:~ $ mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=340904k,nr_inodes=85226,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=188996k,nr_inodes=819200,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94496k,nr_inodes=23624,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/mapper/bitlk-2049 on /media/pi/USB-SSD#1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)after i clicked the eject button in pcmanfm: pi@test:~ $ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,8T 0 disk
└─sda1 8:1 0 1,8T 0 part
mmcblk0 179:0 0 29,7G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 29,5G 0 part /
pi@test:~ $ mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=340904k,nr_inodes=85226,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=188996k,nr_inodes=819200,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94496k,nr_inodes=23624,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)when i try to eject the device from commandline: pi@test:~ $ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,8T 0 disk
└─sda1 8:1 0 1,8T 0 part
└─bitlk-2049 254:0 0 1,8T 0 crypt /media/pi/USB-SSD#1
mmcblk0 179:0 0 29,7G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 29,5G 0 part /
pi@test:~ $ sudo eject /dev/sda
eject: cannot open /dev/sda: Das Gerät oder die Ressource ist belegt
pi@test:~ $ sudo eject /dev/sda1
eject: cannot open /dev/sda: Das Gerät oder die Ressource ist belegt
pi@test:~ $ sudo eject /dev/mapper/bitlk-2049
eject: /dev/mapper/bitlk-2049: is not hot-pluggable device
pi@test:~ $ sudo eject /media/pi/USB-SSD#1/
eject: /dev/mapper/bitlk-2049: is not hot-pluggable device
pi@test:~ $ sudo umount /media/pi/USB-SSD#1
pi@test:~ $ sudo eject /dev/mapper/bitlk-2049
eject: /dev/mapper/bitlk-2049: is not hot-pluggable device
pi@test:~ $ sudo eject /dev/sda1
eject: cannot open /dev/sda: Das Gerät oder die Ressource ist belegt
pi@test:~ $ sudo eject /dev/sda
eject: cannot open /dev/sda: Das Gerät oder die Ressource ist belegtis the Ejecter on the taskbar a custom application? if it is an app from Debian, can you tell me where to find it to test under Debian LXDE Live. |
|
I believe it's custom. @spl237 Looks like it runs |
|
Thanks again for investigating the issue and providing the fixes. The remaining issue with the ejecter can be reported here: https://github.com/raspberrypi-ui/lxplug-ejecter/issues |
RPi-Distro/repo#266 (comment) (cherry picked from commit cc8f695)
RPi-Distro/repo#266 (comment) (cherry picked from commit cc8f695)
hi, there is an issue when i plug an external USB-SSD drive with encrypted content to the "Raspberry Pi OS Buster".the partition is full encrypted by BitLocker.
when i plug the external USB-SSD to the Raspberry Pi, it pops up an error message:
No .Filesystem or .Encrypted interface on D-Bus objectalso when i try to open the shown encrypted drive in PcManFM by double click on it, the same error message pops up again.
ENV:
Raspberry Pi OS Buster (2021-05-07-raspios-buster-armhf.zip) + full-upgradeTo verify i tried:
-> no issues to access the external USB-SSD with full encrypted content BilLocker.
-> no issues to access the external USB-SSD with full encrypted content BilLocker.
because Debian distro and Ubuntu have not this issue, i guess it must be an issue specially related to Raspberry Pi OS.
The text was updated successfully, but these errors were encountered: