More info on this problem...
Output of
efibootmgr -v
:
Code: Select all
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0009,0001,000A,0000,0005
Boot0000* Windows Boot Manager HD(2,GPT,b1852155-bd66-41e5-917c-28de0f83f40b,0xfa000,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)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.}...a................
Boot0001* ubuntu HD(1,GPT,a1c4fc88-2629-43a1-996c-4e625773d9f4,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0005 Windows Boot Manager HD(2,GPT,a8ba65b9-935f-4258-bd31-1df47fb78675,0x3304b,0x2730c)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO
Boot0007* ubuntu HD(1,GPT,a1c4fc88-2629-43a1-996c-4e625773d9f4,0x800,0x100000)/File(\EFI\UBUNTU\GRUBX64.EFI)..BO
Boot0009* ubuntu HD(2,GPT,a8ba65b9-935f-4258-bd31-1df47fb78675,0x3304b,0x2730c)/File(\EFI\UBUNTU\GRUBX64.EFI)..BO
Boot000A* Windows Boot Manager HD(1,GPT,a1c4fc88-2629-43a1-996c-4e625773d9f4,0x800,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO
Output of
sudo blkid
:
Code: Select all
/dev/sda1: UUID="7366-1FFF" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="a1c4fc88-2629-43a1-996c-4e625773d9f4"
/dev/sda2: UUID="79e0ecc3-d1a5-41a8-90d8-df78d0f25701" TYPE="ext4" PARTUUID="1acb7cbd-8bba-4c6c-b57e-a394faf5629c"
/dev/sdb1: LABEL="Data" UUID="5AA6B3C7A6B3A245" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fa03cc90-3717-4b08-a716-1b279c971f4b"
/dev/sdc1: LABEL="DataBU" UUID="52D02E5BD02E4597" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d5123b5d-fb5c-40a2-8e38-0affbefbf1f3"
/dev/sdd1: LABEL="Recovery" UUID="01D497A4CAFAECE0" TYPE="ntfs" PARTLABEL="M-oM-?M-?M-oM-?M-?M-oM-?M-?M-oM-?M-?$" PARTUUID="c101d536-f618-45aa-b54c-8e1e4b478020"
/dev/sdd2: UUID="E42A-F805" TYPE="vfat" PARTUUID="a8ba65b9-935f-4258-bd31-1df47fb78675"
/dev/sdd4: UUID="01D497A788D85AC0" TYPE="ntfs" PARTUUID="a94233a6-4edb-430c-aa6e-950f7d98a5c2"
/dev/mmcblk0p1: LABEL="SysSnap" UUID="0ee8d592-e78f-4a09-8b5d-a59421260b9a" TYPE="ext4" PARTUUID="c99186e7-01"
/dev/sdd3: PARTUUID="8d79c695-a00e-4428-814c-00af5a957549"
/dev/mmcblk0: PTUUID="c99186e7" PTTYPE="dos"
And output of
lsblk -f
:
Code: Select all
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 7366-1FFF /boot/efi
└─sda2 ext4 79e0ecc3-d1a5-41a8-90d8-df78d0f25701 /
sdb
└─sdb1 ntfs Data 5AA6B3C7A6B3A245 /mnt/Data
sdc
└─sdc1 ntfs DataBU 52D02E5BD02E4597 /mnt/DataBU
sdd
├─sdd1 ntfs Recovery 01D497A4CAFAECE0
├─sdd2 vfat E42A-F805
├─sdd3
└─sdd4 ntfs 01D497A788D85AC0 /mnt/WinSys
The entry I'm trying to get rid of is referred to as
Boot000A and PARTUUID
a1c4fc88-2629-43a1-996c-4e625773d9f4.
I tried using
efibootmgr -b 000A -B
to delete the entry, but it still shows up in the grub menu.
And if I do the above followed by:
update-grub
, it makes no difference.
So that raises another question: When I give the number of the entry I want deleted, is it:
- the boot order number (which would be 4 because this partition is listed at #4 in the boot order at the top of efibootmgr's output),
- the hex number in the 'name' (ie. Boot000A as I tried), or
- the ordinal number of as listed by efibootmgr (which in this case would be '6').
This is seriously confusing.
And also brings me back to the question I raised above: Does Linux need that EFI partition? Can I safely delete it? 'Cause if I can, that seems the least complicated way to do this.