Arch Linux

Knackare

Member

Registered: 2018-11-18

Posts: 1

No operating system found with systemd-boot

I have installed Arch on a Lenovo M91p. The install went smooth with no serious error. I had before successfully performed the same install in Virtualbox.
But on reboot the computer prompts the following:

Error 1962: No operating system found. Press any key to repeat boot sequence

I believe this has to do with EFI/UEFI and that the boot doesn't get initiated.
I consider to try to edit or add some entries but i don't want to brick my computer so I would appreciate some advice.

Below is some output with comments. The output is from the shell of the archiso:

/dev/sda1 is formated with FAT32 and mounted at /mnt/boot before arch-chroot into /mnt. After arch-chroot the bootloader was installed into /boot.
/dev/sda2 is formated with BTRFS and root, home and var have their own subvolumes.

# parted -l
Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  538MB  537MB  fat32        boot  boot, esp
 2      538MB   860GB  859GB  btrfs        root
...

From the output below we can see that boot entry 0006 has the PARTUUID of the boot partion. But is it not working.

# blkid /dev/sda1
/dev/sda1: UUID="AAD5-23D0" TYPE="vfat" PARTLABEL="boot" PARTUUID="f04b880b-7979-45ec-8396-bae9e7d00a1f"

# efibootmgr -v
** Warning ** : Boot000a is not UEFI Spec compliant (lowercase hex in name)
** Warning ** : Boot000b is not UEFI Spec compliant (lowercase hex in name)
** Warning ** : please recreate these using efibootmgr to remove this warning.
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001,000B,0006,0007,0009,0004,0003,000A
Boot0000* Hard Drive    BBS(HD,,0x0)SMI USB DISK 1100.
Boot0001* Network Card  BBS(Network,,0x0)IBA GE Slot 00C8 v1365.
Boot0003* Linux Boot Manager    HD(1,GPT,570a3bdf-56d0-4479-8401-d696c3d0f5af,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0004* Linux Boot Manager    HD(2,GPT,7ed1467a-3ccb-41eb-a62c-b8975bf5811e,0x8f8d1,0xee6b2)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0006* Linux Boot Manager    HD(1,GPT,f04b880b-7979-45ec-8396-bae9e7d00a1f,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0007* Linux Boot Manager    HD(1,GPT,36ab3b64-8841-42b2-9831-ae69c51d95a8,0x800,0xfa000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0009* Linux Boot Manager    HD(1,GPT,bdfc6f0e-20c9-8742-afe8-b4b545cdef74,0x800,0x96000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot000a* UEFI: SMI USB DISK 1100       PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(4,0)/HD(1,MBR,0xb341030,0xa4,0x20000)
Boot000b* Hard Drive    BBS(HD,,0x0)P0: Samsung SSD 850 EVO 1TB   .

bugsmanagement

Member

Registered: 2017-04-21

Posts: 201

Re: No operating system found with systemd-boot

This might be able to help others diagnose this issue, can you include your boot directory contents, ie

tree /mnt/boot

and edit your first post to include that information?

EDIT:, if I'm reading your efibootmgr output correctly, HD 1 has multiple fat32 partitions marked as "boot,esp"? If that's correct, perhaps that's the source of your problem? Each disk should only have one EFI Filesystem Partition

Last edited by bugsmanagement (2018-11-21 21:43:24)

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: No operating system found with systemd-boot

IIRC the last time I formatted an EFI system partition using mkfs.fat and tried to specify a lower-case label it threw a warning about compatibilty.

What happens if you set the label as BOOT instead?

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

bugsmanagement

Member

Registered: 2017-04-21

Posts: 201

Re: No operating system found with systemd-boot

Ahh, okay, those could be old EFI entries, it would better if you would drop to a EFI shell and remove irrelevant Boot entires including the one you've just created during the install and reinstall the bootloader per Wiki instructions.

As regarding your question, the FAT32 partition label doesn't matter here, you only need to set the proper 'esp' bit on the FAT32 partition. Which you've already done that here:

 1      1049kB  538MB  537MB  fat32        boot  boot, esp

EDIT: Thought I was responding to the OP. NVM.

Last edited by bugsmanagement (2018-11-21 22:03:26)