I've tried to set up Dropbear and Busybox on my virtualization host running Debian Jessie, so I could unlock the encrypted filesystems from the initramfs, before the actual boot. I've followed this guide: https://stinkyparkia.wordpress.com/2014/10/14/remote-unlocking-luks-encrypted-lvm-using-dropbear-ssh-in-ubuntu-server-14-04-1-with-static-ipst/
I've done a setup using this exact guide before, and it works like a charm to this day. However, this time I'm not actually encrypting the root filesystem, but only an extra partition that contains non-system-critial data, my VM images to be exact. I thought it would be a good idea to unlock that drive before boot time, because I didn't want to run into issues with KVM; I don't know what KVM does if it doesn't find its machines after starting up, and I'd rather not find out.
But now, long story short - something went wrong (early unlocking doesn't work as expected) and primarily I'm just concerned to get the system back to its earlier state so I can boot up normally without the data partition. I can work on the server by starting up a live distribution and chrooting in. I've manually reverted all the steps in the guide (except for Step 1) and rebuilt the initramfs, but still I'm dropped back to Busybox after rebooting and connecting via SSH. I'm slightly afraid of just removing Busybox and Dropbear as that could lock me out of the system entirely.
Does anybody know which settings might have been changed by the steps in that guide that I'm not seeing? All config files etc. that I touched are back to how they were before, but still Busybox starts instead of the actual OS... how do I change that?
Many thanks in advance