dep composed on 2021-08-19 23:23 (UTC):
| tree -D /boot/efi/ (on/from both sda1 and sdc1)
├── [May 18 14:36] EFI │ ├── [Jun 2 14:45] BOOT │ │ ├── [May 19 12:55] bkpbootx64.efi │ │ ├── [Aug 19 14:24] bootx64.efi │ │ ├── [Aug 19 14:24] fbx64.efi │ │ ├── [May 18 14:36] grubx64.efi │ │ └── [Aug 19 14:24] mmx64.efi │ └── [May 18 14:36] ubuntu │ ├── [Aug 19 14:24] BOOTX64.CSV │ ├── [Aug 19 14:24] grub.cfg │ ├── [Aug 19 14:24] grubx64.efi │ ├── [Aug 19 14:24] mmx64.efi │ └── [Aug 19 14:24] shimx64.efi
... Above is approximately all I expected to see. This is from one of mine: # tree -f /boot/efi/ /boot/efi ├── /boot/efi/EFI │ ├── /boot/efi/EFI/BOOT │ │ ├── /boot/efi/EFI/BOOT/BOOTX64.EFI │ │ └── /boot/efi/EFI/BOOT/fbx64.efi │ ├── /boot/efi/EFI/debian10 │ │ └── /boot/efi/EFI/debian10/grubx64.efi │ ├── /boot/efi/EFI/opensuse │ │ └── /boot/efi/EFI/opensuse/grubx64.efi │ ├── /boot/efi/EFI/opensusetw │ │ └── /boot/efi/EFI/opensusetw/grubx64.efi │ └── /boot/efi/EFI/tubuntu │ ├── /boot/efi/EFI/tubuntu/BOOTX64.CSV │ ├── /boot/efi/EFI/tubuntu/grub.cfg │ ├── /boot/efi/EFI/tubuntu/grubx64.efi │ ├── /boot/efi/EFI/tubuntu/mmx64.efi │ └── /boot/efi/EFI/tubuntu/shimx64.efi ├── /boot/efi/grub2 │ └── /boot/efi/grub2/custom.cfg
When I run the command on /dev/sdc1 it runs through 44086 directories and 447378 files which when piped to a file runs 42 megs, so I'll not attach it.
That I totally would not have expected. I suppose it may be that tree mishandles chroot environments.
| efibootmgr -v
BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0002,0006,0005 Boot0000* ubuntu HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(\EFI\ubuntu\shimx64.efi) Boot0002* UEFI OS HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(\EFI\BOOT\BOOTX64.EFI) Boot0005* Hard Drive BBS(HD,,0x0)AMGOAMNO........o.W.D.C. . .W.D.S.5.0.0.G.1.R.0.A.-.6.8.A.4.W.0....................A...........................>..Gd-.;.A..MQ..L.1.2.4.2.0.2.0.A.0.0.A.1. . . . . . . . ......AMBOAMNO........o.W.D.C. .W.D.6.0.0.3.F.R.Y.Z.-.0.1.F.0.D.B.0....................A...........................>..Gd-.;.A..MQ..L.9.V.E.H.0.L.L.2. . . . . . . . . . . . ......AMBOAMNO........o.W.D.C. .W.D.1.0.1.K.R.Y.Z.-.0.1.J.P.D.B.0....................A...........................>..Gd-.;.A..MQ..L.P.7.X.G.W.0.G.M. . . . . . . . . . . . ......AMBOAMNO........q.T.S.-.R.D.F.5. .S.D. .T.r.a.n.s.c.e.n.d....................A.............................>..Gd-.;.A..MQ..L.T.S.-.R.D.F.5. .S.D. .T.r.a.n.s.c.e.n.d......AMBO Boot0006* ubuntu HD(4,GPT,f3d5923e-cff9-4b47-beb9-be3a8442e1a0,0x800,0x96000)/File(EFI\Ubuntu\grubx64.efi)
Has this cast any light on the situation?
I was hopeful, but the GRUB_DISTRIBUTOR=s and GRUB_DISABLE_OS_PROBER=s are missing, and I may need blkid output as well to confirm where I think f3d5923e-cff9-4b47-beb9-be3a8442e1a0 comes from.