Opensuse leap 15.2 cant start corectrly

Hello everyone, I’ve got an issue with opensuse leap 15.2. It can’t run. I have message like belowin logs

I.m trying to start with livecd linux ale repair via fsck but it doesn’t work
Some sugestion ?

Welcome to the openSUSE forums.

As the messages says, you have a problem with a corrupt file system. Most probably the root file system. It may even be a hardware problem.

“does not work” is the worst problem definition one can supply. We need to see the command(s) you gave and the messages that came out of this.
Did you try any of the suggestions I see on your image?
A problem may also be that you run a very out of date openSUSE version that went out of support almost three years ago. Thus not many people here do have that available for reference to help you.

Thanks for reply.

I didnt try any sgestion of this screen because I need to confident that I dont colapse more than it is. When I run Live CD system rescue. List disks and run fsck I get info like below.

I am nor sure I understand this. The first screen-shot says that there are problems with the file system on /dev/mapper/system-root. But now you first are trying to check a file system on /dev/sdb. But there is no file system there, there is a partition table.

Then you try to check a file system on /de/sdb2. As I see it, there is no file system directly on /dev/sdb2, but /dev/sdb2 seems to be a LVM Physical Volume.

Do you have any idea how your mass-storage devices are configured and used?

Leap 15.2 has reached EOL on 4 january 2022… You need to upgrade to 15.3 then 15.4 then 15.5 and ultimatly 15.6.

Maybe your disk is dead, so you have to change it and to reinstall leap 15.6.

Running an operating system that is no longer maintained and skipping so many upgrades is certainly not a good idea.

You should also update regularly to receive security patches. Or configure automatic updating with the yast-online-update module.

Do you have any concrete suggestion how to do it in the current state?

You obviously need to run fsck for the device reported earlier, not some arbitrary device name. The device is /dev/mapper/system-root.

Let’s start from the beginning. I got the computer with the intention of repairing it. I don’t have a copy and I don’t want to break it more. The computer has 2 256 GB SSD drives connected by RAID. The first screenshot is the screen after starting the Opensuse 15.2 Leap system. I don’t want to mess around here because I know it’s not the best idea. So I made a bootable pendrive with the rescue system and there I listed the drives and the partition system that is on the drive. Then I ran fsck \dev\sdb2, but the command didn’t show anything, so I did fsck \dev\sdb referring to the entire drive and got a return as you can see to use the masterblock. Can anyone give me examples of commands or syntax that can help me repair the system? I need it because there are applications installed there that I need to run an external device.

Hi

I believe /dev/sdb2 is the USB stick.

Can you download and run Gparted?

That hopefully will give you a graphical representation of your storage.

Also, and this may be heresy, you could try Debian Live USB just to look at the system, and note any error messages, because the underlying code is going to be similar, and make no modifications at all.

Just get a second opinion?