This is a good starting point.

Thank you very much for suggesting this link above. I have had success with this, it seems now from what I can tell. I passed '# mount /dev/mapper/system-root /mnt'  and the rest I was able to follow without alot of difficulty.

Can you tell me briefly how this happened or may have happened? Is there a way I could have prevented this from happening after the 'zypper dup' was displayed as completed in Konsole?

-Regards

On 24/05/2024 22:16, -pj wrote:

On 05-24-2024 03:08PM, Andrei Borzenkov wrote:

On 24.05.2024 23:01, -pj wrote:

On 05-24-2024 02:51PM, Andrei Borzenkov wrote:

On 24.05.2024 22:48, -pj wrote:

#hexdump -C -n 512 /dev/sdb1
00000000  01 43 44 30 30 31 01 00  20 20 20 20 20 20 20 20  |.CD001..
          |

Is it really your HDD (or SSD)? Not your live USB?

Sorry to have not pasted in susepaste, I realized and was preparing a
susepaste when your message came in here.

The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on
USB Flashdrive.

Well, in the RESULTS.txt you posted earlier it was exactly the other
way riund. Anyway

See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c

# hexdump -C -n 512 /dev/sda1
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
|................|
*
00000200

There is no bootloader where it was supposed to be according to
RESULTS.txt.

Try chrooting into your root and running "update-bootloader --reinit".
You will need to bind mount /dev, /sys, /proc and /run into chroot.

Thank you for your message. I will do as you suggest above. I have not
done this before. Could you explain in more detail at all perhaps? I
will have to look at how to do this .

How to "bind mount /dev, /sys, /proc, and /run into chroot"?

I will return to this machine in a while. I must work on another project
for a few hours now.

-Greatest Hopes