On Wed, Dec 02, 2015 at 09:30:05AM -0800, Carl Myers wrote: > I know this is a bug tracker, not a support forum, but given this is a known > bug, if it isn't going to be fixed soon, could someone point me to a resource > for how to fix a machine in this state? > > I presume the instructions would look something like this: > 1. boot with live CD > 2. unlock encrypted volume, mount to /media/root/ and /media/root/home
Of course you do have to mount /media/root/boot and /media/root/boot/efi as well. After all with encrypted root, you have a seperate boot partition that is unencrypted for loading the kernel and initrd, and since it is a UEFI machine, you have a vfat partition to sture the efi boot loader files too. > 3. bind mount dev, proc, and sys > 4. chroot into /media/root > 5. <do something to convince it to not be broken > 6. grub-install /dev/nvme0 > 7. reboot > > I'm having trouble figureing out step 5, I've done the rest with success =| I suspect step 5 might be 'do nothing'. Step 6 is probably all you need and the part grub-installer fails to do because it doesn't think /dev/nvme* is a valid device name. -- Len Sorensen
