Hello, I am dual booting Leap 15 with Windows 10 Pro. I have a Ryzen 3 2200G CPU and an Asus Prime A320M-K motherboard (with the latest BIOS). Both operating systems (and the EFI partition) are on an M.2 drive. Because I’m using the integrated CPU graphics, I had to upgrade the kernel to 4.18. Secure Boot is enabled in the BIOS (the default), and I am booting through Grub2 in EFI mode. The Windows 10 installation has ‘Fast Startup’ (or whatever it’s called) disabled.
The first installation about a month ago went fine. I booted into Suse a few times but mostly used Windows. After about a week. I tried to boot into Suse again. The Grub menu came up OK, I selected Suse, about 4-5 messages appeared (as normal) but then the machine hung. I let it run, and after approx 2-3 mins a huge number of messages scrolled past. I am pretty certain that the first one referred to the ‘nvme’ module and the implication of the rest was that the M.2 SSD was now unreadable. Once the messages settled down and clearly the machine wasn’t going to boot, I rebooted (with a hardware reset). This time Grub didn’t load and scarily I went straight into the BIOS screen, with no boot options available at all (apart from the CD drive). I later found out (by luck) that switching the mains power off then on seemed to reset the motherboard and the BIOS was able to detect the SSD drive again. However the ‘opensuse’ EFI boot option in the BIOS did not bring up the Grub menu, but went straight in to Windows (as did the Windows Boot Manager option). The Windows 10 installation seemed to be fine.
I then tried booting the Suse installation through the installation media, but got the message “Unable to boot from this partition” (or something like that). I eventually decided to reinstall Leap (which is actually pretty quick on an M.2 drive). I did that and everything was fine - for about another week, and then the same thing happened. And then again a third time, which brings me up to date.
The boot log messages don’t seem to be stored in /var/boot/log - which is consistent with the M.2 drive becoming (temporarily) unusable during boot.
If you’ve read this far, thanks! Two questions:
- What diagnostics could I use to try and trace this problem? I have no idea where even to start. It goes without saying that this might not be an Opensuse problem but something to do with Windows, the motherboard or BIOS.
- More specifically, could Secure Boot be the problem? Is there a periodic (weekly?) scan by Windows 10 which might be messing with either the BIOS or the EFI partition? Obviously I can test by disabling Secure Boot, reinstalling Leap and then waiting a week.
Any clues or pointers would be appreciated.