Hello!
I was installing Debian on a second hard drive, and it didn't find the Solus installation. I told it to install anyway, first with the MBR on the second hard drive, then on the boot partition from the Solus install.
Then I started looking through forums, to augment my button mashing.
I can now mount the encrypted Solus root partition through either Debian or through Solus which I've installed on a flash drive (though that leaves me with two Volume Groups with the same name). I have done "clr-boot-manager update" while chrooted with and without the boot partition mounted to /boot, so now I have lots of boot-related files in both partitions. I did this by vgrename-ing the original Solus system to chroot from the USB stick, and then restoring the original "SolusSystem" name later--because clr-boot-manager couldn't parse the Debian kernel name, so it failed when run from Debian.
From Grub Rescue I have tried "set root=(hd0,1)" and "set prefix=(hd0,1)/boot/grub" and "insmod normal" at which point I get an error--normal.cfg or something doesn't exist.
I'm certain there's an easy fix to all this, but since I have no idea what I'm doing I probably just keep making it worse. Any advice?
Thanks,
HugeMess