On 28/06/2020 13.58, Michael Fischer wrote:
Hello all (and hopefully Andrei),
While reading the recent thread (... Zypper dup renders 15.1 to 15.2...) I got curious about my own system - which had a reinstall (15.0) a few months ago, which went...poorly. It took several installs and boot attempts to get the thing to come up (which is really odd because it was a reinstall of 15.0 on top of the same 15.0 on seemingly perfectly good hardware)
Now I see that perhaps my /boot/efi is not configured correctly?
bootinfoscript doesn't even find/describe the disk where /boot/efi lives, (/dev/nvme0n1) for some reason.
Unfortunately, the script doesn't study /dev/nvme media, I understand.
The guts of my system is
$ df -h Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 233G 9.3G 212G 5% / /dev/nvme0n1p1 500M 5.1M 495M 2% /boot/efi /dev/sdb1 458G 97G 338G 23% /home
There are a few data/backup/etc. disks attached, I ignore these for simplicity
$ blkid /dev/nvme0n1* /dev/nvme0n1: PTUUID="c2d48243-da0e-456d-bd55-d3bee176dbec" PTTYPE="gpt" /dev/nvme0n1p1: SEC_TYPE="msdos" UUID="5591-235C" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f95c0606-ecaa-44af-8fd0-51f9980f26a9" /dev/nvme0n1p2: UUID="65da4abd-8d32-4a12-a6d3-5f237343714d" TYPE="ext4" PARTLABEL="primary" PARTUUID="0c505856-c975-4f34-9119-7a9e70d78b2c"
$ sudo fdisk -l /dev/nvme0n1*
You are calling fdisk on partitions. Instead, run fdisk -l /dev/nvme0n1 I don't know how a second nvme disk would be named (I only have one).
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
Disk /dev/nvme0n1p1: 500 MiB, 524288000 bytes, 1024000 sectors
partition 1, ignore.
Disk /dev/nvme0n1p2: 237 GiB, 254448500736 bytes, 496969728 sectors
partition 2, ignore.
$ ls -al /boot/efi/EFI/opensuse/ total 3600 drwxr-xr-x 3 root root 8192 Feb 14 16:29 . drwxr-xr-x 4 root root 8192 Feb 14 11:07 .. -rwxr-xr-x 1 root root 58 Feb 14 11:07 boot.csv drwxr-xr-x 2 root root 8192 Feb 14 16:29 fw -rwxr-xr-x 1 root root 70464 Feb 14 16:29 fwupx64.efi -rwxr-xr-x 1 root root 155 Feb 14 11:07 grub.cfg -rwxr-xr-x 1 root root 1060704 Feb 14 11:07 grub.efi -rwxr-xr-x 1 root root 123904 Feb 14 11:07 grubx64.efi -rwxr-xr-x 1 root root 1158688 Feb 14 11:07 MokManager.efi -rwxr-xr-x 1 root root 1208968 Feb 14 11:07 shim.efi
(that `fw` directory is empty)
You could do, instead: tree -apugh --si /boot/efi
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. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)