On 28/06/2020 16.26, Michael Fischer wrote:
On Sun, Jun 28, Carlos E. R. wrote:
On 28/06/2020 13.58, Michael Fischer wrote:
You are calling fdisk on partitions. Instead, run
fdisk -l /dev/nvme0n1
Well, that information was already included, but if you like:
Sorry, I should have said "next time" :-)
$ fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt Disk identifier: C2D48243-DA0E-456D-BD55-D3BEE176DBEC
Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1026047 1024000 500M Microsoft basic data /dev/nvme0n1p2 3147776 500117503 496969728 237G Linux filesystem
/dev/nvme0n1p1 -> /boot/efi /dev/nvme0n1p2 -> /
You could do, instead:
tree -apugh --si /boot/efi
$ tree -apugh --si /boot/efi/ /boot/efi/ └── [drwxr-xr-x root root 8.2k] EFI ├── [drwxr-xr-x root root 8.2k] boot │ ├── [-rwxr-xr-x root root 1.2M] bootx64.efi │ └── [-rwxr-xr-x root root 359k] fallback.efi └── [drwxr-xr-x root root 8.2k] opensuse ├── [-rwxr-xr-x root root 58] boot.csv ├── [drwxr-xr-x root root 8.2k] fw ├── [-rwxr-xr-x root root 70k] fwupx64.efi ├── [-rwxr-xr-x root root 155] grub.cfg ├── [-rwxr-xr-x root root 1.1M] grub.efi ├── [-rwxr-xr-x root root 124k] grubx64.efi ├── [-rwxr-xr-x root root 1.2M] MokManager.efi └── [-rwxr-xr-x root root 1.2M] shim.efi
Looks normal to me. cer@Telcontar:~> tree -apugh --si /boot/efi /boot/efi └── [drwxr-xr-x root root 8.2k] EFI ├── [drwxr-xr-x root root 8.2k] auxiliary │ ├── [-rwxr-xr-x root root 1.2M] MokManager.efi │ ├── [-rwxr-xr-x root root 60] boot.csv │ ├── [-rwxr-xr-x root root 155] grub.cfg │ ├── [-rwxr-xr-x root root 1.1M] grub.efi │ ├── [-rwxr-xr-x root root 124k] grubx64.efi │ └── [-rwxr-xr-x root root 1.2M] shim.efi ├── [drwxr-xr-x root root 8.2k] boot │ ├── [-rwxr-xr-x root root 1.2M] MokManager.efi │ ├── [-rwxr-xr-x root root 1.2M] bootx64.efi │ ├── [-rwxr-xr-x root root 359k] fallback.efi │ ├── [-rwxr-xr-x root root 150] grub.cfg │ └── [-rwxr-xr-x root root 1.1M] grub.efi ├── [drwxr-xr-x root root 8.2k] main_opensuse │ ├── [-rwxr-xr-x root root 1.2M] MokManager.efi │ ├── [-rwxr-xr-x root root 68] boot.csv │ ├── [-rwxr-xr-x root root 150] grub.cfg │ ├── [-rwxr-xr-x root root 1.1M] grub.efi │ ├── [-rwxr-xr-x root root 124k] grubx64.efi │ └── [-rwxr-xr-x root root 1.2M] shim.efi └── [drwxr-xr-x root root 8.2k] opensuse ├── [-rwxr-xr-x root root 1.2M] MokManager.efi ├── [-rwxr-xr-x root root 58] boot.csv ├── [-rwxr-xr-x root root 155] grub.cfg ├── [-rwxr-xr-x root root 1.1M] grub.efi ├── [-rwxr-xr-x root root 124k] grubx64.efi └── [-rwxr-xr-x root root 1.2M] shim.efi 5 directories, 23 files cer@Telcontar:~>
So, is this a case of "boot from rescue disk and run various grub commands to re-write /boot/efi and all should be well" or ...?
The problem that was reported was with an MBR boot.
You mean, in the previous thread?
And.. MBR boots and /boot/efi are mutually exclusive? (sorry, not up on these matters).
Not exactly, you might install both (I'm not sure). But you can not /use/ both in a single session.
Still, I am bothered by the differnces between the two systems:
/dev/nvme0n1p1: SEC_TYPE="msdos" UUID="5591-235C" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f95c0606-ecaa-44af-8fd0-51f9980f26a9
/dev/sda1: LABEL="ESP" UUID="4A08-2713" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="bb-2b82-4a57-9652-75c0189aaf2a"
Can the LABEL aspect here really screw things up?
No, the label is indifferent. It goes by some flag or type I don't remember the name. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)