On 8/10/20 2:41 PM, JJM de Faber wrote:
On 10-08-2020 20:31, DennisG wrote:
On 8/10/20 1:55 PM, Carlos E. R. wrote:
On 10/08/2020 15.16, JJM de Faber wrote:
On 10-08-2020 15:06, Carlos E. R. wrote:
On 10/08/2020 14.02, Carlos E. R. wrote:
On Monday, 2020-08-10 at 13:37 +0200, Carlos E. R. wrote:
Thanks, but that doesn't solve the issue that something is changing what I write there, and trying to boot something else instead of openSUSE.
Just a wild guess . . . is it possible that device.map is the cuprit? If the grub install is incorrectly determining the boot order from its bios guess (when there is no device.map file) or there is an incorrect device.map file present, it is possible that the wrong location will be called. Or possibly grub2-mkconfig put an error in the grub.cfg file?
--dg There is no devicemap in grub2
From the GRUB manual:
"GRUB avoids this problem nowadays by using UUIDs or file system labels when generatinggrub.cfg, and we advise that you do the same for any custom menu entries you write. If the device map file does not exist, then the GRUB utilities will assume a temporary device map on the fly. This is often good enough, particularly in the common case of single-disk systems . . . However, the device map file is not entirely obsolete yet, and it is used for overriding when current environment is different from the one on boot."
From openSUSE 15.2 documentation:
"GRUB 2 avoids this problem by using device ID strings (UUIDs) or file system labels when generating|grub.cfg|. GRUB 2 utilities create a temporary device map on the fly, which is usually sufficient, particularly in the case of single-disk systems.
However, if you need to override the GRUB 2's automatic device mapping mechanism, create your custom mapping file|/boot/grub2/device.map."|
|So . . . if the device.map is there, it will be used. And if it is not present but grub installation guesses wrong, then the virtual device map is wrong, too.|
|What am I missing?|