Partition Recovery Failure, I/O Error Until Drive Is Reseated

[xi-pinmping]

Hey, love the software and its a huge help to the community.
Currently it is the only thing that fits into what im trying to do. I use an external drive for media such as music and videos and it is bitlocker encrypted on an exfat partition for compatibility with dualboot windows. The card works fine in windows but not in linux suddenly after very little change. I added umask=022 to the second entry to fstab but it booted fine for a few runs. Now before I reach tty I see 'Dislocker has failed to mount, /mnt/Media has failed dependency check'. Running the commands normally seems to work fine but is quite annoying as it resets some of my xdg icons.

UUID=13f40512-0e12-4367-9c27-0771be4bf443	/         	ext4      	rw,relatime,commit=15	0 1

# /dev/nvme0n1p1 LABEL=SYSTEM
UUID=B2D5-3B2D      	/efi      	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p5 LABEL=BOOT
UUID=FC5A-980E      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

/swapfile           	none      	swap      	defaults  	0 0

# encrypted sd
/dev/mmcblk0p1	/mnt/dislocker	fuse.dislocker	user-password=<password>,rw,nofail	0	0
/mnt/dislocker/dislocker-file	/mnt/Media	exfat	nofail,loop,nosuid,nodev,umask=022,x-gvfs-show	0	0

journalctl and systemctl status mnt-dislocker are of no help, but the output of the former is

systemd[1]: Mounting /mnt/dislocker...
systemd[1]: mnt-dislocker.mount: Mount process exited, code=exited, status=1/FAILURE
systemd[1]: mnt-dislocker.mount: Failed with result 'exit-code'.
systemd[1]: Failed to mount /mnt/dislocker.

[xi-pinmping]

I can no longer unlock from dislocker even on command line but i can view the contents of the card on windows no issue.

[xi-pinmping]

I believe this was due to a recent change in apparmor as I am able to mount like I was previously after disabling it. The weird part is it was fine for approximately two or three boots after enabling apparmor/auditd before it became an issue.

[xi-pinmping]

Issue has popped back up, this time with no apparmor enabled at all. When trying to run the first command to create the dislocker-file i get

Thu Apr 11 20:03:38 2024 [CRITICAL] Error during reading the volume: not enough byte read.
mount: /mnt/Media: failed to setup loop device for /mnt/dislocker/dislocker-file. 

and then my journalctl shows that /mnt/media and /mnt/dislocker are failing dependencies and it appears my device is timing out waiting for the sd card to be recognized. When I take it out and pop it back in, the issue is resolved and i can decrypt and mount it almost immediately. The other partition on the card is a keyfile used to unlock my home partition and is able to be mounted fine without reseating the card even though it says the first (bitlocker) partition is timing out.

journalctl section:

arch kernel: mmcblk0: recovery failed!
arch kernel: I/O error, dev mmcblk0, sector 499744640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
arch kernel: Buffer I/O error on dev mmcblk0, logical block 62468080, async page read
arch kernel: mmcblk0: recovery failed!
arch kernel: I/O error, dev mmcblk0, sector 499744640 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
arch kernel: mmcblk0: recovery failed!
arch kernel: I/O error, dev mmcblk0, sector 65408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
arch kernel: logitech-hidpp-device 0003:046D:101B.0006: HID++ 1.0 device connected.
arch systemd[1]: dev-mmcblk0p1.device: Job dev-mmcblk0p1.device/start timed out.
arch systemd[1]: Timed out waiting for device /dev/mmcblk0p1. 

Is there some kind of module I should add to my mkinitcpio i may be missing now? This is only a relatively recent change but im not sure what would have caused it. I am on the most recent version of the cachyos kernel but it appears to persist across the default linux kernel as well. Soon to test LTS with it.

Currently my modules and hooks for mkinitcpio are:

MODULES=(amdgpu radeon vfat fuse)
HOOKS=(systemd autodetect microcode kms modconf keyboard sd-vconsole keymap consolefont block sd-encrypt filesystems) 

[xi-pinmping]

Confirmed issue is also happening on a brand new card as well with a fresh bitlocker partition. When booting now, without reseating if I run commands to manually unlock the partition I get an error

Wed Apr 17 23:09:08 2024 [CRITICAL] Error during reading the volume: not enough byte read.
mount: /mnt/Media: failed to setup loop device for /mnt/dislocker/dislocker-file.

[xi-pinmping]

As an update, interestingly enough the issue does not present itself in the event I need to force power off (Example: Lately swaylock appears not to be able to wake from sleep and leads to a red screen when unlocked, I force off by holding power for several seconds and it blanks off without 'properly' shutting down) and power back on. At poweron, my symbolic links to the drive are active and drive is open. So maybe it is getting locked or held onto by some process when it is shutting down properly that prevents it from being opened properly after a 'proper' shut down. Or bitlocker isnt being closed all the way I guess.