Hi, on my tuxedo infinity pro with tri boot windows10-leap 15.1-leap 15.2 after the installation of leap 15.2 I have a black screen with this:
“minimal BASH-like line editing is supported. For the first word, TAB list possible command completition. Anywhere else TAB lists possible device or file completition”
https://paste.opensuse.org/34475495
I tried with the new leap 15.2 rescue disk to reinstall bootloader, but had this:
https://paste.opensuse.org/17644263
https://paste.opensuse.org/39488655
how can I have my laptop booting again??
Your first screenshot is from grub-2.02. However, Leap 15.2 is using grub-2.04. So somehow you are using an old left-over grub which is no longer functional.
Are you using UEFI booting or legacy MBR booting?
UEFI booting
I don’t know why 2.02 is there, I installed the new 15.2 on a existent partition formatting it and using existent/home without formatting it
Did you install it in legacy BIOS or EFI mode?
I don’t know but I think in efi mode, I don’t know how to identify if bios or uefi mode, I inserted the usb key and booted from there
As long as you are booted that way, can you give us the output from:
grep LOADER_TYPE /etc/sysconfig/bootloader
/usr/sbin/efibootmgr -v
Hi
I would surmise that since it’s Leap 15.1 and Leap 15.2 and UEFI that the /boot/efi/leap directory has been overwritten by the Leap 15.2 install and efi nvram still has the old entries for Leap 15.1…
manythanks nick, I cannot boot, so I suppose I can access this file
/etc/sysconfig/bootloader/usr/sbin/efibootmgr
via a live distribution (or windows, I discovered that pressing F2 at start to access the boot manager I can boot windows but not in leap) and search in it
LOADER_TYPE
and give the row where it is?
…the
https://paste.opensuse.org/17644263
says things about …/usr/bin/grub2-editenv… failed command and “failure to get the canonical path of liveos rootfs” but may be, I’m thinking now that I get that message from the leap 15.2 rescue usb disk.
as I said to nickert, I discovered that pressing F2 at start to access the boot manager I can boot windows but not in leap, I have some other entry with efi and opensuse but they doesn’t works.
…so I suppose I haveto reinstall grub2, I found these two
that has in the first line the same phrase I have:
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
but grub2 versio 0.97 and valid for SUSE Linux Enterprise Desktop, but updated at 03-Mar-2020, do you think are valid instructions?
and How to reinstall the GRUB boot loader | Support | SUSE
that begin with
Place your SLED 10 CD 1 or DVD in the drive and boot up to the CD or DVD. On the resulting menu select “Rescue System”
but I have the leap 15.2 rescue usb disk, and valid for SUSE Linux Enterprise Desktop, but updated at 03-Mar-2020, do you think are valid instructions?
and olso this:
that seems recent 2020.
which can I use of them?
or there is another and more simple way??
manythanks 
I misunderstood. When you said you were booting with USB key, I had assumed you were using the installer and then selecting “boot from hard drive”.
Have you tried to see if you can boot that way?
…not, I tried but doesn’t works, I booted from usb 15.2 kde live and usb 15.2 rescue disk, booted also windows10 pressing F2 and choosing boot manager from bios (or what other else it is called, UEFI or otherway…) and selecting windows, I also tried selecting other issues like opensuse but doesn’t works, furthermore trying “boot from hard drive” booting from usb keys it leads the same situation I mentioned “minimal bash-like line editing…”
Boot from live media.
Open a terminal session (“konsole” or similar), and use “su” to become root. From the live media, that should not ask for a password.
Mount your root partition at “/mnt”. That will be something like:
mount /dev/sda3 /mnt
except that it probably won’t be “sda3”. I hope you know which partition is your root partition.
Once you have done that, try:
mount --bind /dev /mnt//dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
mount -a
exit
That last “exit” should just take you out of the “chroot” environment. The result of all of that is that you should have all partitions mounted.
Can you then get us the output from:
grep LOADER_TYPE /mnt//etc/sysconfig/bootloader
When you have that output, you can shutdown for now. But post that output here, so that we can know how you installed booting.
I used leap 15.2 rescue usb disk
I mounted sda9
mount /dev/sda9 /mnt
where I installed leap 15.2 as root
after
mount -a
I get this:
modprobe: FATAL: Module fuse not found in directory /lib/modules/5.3.18
after
grep LOADER_TYPE /mnt//etc/sysconfig/bootloader
I get:
LOADER_TYPE="grub2-efi"
I did the same on /dev/sda7 that is where leap 15.1 was mounted and get the same result
That shouldn’t matter at this stage.
after
grep LOADER_TYPE /mnt//etc/sysconfig/bootloader
I get:
LOADER_TYPE="grub2-efi"
I did the same on /dev/sda7 that is where leap 15.1 was mounted and get the same result
Can you now try mounting the EFI partition.
If you directly mount the EFI partition to “/mnt”, then I am looking for the output from:
ls -l /mnt/EFI/opensuse
Or, if you prefer to mount everything as you did before, the provide the output from:
ls -l /mnt/boot/efi/EFI/opensuse
While you are about it, can we see the output from:
efibootmgr -v
good
I used the leap 15.2 live KDE usb stick,
I mount /dev/sda1 that should be the efi partition, it is label=“BOOT”, FStype=“FAT”, Type=“EFI System”
I made ls -l > fileonusbpen.txt and report here the results.
there isn’t /mountpoint/EFI/opensuse
here in ls -l > /mountpoint
total 8drwxr-xr-x 4 root root 4096 Apr 24 2019 EFI
drwxr-xr-x 2 root root 4096 Jul 13 16:17 System Volume Information
here in ls -l > /mountpoint/EFI
total 8
drwxr-xr-x 2 root root 4096 Apr 24 2019 Boot
drwxr-xr-x 4 root root 4096 Apr 24 2019 Microsoft
[/QUOTE]
doing this I get:
there isn’t /mnt/boot/efi/EFI/opensuse, only /mnt/boot
here is ls -l /mnt/boot
total 40084-rw-r--r-- 1 root root 65 Jun 30 03:22 .vmlinuz-5.3.18-lp152.20.7-default.hmac
-rw-r--r-- 1 root root 4600984 Jun 30 02:42 System.map-5.3.18-lp152.20.7-default
-rw-r--r-- 1 root root 1725 Jun 8 15:25 boot.readme
-rw-r--r-- 1 root root 228312 Jun 30 02:01 config-5.3.18-lp152.20.7-default
-rw-r--r-- 1 root root 0 Jul 11 10:44 do_purge_kernels
drwxr-xr-x 3 root root 4096 Jul 11 10:48 grub2
lrwxrwxrwx 1 root root 32 Jul 11 10:44 initrd -> initrd-5.3.18-lp152.20.7-default
-rw------- 1 root root 12837788 Jul 11 10:48 initrd-5.3.18-lp152.20.7-default
-rw-r--r-- 1 root root 432172 Jun 30 02:46 symvers-5.3.18-lp152.20.7-default.gz
-rw-r--r-- 1 root root 484 Jun 30 02:46 sysctl.conf-5.3.18-lp152.20.7-default
-rw-r--r-- 1 root root 13877734 Jun 30 02:51 vmlinux-5.3.18-lp152.20.7-default.gz
lrwxrwxrwx 1 root root 33 Jul 11 10:44 vmlinuz -> vmlinuz-5.3.18-lp152.20.7-default
-rw-r--r-- 1 root root 9036000 Jun 30 03:22 vmlinuz-5.3.18-lp152.20.7-default
[/QUOTE]
here is:
BootCurrent: 0004Timeout: 2 seconds
BootOrder: 0002,0003,0001,2003,2001,2002
Boot0000* EFI PXE 0 for IPv4 (80-FA-5B-69-82-7D) PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x1)/MAC(80fa5b69827d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0001* Windows Boot Manager HD(1,GPT,ce96f7fa-91a6-42d0-8fdd-20c80fc00c55,0x800,0x2ee000)/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.}....................
Boot0002* opensuse-secureboot HD(6,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x6aa4800,0x117800)/File(\EFI\opensuse\shim.efi)
Boot0003* openSUSE HD(5,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x74e57000,0x117701)/File(\EFI\opensuse\grubx64.efi)
Boot0004* EFI USB Device (SanDisk) PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0x0,0x1bf7c4,0x7800)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Then it seems that you have two EFI partitions. Or at one time you had two EFI partitions.
doing this I get:
there isn’t /mnt/boot/efi/EFI/opensuse, only /mnt/boot
There should be. So that’s part of what went wrong.
here is:
BootCurrent: 0004Timeout: 2 seconds BootOrder: 0002,0003,0001,2003,2001,2002 Boot0000* EFI PXE 0 for IPv4 (80-FA-5B-69-82-7D) PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x1)/MAC(80fa5b69827d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC Boot0001* Windows Boot Manager HD(1,GPT,ce96f7fa-91a6-42d0-8fdd-20c80fc00c55,0x800,0x2ee000)/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.}.................... Boot0002* opensuse-secureboot HD(6,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x6aa4800,0x117800)/File(\EFI\opensuse\shim.efi) Boot0003* openSUSE HD(5,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x74e57000,0x117701)/File(\EFI\opensuse\grubx64.efi) Boot0004* EFI USB Device (SanDisk) PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0x0,0x1bf7c4,0x7800)RC Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC
Your second EFI partition has PARTUUID=6a40e21d-6045-48d8-8ca3-94620ed1e964
Can you check whether that partition still exists, and give us its device name.
Try
ls -ld /dev/disk/by-partuuid/6a40e21d-6045-48d8-8ca3-94620ed1e964
Partition 6
Boot0003* openSUSE HD(5,GPT,6a40e21d-6045-48d8-8ca3-94620ed1e964,0x74e57000,0x117701)/File(\EFI\opensuse\grubx64.efi)
Partition 5 with the same GUID. Both are different partitions (different partition number, different offset on disk, different size). I am not sure what happens at boot time.
I hadn’t looked at that detail.
There’s a lot of inconsistency in what is being reported here.
We see: LOADER_TYPE=“grub2-efi”
and yet “/boot/efi” does not exist. I’m not sure how that is even possible – the directory “/boot/efi” should have been created early in the install.
There could be a badly messed up EFI partition. But he got far enough to have that grub prompt mentioning grub-2.02. Or maybe that is actually from grub installed in MBR or PBR. I’m hesitant to trust anything about this. Perhaps you can make more sense of it.
Hi
Need to see the likes of gdisk and lsblk output to see what partitions really exist etc?
manythanks everybody
I used leap 15.2 live KDE usb stick
linux@MININT-J122378:~> su -
MININT-J122378:~ # ls -ld /dev/disk/by-partuuid/6a40e21d-6045-48d8-8ca3-94620ed1e964
lrwxrwxrwx 1 root root 10 Jul 15 12:22 /dev/disk/by-partuuid/6a40e21d-6045-48d8-8ca3-94620ed1e964 -> ../../sda6
MININT-J122378:~ #
I don’t know why these two efi partition, but it seems that there was also before to install leap 15.2, I always considered /dev/sda1 the boot partition
using opensuse partitioner:
situation before install leap 15.2
https://paste.opensuse.org/15465431
situation now after install leap 15.2
https://paste.opensuse.org/16383878
I remounted /dev/sda6 under /mnt
and asked what you asked me yesterday that in this case /mnt/EFI/opensuse exist
MININT-J122378:/mnt/EFI # ls
boot opensuse
MININT-J122378:/mnt/EFI/opensuse # ls -l
total 3484
-rwxr-xr-x 1 root root 1158688 May 6 2019 MokManager.efi
-rwxr-xr-x 1 root root 58 May 6 2019 boot.csv
-rwxr-xr-x 1 root root 155 May 6 2019 grub.cfg
-rwxr-xr-x 1 root root 1060704 May 6 2019 grub.efi
-rwxr-xr-x 1 root root 123904 May 6 2019 grubx64.efi
-rwxr-xr-x 1 root root 1208968 May 6 2019 shim.efi
MININT-J122378:/mnt/EFI/opensuse #
MININT-J122378:~ # gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help):
Command (? for help): ^C
MININT-J122378:~ #
MININT-J122378:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 797.1M 1 loop /run/initramfs/squashfs_container
loop1 7:1 0 4.5G 1 loop /run/rootfsbase
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1.5G 0 part
├─sda2 8:2 0 2G 0 part
├─sda3 8:3 0 48G 0 part
├─sda4 8:4 0 15.6G 0 part
├─sda5 8:5 0 2G 0 part
├─sda6 8:6 0 559M 0 part
├─sda7 8:7 0 58.6G 0 part
├─sda8 8:8 0 58.6G 0 part
├─sda9 8:9 0 59.6G 0 part
├─sda10 8:10 0 59.6G 0 part
└─sda11 8:11 0 1.5T 0 part /run/media/linux/dati
sdb 8:16 1 7.5G 0 disk
├─sdb1 8:17 1 895M 0 part /run/initramfs/live
├─sdb2 8:18 1 15M 0 part
└─sdb3 8:19 1 6.6G 0 part /run/overlayfs
sdc 8:32 1 57.3G 0 disk
└─sdc1 8:33 1 57.3G 0 part /run/media/linux/STEEL
MININT-J122378:~ #