No boot after dbus-broker update

General system Newbie
1

Did the dbus-broker update today, and since that the system does not boot. There is no boot manager (systemd-boot) at all, only blank screen.

EndeavourOS is installed on an external SSD and works flawless since the last update.

Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDS500G3X0C-00SJG0                      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x81ab4538

Device         Boot   Start       End   Sectors   Size Id Type
/dev/nvme0n1p1 *       2048   1187839   1185792   579M  7 HPFS/NTFS/exFAT
/dev/nvme0n1p2      1187840 976771071 975583232 465.2G  7 HPFS/NTFS/exFAT


Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: SSD 870 EVO     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 85E74688-6E12-4B0F-8653-FECCDDEA1564

Device         Start       End   Sectors   Size Type
/dev/sda1       4096   2052095   2048000  1000M EFI System
/dev/sda2    2052096 940905353 938853258 447.7G Linux filesystem
/dev/sda3  940905354 976768064  35862711  17.1G Linux swap

Partition 3 does not start on physical sector boundary.


Disk /dev/sdb: 114.61 GiB, 123060879360 bytes, 240353280 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6e6b1770

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *         2048 240287743 240285696 114.6G  7 HPFS/NTFS/exFAT
/dev/sdb2       240287744 240353279     65536    32M ef EFI (FAT-12/16/32)


Disk /dev/mapper/ventoy: 2.43 GiB, 2608148480 bytes, 5094040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb64c04a4

Device                   Boot   Start     End Sectors  Size Id Type
/dev/mapper/ventoy-part1 *         64 4849663 4849600  2.3G  0 Empty
/dev/mapper/ventoy-part2      4849664 5093375  243712  119M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 2.19 GiB, 2355683328 bytes, 4600944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0000,0004,0001,0002,0005
Boot0000* Linux Boot Manager    HD(1,GPT,034b87f0-a0d9-48ff-b6bd-475aa0ca7270,0x1000,0x1f4000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0001* Hard Drive    BBS(HD,,0x0)
Boot0002* USB   BBS(USB,,0x0)80033003500350038003100300037006200620032003800620032003400310000007fff04000000424f
Boot0004* UEFI OS       HD(1,GPT,034b87f0-a0d9-48ff-b6bd-475aa0ca7270,0x1000,0x1f4000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0005* UEFI:  USB, Partition 2       PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(0,0)/USB(1,0)/HD(2,MBR,0x6e6b1770,0xe528000,0x10000)0000424f

thanks for help,
moxdrox

2

This may not help, but did you explicitly install dbus-broker-units? I found that I had to (it did not ask me if I wanted to install it automatically). To fix my system, I had to arch-chroot into my system from an Endeavour OS USB and then do the explicit install of dbus-broker-units. Then my system could boot (I was getting dbus errors during the boot up procedure that I could see…perhaps your case is different).

1 Like
3

i think so. Maybe stupid question but how do i arch-chroot?

4

https://discovery.endeavouros.com/system-rescue/arch-chroot

5

That worked. dbus-broker-units are already installed.

//edit
tried to reinstall boot loader, wich gave me following error message:

Mount point '/efi' which backs the random seed file is world accessible, which is a security hole!
Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole!
1 Like
6

Hi,

You need to mount ESP with the following options: dmask=0137,fmask=0027. Once it’s done, you’ll be able to proceed further.

See also "bootctl install" outputs some warnings about /efi mount point and random seed file in the terminal

7

Done that. Now no error messages, but system is still stuck on boot.
reinstall-kernels doesn‘t help either.

8

is it still breaking on debus-broker-units because i have not yet updated my system and during the update i saw this and thought of it suspicious and stopped in between.
Should i just install the default debus-daemon-units right now ?

9

Does this affect only systemd-boot?

10

I didn’t try grub. Had to figure out how to switch.

11

I followed your advice, i updated my system, then before a reboot I explicitly reinstalled dbus-broker-units sudo pacman -S dbus-broker-units, as a precautioned I reran sudo reinstall-kernels, and I’m able to reboot just fine with no issues, everything is working fine

12

For me none of the commands worked.
Ended up with reinstalling the system.

13

Did an eos-update today and now i have the exact same behavior. No systemd-boot only blank screen.

Did arch-chroot, reinstall-kernels and bootctl install. None of that worked.

Maybe its my hardware. Had an old Bios on my Asrock B450M Pro4. Now I have updated the Bios and installing EndeavourOS from an backup :slight_smile: