Hello, I have a dual boot setup of opensuse TW/Win 10 on my laptop.
I don’t know which of the following incidents caused the disappearance of opensuse from the grub menu:
A recent windows 10 update happened a few days ago but after I let it finish I was still able to boot to opensuse recently.
A power blackout in the room yesterday when I was in the opensuse session. I also completed a 400 MB update of opensuse before the power blackout without rebooting (but I re-loggedin after the update). If understand the update screen right, I guess bootloader was updated as well.
After the power blackout incident in opensuse session when I boot up the machine Win10 came out automatically preparing its update done a few days ago. And however I reboot opensuse menu is long gone.
I am trying to rescue with my portable opensuse (usb drive) by using its Yast2-bootloader (probing foreign OS), but all it find is win10. Because the opensuse on the laptop uses lvm/luks managed partition encryption setup during installation, I wonder whether it is because the partition is encrypted so it can’t be seen by the rescue session?
Here’s the screenshot of laptop partition: http://i.imgur.com/CkewrNd.png?1
sda6 being / partition
sda7 being /home
sda8 being /boot (if I remember/understand right…)
I could google how to mount a luks encrypted partition. But I wonder if it works here and if it does, what mount point I should choose before I use Yast2-bootloader to fix?
Not sure of the problem but why do you have 2 LVM partitions normally you put root swap and home in a single LVM container so you only need one password and swap is protected. Note that LVM is a container for one or more partitions which then have the files systems. With boot outside the LVMs you should see grub. Sounds like something was not completed and interrupted by the power outage.
You can chose any point you like normally for temp mounts you could use /mnt
But I used the default lvm setup during the installation. I have no good understanding of lvm. I also need only one password to decrypt all partitions, except swap is not encrypted.
So I mount the encrypted partition under /mnt then yast2-bootloader addon should pick up the OS inside it?
Yes but you don’t have a MBR boot looks like you use EFI boot and your partitioning choices have complicated things. Not sure how to proceed with this configuration.
Except for the first step of “cryptsetup luksOpen /dev/sda6 fedora”, I had all kinds of errors/problems that I couldn’t understand.
Later I found that by using an installation session it would prompt for the luks password of the partition, so I used a rescue cd and launched its live installation addon in Yast. After it asked for the password of the encrypted partition, I gave the password but canceled the installation. Then I used “mount” command to see what was mounted and found something like “/dev/mapper/system-root /run/media/…” Then I mount it again under “mnt/root” and followed the steps in the link, which are:
mount /dev/mapper/system-root /mnt/root
mount /dev/sda8 /mnt/root/boot/
mount /dev/sda2 /mnt/root/boot/efi #this line was not in the link but I guessed I needed it but I'm not sure
mount -o bind /dev /mnt/root/dev
mount -o bind /proc /mnt/root/proc
mount -o bind /sys /mnt/root/sys
mount -o bind /run /mnt/root/run
chroot /mnt/root
grub2-install --no-floppy --recheck /dev/sda
grub2-mkconfig -o /boot/grub2/grub.cfg
I didn’t encounter more problems with the grub encryption like in the link on my part.
To be safe, I used the bootloader addon in yast again to generate a new grub with the repaired system and it went fine too.