Raspberry pi 3 ssh remote unlock via dropbear fails with "resource busy"

Hi All,

As per the $subject of this post, I've hit an issue after following the article here: https://www.kali.org/tutorials/secure-kali-pi-2018/

In short almost everything works, the pi sits with dropbear happily listening, I can SSH to it to no problem and get prompted for the unlock password of the LUKS encrypted partition; so far so good...

After entering the correct password however, `/dev/mmc0p2` fails to mount with the error "resource busy", at which point the boot into kali fails and it drops to a recovery shell,

Has anyone encountered this issue before, could it be the SD Card ? (32GB EVO Plus 87MB/s w, 91.5MB/s r);

I'm going to try a couple differing SD Cards and see if I can workaround this issue if indeed it is hardware storage based, I'll post back with the results in the mean time if anyone knows of a potential area to explore other than swapping out hardware in the hopes something works I'm all ears.

(Yes, I've used the forum search but could not find any similar threads hence posting this).

It could be the sdcard. I'd definitely run through the instructions again. I've done it on 4 different sdcards and haven't had it drop me to a shell because it couldn't mount the partition. I'd suggest double checking on the machine you made the sdcard on - are you sure there are no typos made? :)