You are not logged in.

#1 2026-03-13 11:35:53

Fool4U
Member
Registered: 2026-02-25
Posts: 6

Is this normal?

I am so confused why can i still see all entries

efibootmgr -u
BootCurrent: 0006
Timeout: 2 seconds
BootOrder: 0006,0005,0004,0003,0002,0001,0000,0010,0011,0012,0013,0014,0015,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023
Boot0000* Windows Boot Manager   
Boot0001* Ubuntu   
Boot0002* Fedora   
Boot0003* Linux Boot Manager   
Boot0004* Linux Boot Manager   
Boot0005* Linux Boot Manager   
Boot0006* Linux Boot Manager   

I have used mutliple distros before so these check out but are they are important? and if not should i remove them? I hope this question is not annoying for anyone
Thank You!

Offline

#2 2026-03-13 11:47:49

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,712

Re: Is this normal?

What distro are you using now? That output seems to be from an old version of efibootmgr that hasn't been in Arch for years.

And yes, it matters, we have no idea what entries are valid.

Offline

#3 2026-03-13 12:08:15

Fool4U
Member
Registered: 2026-02-25
Posts: 6

Re: Is this normal?

Scimmia wrote:

What distro are you using now? That output seems to be from an old version of efibootmgr that hasn't been in Arch for years.

And yes, it matters, we have no idea what entries are valid.

I am currently on 6.19.6-arch1-1 with kde plasma and this issue was even before i started using arch and I am not dual booting or anything

Offline

#4 2026-03-13 12:27:04

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,712

Re: Is this normal?

Then why aren't the paths being shown, as verbose output became default a long time ago? That's important information to know what those entries are actually doing.

Anyway, adding -v should get that output, but you should probably look into what's happening, if you're overriding efibootmgr or something (type -a efibootmgr)

Offline

#5 2026-03-13 12:35:51

Fool4U
Member
Registered: 2026-02-25
Posts: 6

Re: Is this normal?

Scimmia wrote:

Then why aren't the paths being shown, as verbose output became default a long time ago? That's important information to know what those entries are actually doing.

Anyway, adding -v should get that output, but you should probably look into what's happening, if you're overriding efibootmgr or something (type -a efibootmgr)

my apologies here are they

efibootmgr -v
BootCurrent: 0006
Timeout: 2 seconds
BootOrder: 0006,0005,0004,0003,0002,0001,0000,0010,0011,0012,0013,0014,0015,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023
Boot0000* Windows Boot Manager    HD(2,MBR,0x5a1eb830,0x265980,0x7d800)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
      dp: 04 01 2a 00 02 00 00 00 80 59 26 00 00 00 00 00 00 d8 07 00 00 00 00 00 30 b8 1e 5a 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 00 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Ubuntu    HD(1,GPT,2c1e5045-6672-4461-ba3d-8e1a426d4894,0x800,0x100000)/\EFI\ubuntu\shimx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 45 50 1e 2c 72 66 61 44 ba 3d 8e 1a 42 6d 48 94 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 75 00 62 00 75 00 6e 00 74 00 75 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0002* Fedora    HD(1,GPT,d25ba3bd-8996-4469-a144-b92f0a2aa633,0x800,0x12c000)/\EFI\fedora\shimx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 c0 12 00 00 00 00 00 bd a3 5b d2 96 89 69 44 a1 44 b9 2f 0a 2a a6 33 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0003* Linux Boot Manager    HD(1,GPT,8737e088-655b-4e21-8998-e5cc5c8513b3,0x800,0x200000)/\EFI\systemd\systemd-bootx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 88 e0 37 87 5b 65 21 4e 89 98 e5 cc 5c 85 13 b3 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0004* Linux Boot Manager    HD(1,GPT,168ba53c-4aa6-4c47-8e36-cee15dad34ae,0x1000,0x400000)/\EFI\systemd\systemd-bootx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 00 40 00 00 00 00 00 3c a5 8b 16 a6 4a 47 4c 8e 36 ce e1 5d ad 34 ae 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0005* Linux Boot Manager    HD(1,GPT,1686aedc-df09-4bba-8ee0-4caedb2a1d16,0x800,0x200000)/\EFI\systemd\systemd-bootx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 dc ae 86 16 09 df ba 4b 8e e0 4c ae db 2a 1d 16 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0006* Linux Boot Manager    HD(1,GPT,d47294a8-2ac4-4272-a705-85f6b6e734e9,0x800,0x200000)/\EFI\systemd\systemd-bootx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 a8 94 72 d4 c4 2a 72 42 a7 05 85 f6 b6 e7 34 e9 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

Offline

#6 2026-03-13 12:47:32

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,712

Re: Is this normal?

So it looks like you have 4 systemd-boot entries, all on different partitions, as well as Ubuntu and Fedora entries also on different partitions. If you look at `lsblk -o +PARTUUID`, you can see the partition UUIDs, I'm guessing that most of those in the list don't exist anymore?

The Windows entry is on a different disk. Does that exist?

Offline

#7 2026-03-13 14:13:29

Fool4U
Member
Registered: 2026-02-25
Posts: 6

Re: Is this normal?

Scimmia wrote:

So it looks like you have 4 systemd-boot entries, all on different partitions, as well as Ubuntu and Fedora entries also on different partitions. If you look at `lsblk -o +PARTUUID`, you can see the partition UUIDs, I'm guessing that most of those in the list don't exist anymore?

The Windows entry is on a different disk. Does that exist?

Yes none of those exist exist except arch and as for windows on a diff disk; i am only using a single nvme on this device so i dont think so
I also checked partitions using your command and also fdisk -l; there is nothing out of ordinary its just standard 3 partitions with 8 gb of swap and all of them are derived from a single disk
I hope i am not disturbing you too much thank you for your cooperation

Offline

Board footer

Powered by FluxBB