http://bugzilla.opensuse.org/show_bug.cgi?id=1018185 Bug ID: 1018185 Summary: [doc] [grub2] Explanation about boot code locations not up to date Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs@suse.com Reporter: richard.bos@xs4all.nl QA Contact: fs@suse.com Found By: --- Blocker: --- Procedure 12.1: Changing the Boot Loader Location https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref... Following a discussion about the boot code location in #1017677#c3 it appears that the documentation at the web is out of date.
In case you can take care for the above mentioned items, I create another bug ticket to address this: see if the explanation on the web can explain 'when to select which of the three options':
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse. reference/cha.grub2.html#pro.sec.grub2.yast2.location
ok, in fact this section of documentation is wrong as it changed for Leap 42.2 and TW. Now MBR use disk MBR where "/boot" lives. so if "/boot" is on /dev/sdb6, then it install grub2 to /dev/sdb. Also boot from root is not default. Default proposal is very complex code that consider partitioning setup. So currently default is pick between root/boot partition and MBR depending on disk setup.
Is the code saved to the root partition or is it saved to the /boot/grub2? Imagine that /boot has its own partition it is no longer saved to the root partition, but to the /boot partition (if the code is indeed saved to /boot/grub2). PS: a long time ago I had indeed a separate partition for /boot... As such: are there requirements for the custom partition? If so what is the requirement? Must /boot/grub reside on that partition? When there are requirements, have them stated in the documentation, please. If there is a separate /boot partition, it must be /boot. Correct?
For help to user which option use when it is not so easy. In general if opensuse is only system on disk, then MBR is always good option. If there are more systems and that system can chainload ( almost majority of current OSes ), then boot from partition is good idea unless it use specific partitioning scenarios ( it is quite long list including encrypted partitions, RAIDs and more. I will need more digging if you want exact list when what can be used).
It would be good to have this information (as is above) included in the web documentation. The documentation just needs some love.... If you can't explain when to use which of the three option, how should the regular user know ( I mean the user that must use the bootloader GUI, for whatever reason ). Making a mistake here, can have far reaching effects e.g. making the system completely unavailable. Hence good documentation is appreciated. -- You are receiving this mail because: You are on the CC list for the bug.