http://bugzilla.opensuse.org/show_bug.cgi?id=1182957 http://bugzilla.opensuse.org/show_bug.cgi?id=1182957#c5 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE --- Comment #5 from Michael Chang <mchang@suse.com> --- (In reply to Dr. Werner Fink from comment #4)
I've have shrink /boot round about 1MB and inserted a clean partition with 1MB size with the boot_grub flag. Now I can run
grub2-install -vvvv /dev/nvme0n1
and indeed after enabling the SSD in BIOS it boot flawless ... now I've looked into the YaST2 logs and found that it uses --force with grub2-install and does not check the warning nor error messages from grub2-install to warn the user.
This NVME SSD M2 disk was a replacment for a broken non-NVME SSD M2, that is I had done this in the rescue mode without knowing about the need of having a small boot_grub partition for the (standard) GPT. Otherwise I had choosen MBR/DOS.
Feel free to reasign this to the YaST team
Thanks Andrei for pointing this out, and also Werner to verify the solution really works. About the --force flag, it is required to proceed with block list installation. As long as we have to support installation into partition boot record, ripping it off unconditionally will make the scenario to fail. And I think it is a bit weird to warn user about, for eg, you are going to install to extX partition but it is unreliable ... We have been support that for years, maybe lilo, grub 0.96 and on ... Therefore I close this as resolved feature. Hope this helps. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.