13.11.2016 04:49, Carlos E. R. пишет:
Hi,
In my laptop I have Win 10, OS 13.1, and 42.2 RC2; the later just installed and doesn't boot.
In 13.1 I have grub 1, with this entry that has worked for years:
title openSUSE Factory (/dev/sda9) via chainloader rootnoverify (hd0,8) chainloader +1
but now produces this error:
Error 13: Invalid or unsupported executable format press any key to continue
The documentation says:
13 : Invalid or unsupported executable format This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
which I fail to understand. There should not be a kernel there, but grub2.
Attached is the information from bootinfoscript.
First question offtopic: => No known boot loader is installed in the MBR of /dev/sda. Do you remember how you installed MBR here? I would like to add this boot block to the list of know ones. sda9: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: XFS does not support booting from partition - it does not have any place to put boot block into. ...
+++---------------- Booting
The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk.
* Bot loader type: grub2 * Enable trusted boot: no * Status location: /dev/sda9 ("/") * Change location: * Do not install bootcode into MBR (install) * Order of hard disks: /dev/sda, /dev/sdb ----------------++-
On previous years, there was a list of choices to boot from, like "boot from root partition", which is what I wanted to do. I can not permit the installer to modify the MBR, which is customized. Touch it and booting breaks.
Now there is a line where to type the "custom boot partition". It is possible that YaST did not write the grub images at all anywhere.
This is a bug. Installer should not offer XFS for first stage install. Please open bug report.