[opensuse] My mini server fails to boot after yast online update
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a small MSI Cubi N machine that I use as home server and multimedia server on my workroom, with Leap 42.1. I applied with yast a month worth of updated, which included a kernel, and rebooted. It failed. I got the MSI logo, then blank screen. I don't think it gets to grub. If at the MSI logo I press "Del" I get the Bios configuration page. If I plug the installation USB, I can boot that one, theh choose "boot from hard disk", which works. The system is currently running. The machine is UEFI. How do I diagnose this? I got some info: Boot Info Script 0.75 [14 November 2016] ============================= Boot Info Summary: =============================== => No boot loader is installed in the MBR of /dev/sda. => libparted MBR boot code is installed in the MBR of /dev/sdb. => libparted MBR boot code is installed in the MBR of /dev/sdc. sda1: __________________________________________________________________________ File system: vfat Boot sector type: FAT16 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/boot/bootx64.efi /efi/boot/fallback.efi /efi/opensuse/MokManager.efi /efi/opensuse/grub.efi /efi/opensuse/grubx64.efi /efi/opensuse/shim.efi I don't know if this is correct. No boot loader in MBR of sda? That's the boot disk. It is the only UEFI machine I have, so I can't compare. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlh2u/IACgkQtTMYHG2NR9UHYwCcCenKLg6BjT9RFnElgnhpHRUl veYAoI+0vLYg+VCz23/jkoA6tJGwKDWP =wFpW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
12.01.2017 02:12, Carlos E. R. пишет:
Hi,
I have a small MSI Cubi N machine that I use as home server and multimedia server on my workroom, with Leap 42.1. I applied with yast a month worth of updated, which included a kernel, and rebooted.
It failed.
I got the MSI logo, then blank screen. I don't think it gets to grub.
If at the MSI logo I press "Del" I get the Bios configuration page. If I plug the installation USB, I can boot that one, theh choose "boot from hard disk", which works. The system is currently running.
The machine is UEFI.
It does not mean it cannot boot in legacy BIOS mode. Installation menu on UEFI does not offer "Boot from hard disk" as far as I remember, so it suggests you *do* boot in legacy BIOS. Do you have /sys/firmware/efi directory after boot? Does "efibootmgr -v" work?
How do I diagnose this?
You verify how your system is configured to boot.
I got some info:
Boot Info Script 0.75 [14 November 2016]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda. => libparted MBR boot code is installed in the MBR of /dev/sdb. => libparted MBR boot code is installed in the MBR of /dev/sdc.
sda1: __________________________________________________________________________
File system: vfat Boot sector type: FAT16 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/boot/bootx64.efi /efi/boot/fallback.efi /efi/opensuse/MokManager.efi /efi/opensuse/grub.efi /efi/opensuse/grubx64.efi /efi/opensuse/shim.efi
I don't know if this is correct. No boot loader in MBR of sda? That's the boot disk.
How do you know? "Boot disk" is whatever BIOS is configured to boot from.
It is the only UEFI machine I have, so I can't compare.
It does not look like you boot in EFI mode.
On 2017-01-12 04:39, Andrei Borzenkov wrote:
12.01.2017 02:12, Carlos E. R. пишет:
The machine is UEFI.
It does not mean it cannot boot in legacy BIOS mode. Installation menu on UEFI does not offer "Boot from hard disk" as far as I remember, so it suggests you *do* boot in legacy BIOS. Do you have /sys/firmware/efi directory after boot? Does "efibootmgr -v" work?
Yes, see the post I just sent. For the moment, it is solved. I don't know if this little thing can boot in legacy mode, but I remembered that last month, when I set this up, I saw a uefi boot menu at the start. Isengard:/boot/efi/EFI # tree . ├── boot │ ├── bootx64.efi │ └── fallback.efi └── opensuse ├── MokManager.efi ├── boot.csv ├── grub.cfg ├── grub.efi ├── grubx64.efi └── shim.efi 2 directories, 8 files The "grub.cfg" is text: set btrfs_relative_path="yes" search --fs-uuid --set=root 0d457df1-b43d-4587-aa5a-6c919bcbedb8 set prefix=(${root})/boot/grub2 source "${prefix}/grub.cfg" The first line is curious, I use ext4, not btrfs.
How do I diagnose this?
You verify how your system is configured to boot.
Yeah, I know! LOL, but how? I know very little about UEFI systems, can barely diagnose them.
I got some info:
Boot Info Script 0.75 [14 November 2016]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda. => libparted MBR boot code is installed in the MBR of /dev/sdb. => libparted MBR boot code is installed in the MBR of /dev/sdc.
sda1: __________________________________________________________________________
File system: vfat Boot sector type: FAT16 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/boot/bootx64.efi /efi/boot/fallback.efi /efi/opensuse/MokManager.efi /efi/opensuse/grub.efi /efi/opensuse/grubx64.efi /efi/opensuse/shim.efi
I don't know if this is correct. No boot loader in MBR of sda? That's the boot disk.
How do you know? "Boot disk" is whatever BIOS is configured to boot from.
The other two disks are data disks and external, added later.
It is the only UEFI machine I have, so I can't compare.
It does not look like you boot in EFI mode.
Well, I do... see the other post. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-01-12 00:12, Carlos E. R. wrote:
Hi,
I have a small MSI Cubi N machine that I use as home server and multimedia server on my workroom, with Leap 42.1. I applied with yast a month worth of updated, which included a kernel, and rebooted.
It failed.
I got the MSI logo, then blank screen. I don't think it gets to grub.
If at the MSI logo I press "Del" I get the Bios configuration page. If I plug the installation USB, I can boot that one, theh choose "boot from hard disk", which works. The system is currently running.
The machine is UEFI.
How do I diagnose this?
I found the issue, but not the cause of it. The clue was here: Isengard:~ # efibootmgr BootCurrent: 0006 Timeout: 6 seconds BootOrder: 0006,0005,0003,0002,0001,0000 Boot0000 Windows Boot Manager Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller Boot0003* opensuse-secureboot Boot0005* opensuse Boot0006* UEFI: VerbatimSTORE N GO, Partition 1 Isengard:~ # I remembered that the BIOS was set to boot "opensuse", whereas on a secure boot system it might be "opensuse-secureboot". So I rebooted, and in the bios made sure the first entry was that one, rebooted again, and it worked. I have no idea why the BIOS had "opensuse" as the default entry, as that can not boot. Who/what did that? No idea. And why did it not print any message? No EFI menu, either (there is a 6 second timeout before booting main entry, apparently). Current status: Isengard:~ # efibootmgr BootCurrent: 0003 Timeout: 6 seconds BootOrder: 0003,0005,0002,0001,0000 Boot0000 Windows Boot Manager Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller Boot0003* opensuse-secureboot Boot0005* opensuse Isengard:~ # man efibootmgr Isengard:~ # efibootmgr -v BootCurrent: 0003 Timeout: 6 seconds BootOrder: 0003,0005,0002,0001,0000 Boot0000 Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(4ccc6a6150a1,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0..BO Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(4ccc6a6150a1,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO Boot0003* opensuse-secureboot HD(1,800,4e000,cada5ef3-03a1-4d0b-a984-49c1c16c75bb)File(\EFI\OPENSUSE\SHIM.EFI) Boot0005* opensuse HD(1,800,4e000,cada5ef3-03a1-4d0b-a984-49c1c16c75bb)File(\EFI\OPENSUSE\GRUBX64.EFI)..BO Isengard:~ # Another curiosity: why the presence of "Windows Boot Manager"? This machine never had any Windows, I bought it new. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (2)
-
Andrei Borzenkov -
Carlos E. R.