rEFInd loads and refreshes slowly: scanfor manual, and only one FS driver

[FreezyLemon]

I'm using the official Arch package and installed the boot loader/manager with refind-install.

When starting refind, it takes almost 10 seconds for the menu to show up. Other boot loaders like GRUB don't take nearly as long. I tried to speed it up by setting scanfor manual and even disconnecting other drives from the system. Both did not reduce the loading time. There is only one driver (ext4) in the drivers directory.

I tried enabling the logs to see what could cause it, and it looks like the delay happens after the ext4 driver finishes loading and before it starts scanning for volumes:

==========Loading drivers==========
12:30:39 - Starting ext4_x64.efi
12:30:39 - Using load options ''
12:30:39 - Note: ext4_x64.efi is a driver
12:30:39 - 'EFI\refind\drivers_x64\ext4_x64.efi' is a valid loader
12:30:39 - Getting EFI variable 'SecureBoot' from NVRAM
12:30:39 - Launching 'ext4_x64.efi'
12:30:39 - Program has returned 0

----------Next loader----------

==========Scanning for volumes==========
12:30:48 - Found handles for 5 volumes
...

Any idea on what I could try to speed it up? Everything else works well (using the menu, booting into Windows/Linux), but loading the menu or refreshing via Esc takes 5-10 seconds every time.

[Funami]

I’m having the exact same issue. My thought was that it takes so long for finding all the volume handles. For me it identifies one ' whole disk volume', 3 times 'unknown volume' and one "Error 18 reading boot sector of '(null)'" occurs. A total of 6 volume handles are found. In the EFI shell it shows in the Mapping Table the working partitions

• FS0 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)/HD...
• FS1 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)/HD...

and the others

• BLK0 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)
• BLK3 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x1)
• BLK4 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x2)
• BLK5 PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x3)

I’m not sure if it is of interest, but I’m using an eMMC-drive, and it has the additional "disks" mmcblk1boot0 and mmcblk1boot1 besides my main disk mmcblk1.

[FreezyLemon]

My thought was that it takes so long for finding all the volume handles.

Hm.. I doubt this is the problem, at least for me. I tried this both with just one and also with 5 storage devices attached, without noticing any difference in load times. And other boot loaders don't take nearly as long, either.