mounting internal LUKS partition fails: unhandled device #220
Comments
|
Hi, thanks for the info. I'm very sorry to respond so late, I seem to have missed this issue. Unfortunately, I probably won't have time to look further into this in the next month or so either.
Anyway, I want to change the CLI so that user command line is considered more important than rules... udiskie-mount shouldn't refuse from trying to mount/unmount a particular device if it was passed explicitly on the command line. |
|
I think I had this issue with my NVMe. I can provide the related output.
|
|
I also have a sdcard in my machine and was able to unlock I did come another problem though, which I don't think is udiskie's fault, but maybe you can give me some pointers as to what to try next. I was able to reproduce this with a LUKS encrypted USB stick too, with a single partition. I'm wondering if it's related to #200 Alpine Linux machine I was having issues getting udiskie to mount an encrypted volume.
What is interesting is "PreferredDevice" doesn't say:
Obviously I know it can mount this filesystem, it's ext4 and
|
|
Hey @dngray,
thanks for your input, but please don't hijack existing issues for new problems. I'm not going to read through this, because the OPs problem is already identified: udiskie always applies the ignore-filters, even for devices given on the command line. It should be changed not to ignore devices if they were explicitly passed on the command lines. This should be relatively easy to fix (PRs welcome), but I currently don't have time to do it. For now, a workaround is to add a |
That wasn't the intention. I was trying to reproduce original issue with an internal
I do think that's a good idea. It happened that the machine I had an sdcard reader on, ran Alpine Linux and had Anyway I tested with Fedora 35 (v2.4.0) and Debian (v1.7.7) with my sdcard reader (
Can confirm this did fix the problem for device_config:
- device_file: /dev/nvme*
ignore: false
options: [rw] |
Hi,
I have an internal disk with an encrypted partition, /dev/mmcblk1p3. In the past, I could unlock/mount this disk with udiskie:
Debugging into the issue, I found that the
match_config()function in config.py first checks the is_toplevel rule for/dev/mmcblk1p3, then checks its parent device,/dev/mmcblk1, which of course is a toplevel device, making the rule fail.I believe this is a bug, since by iterating up to the toplevel (via
device = device.partition_slave) in thewhileloop inmatch_config, every device is eventually marked as a toplevel device.The text was updated successfully, but these errors were encountered: