sigi wrote:
> LM17 was not bootable before - obviously due to missing boot code in the LM17
> partition (although I am not aware how that could have happened). I followed your
> above link and installed Grub2 to the LM17 partition. When working through the items
> in Grub Article #4 I had to skip paras 4 and 5 for some reason I cannot remember. I
> succeeded albeit with some obscure warning, which ATTACHMENT 1 illustrates.
>
> The translation of the German text reads as follows:
>
> warning:
> File system 'ext2' doesn't support embedding.
> warning:
> Embedding is not possible. GRUB can only be installed in this setup by using
> blocklists. However, blocklists are UNRELIABLE and their use is discouraged.
>
> DO I HAVE TO CARE ABOUT THESE WARNINGS? WHAT IS THEIR MEANING?
>
That's a normal message when installing grub2 to a partition (as opposed to the MBR). Grub2 won't allow installing to a partition unless you use the --force parameter in the 'grub-install' command line (as you did). This wiki page explains the warnings you see:
https://wiki.archlinux.org/index.php/GR ... nless_diskDespite the warnings, most users don't have any problems from what I've seen. I use grub2 this way myself, including on my main Linux install of Debian, and have never seen any problems through many many updates. In any case, there's no choice if you want to use BIBM as boot manager (or any 3rd party boot manager). The boot manager needs to occupy the MBR, so grub can't be installed there.
> The result was that LM17 did boot from HDD but for one time only. Thereafter the boot
> process from HDD ended with the following message "SP < Min" (I cannot
> remember the exact wording). Only the non-Linux partitions were concerned by this
> error. Applying the "Fill E-CHS" button to the faulty partitions restored
> the bootability from HDD again and again for one time only.
>
> It was not before I changed the Drive Settings in BIBM that the bootability from HDD
> (all OS's including LM17) became permanent (cf. ATTACHMENT 2 - 1st screenshot = old
> settings, 2nd screenshot = new settings).
I don't know what the issue is/was with the drive settings, but hopefully it's settled now.