Some bitlocker partition not opening after update to Manjaro 26.0.0

After upgrading to Manjaro 26.0.0 I find a bitlocker partition to be not working. It is basically a thumb drive with multiple bitlocker partitions, but strangely only one partition won’t open after the upgrade.

For verification, I checked the same thumb drive on a different Manjaro machine, which has not yet conducted the same update. The problematic partition opens there without any problems.

One additional observation:

If I open the partition via command line, I am not prompted for a passphrase. The command temrinates without error. If I open a working partition on the same thumb drive, I am asked for the passphrase as expected.

This is my system:

~ >>> inxi --admin --verbosity=8 --filter --no-host --width                                                                                                                                                       
System:
  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=4c2ea2f1-3cfa-4377-8778-97f19f2453fe rw quiet
    cryptdevice=UUID=ac37595d-5b67-408c-82b8-547a678e97e6:luks-ac37595d-5b67-408c-82b8-547a678e97e6
    root=/dev/mapper/luks-ac37595d-5b67-408c-82b8-547a678e97e6
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.21.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: MSI product: MS-7798 v: 1.0
    serial: <superuser required>
  Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends v: 1.9
    date: 09/30/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 24 GiB available: 23.4 GiB used: 3.51 GiB (15.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 4 modules: 4 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR3 detail: synchronous size: 4 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CML8GX3M2A1600C9 serial: N/A
  Device-2: ChannelA-DIMM1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Hynix/Hyundai part-no: HMT41GU6AFR8A-PB serial: <filter>
  Device-3: ChannelB-DIMM0 type: DDR3 detail: synchronous size: 4 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CML8GX3M2A1600C9 serial: N/A
  Device-4: ChannelB-DIMM1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Hynix/Hyundai part-no: HMT41GU6AFR8A-PB serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-3450S bits: 64 type: MCP arch: Ivy Bridge
    gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1643 min/max: 1600/3500 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 1643 2: 1643 3: 1643 4: 1643 bogomips: 22410
  Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov
    constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb
    ept erms est f16c flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb ibrs
    ida lahf_lm lm mca mce md_clear mmx monitor msr mtrr nonstop_tsc nopl nx
    pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pti pts
    rdrand rdtscp rep_good sep smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid xsave
    xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
    vendor: Micro-Star MSI driver: nvidia v: 590.48.01
    alternate: nouveau,nvidia_drm non-free: 550-580.xx+ status: current (as of
    2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3
    bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: Idek Iiyama PL2792Q serial: <filter> built: 2021
    res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2 chroma: red:
    x: 0.671 y: 0.333 green: x: 0.298 y: 0.627 blue: x: 0.141 y: 0.051 white:
    x: 0.322 y: 0.329 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: 2560x1440, 2048x1280, 1920x1200, 1920x1080, 1600x1200,
    1680x1050, 1600x900, 1280x1024, 1440x900, 1280x720, 1024x768, 800x600,
    720x576, 720x480, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 25.3.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    memory: 11.72 GiB display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 4 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3060 driver: nvidia v: 590.48.01
    device-ID: 10de:2504 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings, nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1e20 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228e
    class-ID: 0403
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: NetGear WNDA4100 802.11abgn 3x3:3 [Ralink RT3573]
    driver: rt2800usb type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-3:3 chip-ID: 0846:9012 class-ID: 0000 serial: <filter>
  IF: wlp0s20u3 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
    chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: bitlk_daniel_stick maj-min: 254:3 type: Crypto dm: dm-3
    size: 30 GiB
  Components:
  p-1: sdd2 maj-min: 8:50 size: 30 GiB
  Device-2: bitlk_bibliothek_stick maj-min: 254:4 type: Crypto dm: dm-4
    size: 30 GiB
  Components:
  p-1: sdd3 maj-min: 8:51 size: 30 GiB
  Device-3: bitlk_wiki_stick maj-min: 254:5 type: Crypto dm: dm-5
    size: 30 GiB
  Components:
  p-1: sdd4 maj-min: 8:52 size: 30 GiB
  Device-4: bitlk_work_stick maj-min: 254:6 type: Crypto dm: dm-6
    size: 30 GiB
  Components:
  p-1: sdd5 maj-min: 8:53 size: 30 GiB
  Device-5: luks-ac37595d-5b67-408c-82b8-547a678e97e6 maj-min: 254:0
    type: LUKS dm: dm-0 size: 232.59 GiB
  Components:
  p-1: sda2 maj-min: 8:2 size: 232.59 GiB
  Device-6: luks-8e70af97-5288-4227-b43f-15c7ae8b158e maj-min: 254:2
    type: LUKS dm: dm-2 size: 931.51 GiB
  Components:
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB
  Device-7: luks-97478fb5-267e-493d-8774-49eef2f55050 maj-min: 254:1
    type: LUKS dm: dm-1 size: 465.76 GiB
  Components:
  p-1: sdc1 maj-min: 8:33 size: 465.76 GiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.83 TiB used: 1.17 TiB (64.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: Flash Drive FIT
    size: 239.02 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
    fw-rev: 1100 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 232.59 GiB size: 227.88 GiB (97.98%)
    used: 119.9 GiB (52.6%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ac37595d-5b67-408c-82b8-547a678e97e6 label: System
    uuid: 4c2ea2f1-3cfa-4377-8778-97f19f2453fe
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 472 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: NO_LABEL
    uuid: 04E7-F02F
  ID-3: /mnt/org/bibliothek raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 8.54 GiB (28.5%) fs: fuseblk dev: /dev/dm-4 maj-min: 254:4
    mapped: bitlk_bibliothek_stick label: N/A uuid: N/A
  ID-4: /mnt/org/daniel raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 15.59 GiB (52.0%) fs: fuseblk dev: /dev/dm-3 maj-min: 254:3
    mapped: bitlk_daniel_stick label: N/A uuid: N/A
  ID-5: /mnt/org/wiki raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 6.14 GiB (20.5%) fs: fuseblk dev: /dev/dm-5 maj-min: 254:5
    mapped: bitlk_wiki_stick label: N/A uuid: N/A
  ID-6: /mnt/org/work raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 83.5 MiB (0.3%) fs: fuseblk dev: /dev/dm-6 maj-min: 254:6
    mapped: bitlk_work_stick label: N/A uuid: N/A
  ID-7: /run/media/schatzi/Data raw-size: 465.76 GiB
    size: 457.38 GiB (98.20%) used: 353.69 GiB (77.3%) fs: ext4 dev: /dev/dm-1
    maj-min: 254:1 mapped: luks-97478fb5-267e-493d-8774-49eef2f55050
    label: Data uuid: aea89950-6192-4055-8c45-0991f2477684
  ID-8: /run/media/schatzi/Extra raw-size: 931.51 GiB
    size: 915.81 GiB (98.31%) used: 699.14 GiB (76.3%) fs: ext4 dev: /dev/dm-2
    maj-min: 254:2 mapped: luks-8e70af97-5288-4227-b43f-15c7ae8b158e
    label: Extra uuid: a584c501-ec7f-44d1-8912-433590b0e4a3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/sdd1 maj-min: 8:49 size: 119.01 GiB fs: bitlocker
    label: 20IAV502790N-0 Mobi 20.06.2023
    uuid: 19a7082b-3c22-4c74-b120-5145a4be6aea
  ID-2: /dev/sdd2 maj-min: 8:50 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Daniel 22.06.2023
    uuid: 31203ad1-da38-4cc3-a989-36c1904f0ce1
  ID-3: /dev/sdd3 maj-min: 8:51 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Bibliothek 20.06.2023
    uuid: 2cf5acb6-cd16-469d-9969-fe23c47bfb15
  ID-4: /dev/sdd4 maj-min: 8:52 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Wiki 20.06.2023
    uuid: 02985be4-7822-4688-af77-2b2f231f9ec5
  ID-5: /dev/sdd5 maj-min: 8:53 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Iav 20.06.2023
    uuid: 40082e01-5629-41e6-9622-4efe2c06129c
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0a12:0001 class-ID: e001
  Device-2: 1-3:3 info: NetGear WNDA4100 802.11abgn 3x3:3 [Ralink RT3573]
    type: Network driver: rt2800usb interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 450mA
    chip-ID: 0846:9012 class-ID: 0000 serial: <filter>
  Hub-2: 1-4:4 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 214b:7250 class-ID: 0900
  Hub-3: 1-4.3:5 info: Monterey BakkerElkhuizen Wired Keyboard S-board 840
    Design USB-Hub ports: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0566:3020 class-ID: 0900
  Device-1: 1-4.3.2:6 info: Logitech Unifying Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-2: 1-4.3.3:7 info: Monterey BakkerElkhuizen Wired Keyboard S-board
    840 Design type: keyboard,HID driver: hid-generic,usbhid interfaces: 2
    rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 0566:3013 class-ID: 0300
  Hub-4: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
  Hub-6: 2-1.5:3 info: Realtek 4-Port USB 2.0 Hub ports: 2 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5412
    class-ID: 0900
  Device-1: 2-1.5.1:4 info: Silicon Motion - Taiwan (formerly Feiya ) Flash
    Drive type: mass storage driver: usb-storage interfaces: 1 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 300mA
    chip-ID: 090c:1000 class-ID: 0806 serial: <filter>
  Hub-7: 3-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-8: 4-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-9: 4-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 2009 libs: 462 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors2.manjaro.org/stable/$repo/$arch
    2: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    3: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 337
  1: cpu: 9.7% command: firefox pid: 4951 mem: 773.8 MiB (3.2%)
  2: cpu: 4.5% command: kwin_wayland pid: 937 mem: 338.9 MiB (1.4%)
  3: cpu: 3.6% command: firefox pid: 5232 mem: 317.6 MiB (1.3%)
  4: cpu: 2.9% command: zsh pid: 12999 mem: 8.40 MiB (0.0%)
  5: cpu: 2.3% command: firefox pid: 12726 mem: 296.3 MiB (1.2%)
  Memory top: 5 of 337
  1: mem: 773.8 MiB (3.2%) command: firefox pid: 4951 cpu: 9.7%
  2: mem: 628.0 MiB (2.6%) command: plasmashell pid: 1117 cpu: 0.8%
  3: mem: 361.6 MiB (1.5%) command: firefox pid: 11765 cpu: 1.7%
  4: mem: 338.9 MiB (1.4%) command: kwin_wayland pid: 937 cpu: 4.5%
  5: mem: 317.6 MiB (1.3%) command: firefox pid: 5232 cpu: 3.6%
Info:
  Processes: 337 Power: uptime: 28m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 9.33 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.3.9 running-in: konsole inxi: 3.3.40

Can someone help me, please?

I have a similar problem with the external drive in btrfs. If I mount it from the Plasma desktop applet, 30 seconds after clicking mount, Plasmashell displays an inaccessible drive error but after approximately 4 or 5 minutes checking the drive, it mounts without problems. If I mount the drive from Dolphin or using udiskctl or using the mount without checking option in the applet, it mounts without problems. It looks as if Plasmashell is running the btrfs --check command.

Do you mount bitlocker partition with the applet or Dolphin?

If you mount with the desktop applet try with dolphin.

Hey @ddns, thanks for the quick reply!

I open the encrypted partition and mount it by using a script, since Manjaro would not remember the passphrase for bitlocker in the past. But following your advice, I can mount the “lost” partition with the desktop applet. Still strange, though. I’d expect command line/ script to be the bulletproof method!?

When you encrypt a disk using BitLocker it offers two modes.

A new mode and a compatibility mode.

It is only a guess - this could make the difference - but the idea may be void as

Ok, so just to get it right: You would suggest comparing the different partitions on some Windows machine and considering re-encrypting the non-working partition?

What is puzzling me, is that all partitions worked for many years without any flaw and I could switch between Linux and Windows without any issues. In addition, I am wondering what the desktop applet is using, when I mount it with gui via “Drives and Devices”. Is this not cryptsetup?

That could be one interpretation, I guess, but I have next to experience with BitLocker and Windows encryption.

I did some quick skimming on a search result linux support for bitlocker - it seems there is a utility called dislocker - I presume that is what you to script the unlocking?

And the fact that an update apparently changed something which caused your otherwise functioning script to fail.

Then taking the same partition to another system and it unlock as expected.

I have a head full of knowledge - and something I don’t remember where came from - such as the two methods on applying bitlocker encryption, but due to my recent endeavours with encryption I remembered this

From the man page - I remember limited support - which makes me think it could be cryptsetup related

that is - if you are using cryptsetup to unlock the device in script and not dislocker

Cryptsetup also provides limited support for volumes created by other encryption systems, including loop-AES, TrueCrypt, VeraCrypt, BitLocker, and FileVault2.
cryptsetup(8) — Arch manual pages

Sometimes I forget to restart my system after a kernel update - to ram into unexpected and strange filesystem issues - then remember - bam - I forgot to restart the system after the kernel update.

No, I am using cryptsetup:

cryptsetup bitlkOpen /dev/disk/by-partuuid/<id> bitlk_stick && mount /dev/mapper/bitlk_stick /mnt/stick

Hey, this is my favorite mistake! Thanks for the hint, but this time this does not hold. :roll_eyes:

But this is still insane… Below two attempts to mount the partitions manually. Note the first attempt actually fails silently and does not prompt for passphrase. This is the partition, which can be mounted via applet (mount and open in dolphin via “Volumes and Devices”). The second one prompts for the password and correctly opens the /dev/mapper/tmp.

~ >>> sudo cryptsetup bitlkOpen /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527 tmp                                                                         [1]
~ >>> sudo cryptsetup bitlkOpen /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb tmp                                                                         [1]
Geben Sie die Passphrase für »/dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb« ein: 
~ >>>                                                             

Adding the –debug flag does not really resolve either. This is the successful call:

~ >>> sudo cryptsetup --debug bitlkOpen /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb tmp                                                                 
# cryptsetup 2.8.3 processing "cryptsetup --debug bitlkOpen /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb tmp"
# Verifying parameters for command open.
# Running command open.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb.
# Trying to open device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb with direct-io.
# Initialising device-mapper backend library.
# Trying to load BITLK crypt type from device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb.
# Crypto backend (OpenSSL 3.6.0 1 Oct 2025 [default][legacy][threads][argon2]) initialized in cryptsetup library version 2.8.3.
# Detected kernel Linux 6.12.63-1-MANJARO x86_64.
# BITLK type from GUID: normal.
# Reading BITLK FVE metadata copy #0 of size 112 on device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb, offset 37748736.
# Getting BITLK FVE metadata entries of size 854 on device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb, offset 37748848.
# Activating volume tmp [keyslot -1] using passphrase.
# dm version   [ opencount flush ]   [16384] (*1)
# dm versions   [ opencount flush ]   [16384] (*1)
# Detected dm-ioctl version 4.48.0.
# Detected dm-zero version 1.2.0.
# Detected dm-crypt version 1.28.0.
# Device-mapper backend running with UDEV support enabled.
# dm status tmp  [ opencount noflush ]   [16384] (*1)
# No more VMKs to try.
# Interactive passphrase entry requested.
Geben Sie die Passphrase für »/dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb« ein: 
# Activating volume tmp [keyslot -1] using passphrase.
# dm versions   [ opencount flush ]   [16384] (*1)
# dm status tmp  [ opencount noflush ]   [16384] (*1)
# Trying to decrypt validation metadata using VMK.
# Calculated device size is 62914560 sectors (RW), offset 0.
# Trying to activate BITLK on device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb with name tmp.
# DM-UUID is CRYPT-BITLK-tmp
# Udev cookie 0xd4de558 (semid 41) created
# Udev cookie 0xd4de558 (semid 41) incremented to 1
# Udev cookie 0xd4de558 (semid 41) incremented to 2
# Udev cookie 0xd4de558 (semid 41) assigned to CREATE task(0) with flags DISABLE_LIBRARY_FALLBACK         (0x20)
# dm create tmp CRYPT-BITLK-tmp [ opencount flush ]   [16384] (*1)
# dm reload   (254:3) [ opencount flush securedata ]   [16384] (*1)
# dm resume tmp  [ opencount flush securedata ]   [16384] (*1)
# tmp: Stacking NODE_ADD (254,3) 0:0 0600 [trust_udev]
# tmp: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4de558 (semid 41) decremented to 1
# Udev cookie 0xd4de558 (semid 41) waiting for zero
# Udev cookie 0xd4de558 (semid 41) destroyed
# tmp: Skipping NODE_ADD (254,3) 0:0 0600 [trust_udev]
# tmp: Processing NODE_READ_AHEAD 256 (flags=1)
# tmp (254:3): read ahead is 256
# tmp: retaining kernel read ahead of 256 (requested 256)
# Releasing crypt device /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb context.
# Releasing device-mapper backend.
# Closing read only fd for /dev/disk/by-partuuid/ba69d490-e487-4371-9e4e-cb96aa91c7bb.
Befehl erfolgreich.
~ >>>                                

This is the non-successful call:

~ >>> sudo cryptsetup --debug bitlkOpen /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527 tmp                                                                    
# cryptsetup 2.8.3 processing "cryptsetup --debug bitlkOpen /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527 tmp"
# Verifying parameters for command open.
# Running command open.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527.
# Trying to open device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527 with direct-io.
# Initialising device-mapper backend library.
# Trying to load BITLK crypt type from device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527.
# Crypto backend (OpenSSL 3.6.0 1 Oct 2025 [default][legacy][threads][argon2]) initialized in cryptsetup library version 2.8.3.
# Detected kernel Linux 6.12.63-1-MANJARO x86_64.
# BITLK type from GUID: normal.
# Reading BITLK FVE metadata copy #0 of size 112 on device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527, offset 117248000.
# Getting BITLK FVE metadata entries of size 1058 on device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527, offset 117248112.
# Activating volume tmp [keyslot -1] using passphrase.
# dm version   [ opencount flush ]   [16384] (*1)
# dm versions   [ opencount flush ]   [16384] (*1)
# Detected dm-ioctl version 4.48.0.
# Detected dm-zero version 1.2.0.
# Detected dm-crypt version 1.28.0.
# Device-mapper backend running with UDEV support enabled.
# dm status tmp  [ opencount noflush ]   [16384] (*1)
# No more VMKs to try.
# Releasing crypt device /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527 context.
# Releasing device-mapper backend.
# Closing read only fd for /dev/disk/by-partuuid/47119ece-19e8-423c-add4-20af5e57f527.
Fehler -1 beim Ausführen des Befehls »Falsche oder fehlende Parameter«.

Whooop, I can solve by myself:

Comparing the bitlocker partitions on Windows as suggested by @linux-aarhus revealed different key order for the non-working partition in comparison with my working bitlocker partitions. In fact position one was occupied by some recovery key instead of a proper password. This order was very likely introduced by myself, when I manually changed the passphrase for this particular partition.

Fix: Since the order cannot be changed directly, I deleted/added keys/passphrase until the desired password hold position one. Now all partitions open again with cryptsetup!

Since my setup was working very stable for a long time before, I assume some change in cryptsetup, where earlier versions supported attempts in order to try multiple “slots”, whilst the new version does not do anymore (maybe as additional security layer?).

I am therefore not sure, if this should be filed somewhere upstream (if it is considered unwanted behavior). Please let me know in case!

Thanks to all for the support!

1 Like

That is possible other than that I haven’t got the foggiest idea.

When I look at my system I see a change to cryptsetup from 2.8.12.8.3 and could be the cause.

The upstream source is found at cryptsetup / cryptsetup · GitLab, and it the likely place to create an issue.

If you look at the closed issues look for BITLK or BitLocker - a couple of issues has been addressed - could have caused a regression - but that is just an idea.

Ok, thanks!

Done: Cryptsetup fails to unlock bitlocker partition with password located at third third key position (#973) · Issues · cryptsetup / cryptsetup · GitLab

1 Like