On 17/08/2020 04.43, Mark Misulich wrote:
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote:
Tried booting any rescue media on USB stick? I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
I would try the openSUSE rescue image.
< http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-...
I tried to run the Supergrub2 software which I copied to a USB stick. When I booted the computer the bios recognized the USB stick, but I wasn't able to access the USB stick and the software after I selected
On Sun, 2020-08-16 at 23:50 +0200, Carlos E. R. wrote: the USB stick. It just went back to the password screen for the bios.
Next, I downloaded the opensuse rescue cd for which you provided the link above. I wrote it to the USB stick and made it a bootable image using Suse Studio Imagewriter.
Nonono.... don't do anything. Just write the image to the USB as is. The image is already bootable. dd if=openSUSE-...iso of=/dev/sdX oflag=direct bs=16M or cp openSUSE-...iso /dev/sdX or cat openSUSE-...iso > /dev/sdX
When I put it in the USB port of the laptop and booted the laptop, I was able to boot the rescue software from the USB stick.
Ok, good.
After booting up the rescue system, I opened Yast and tried to run the bootloader software. The software ran to the point that an error window popped up. It says:
YaST2 (on localhost.localdomain)
Error
Execution of command "[["/usr/bin/grub2-editnv","list"]]" failed.
Exit code: 1
Error output: /usr/bin/grub2-editnv: error: failed to get canonical path of 'LiveOS_rootfs'
When I clicked on "OK", another dialog box popped up.
YaST2(on loacalhost.localdomain)
Error
YaST cannot configure the bootloader because it failed to find the root file system.
OK
I ran the boot loader software on my desktop for a comparison to see if I could remember any differences from the configuration presented on the laptop when I ran the bootloader software in yast on that machine. On the Boot Code Options tab, the desktop software has checked:
Boot from Master Boot Record
and below it the following two options are checked:
Set active Flag in Partition Table for Boot Partition
Write generic Boot Code to MBR
On the laptop, I vaguely remember that it had the following selected
Boot from Master Boot Record
and below it
Write generic Boot Code to MBR
Could it be that the laptop Bootloader software should have also presented as checked, the option
Set active Flag in Partition Table for Boot Partition
If it wasn't checked, could that be the source of my present problem in booting, and how do I fix it?
You mention the MBR, but I thought you were using UEFI? The system to boot is very different. The generic procedure to repair a system, would be (mutandis mutandi): mount /dev/sda3 /mnt # assuming sda3 is the faulty root system mount /dev/sda2 /mnt/boot # assuming sda2 is the separate # boot partition if it exists mount /dev/sda1 /mnt/boot/efi # assuming sda1 has the efi fat part, # if it exists. It doesn't if your # boot is "Classic" mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev chroot /mnt You might have to edit /etc/mtab to match. If you need network, it might fail and you would have to edit some files. yast # Not yast2. You need the text version of yast, # running from the failed system, not from the # rescue system. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)