So for some reason PlayOnLinux does not like my laptop, I always have display issues after trying to install it. Either way to recover from my most recent adventure, I figured I would just unzip my tar archive over the current setup, and this worked to a point. I was able to get back into the system, hurrah. But I was now having display issues with Steam, causing it not to load. I like to play around (I always wondered what rm -rf / did, 'exactly'...now I know) so I figured, I would wipe the system, install a new instance of Debian 9, unzip over it, and go from here. So now I am here.
I installed a new instance of Debian Stretch. This install is to an encrypted LVM spanning 2 drives, exactly as the backup came from.
At this point we have the Laptop running Stretch 9 & Kernal 4.05, while the archive was made on Kernel 4.17.
Booted to a live filesystem, mounted the LVM and drive with the tar.gz, ran standard extraction of the archive to root of the LVM. This proceeded correctly, no errors.
I rebooted the system, and grub send me to the 4.05 recovery as I expected.
I altered /etc/crypttab with the new UUIDs for the drives with the output of
Code: Select all
cryptsetup luksUUID /dev/sd$$
Code: Select all
update-initramfs -u
I ran
Code: Select all
update-grub
Reboot and grub still tries to force me into the 4.05 kernel.
Obviously I am missing something, but I am not sure what. Any points in the correct direction would be great.
Thanks for everything!