Peculiar Problem Booting Leap 15.6

I have a desktop (old) i3-2105 @ 3.10GHz, 2 SSDs (one for OpenSUSE and one for Windows 10). The OpenSUSE SSD has Leap 15.5 and 15.6. In addition I have a portable SSD with Leap 15.6. When booting I use F12 key to select where I wish to work, else system boots into Windows as default. My working data is on a separate partition so I can access it from either installations.

I have no idea as to how it happened but the SSD 15.6 started freezing to a black screen. I could boot into 15.5 and tried to check disk integrity and found nothing wrong. And after selecting the SSD, the Grb menu would come up but 15.6 would not boot and end up in booting into Windows.

Now I booted up to the portable SSD (via F12). The installation there is fine. Next as a matter of curiosity after F12 key and selecting Portable SSD to boot from, on the Grub menu I scrolled to the Leap 15.6 on internal SSD and it booted and worked properly!

I cannot make out what could be wrong. I even tried refreshing the Grub on internal SSD but makes no difference.

What can I try next? Or should I go in for a clean reinstall of 15.6 on the internal SSD?

PrakashC

1 Like

Then it seems that your internal 15.6 system is fine, but perhaps something is broken in its boot setup.

You have not told us whether you are using UEFI booting or legacy booting.

It would help if you could give more details on what you tried – what system was running and what command you used.

1 Like

Thanks nrickert, I will try to detail my problem.

While working with Leap 15.6 KDE Plasma off the internal SSD, the problem started with suddenly the system going sort of blank and then presenting a text login screen. Entering name and password again, both as user and root did not have any effect. Had to switch off the PC and restart. The F12 key start would not show the Leap SSD and booted into Windows. Closing the Windows and restarting would show both the SSDs again and could boot to Leap 15.6.

Suspecting some problem with the 15.6 installation I booted into 15.5, downloaded GSmartControl and checked the SSD. It showed all is well. Again to ensure that problem was with Grub, I changed the waiting time in the boot loader in 15.5. Rebooted into 15.6 and did the same to the boot loader from there.

The problem continued and then worsened to the stage that selecting 15.6 from Grub menu ended up in Windows. That brings us to my portable SSD on which I have installed 15.6. I use it when I am away from my PC and have to work on my daughter’s PC. Since I have my working files on a separate partition (internal SSD), I can boot with the portable SSD and access the working files.

As I mentioned in the first post out of curiosity, on the Grub menu brought up by the portable ssd, I scrolled down to the option to boot 15.6 from internal SSD. It worked. However, even now the pc freezes and ends up in a black screen.

Let me add a side issue which may have a bearing. Once in a while I do play ā€˜Five or More’ (from Gnome). I now found starting it caused the system to logout. I have since uninstalled the game. But the other problem continues.

Sorry I missed mentioning I use legacy booting.

It does now look as if there is something wrong with your system.

Yes, you could try a re-install of 15.6. But perhaps the SSD really is failing. I don’t have any experience with SSD failure modes, so I’m not sure how it would behave in that case. However, and SSD has a limited life, and it seems that your system is somewhat old.

I just now tried to reinstall 15.6 afresh. However ran into an error. A Yast 2 file had the wrong checksum and the installation aborted. Any idea of what has happened?

PrakashC

Yast is going away

That is not related here. @PrakashC is talking about a fresh install of 15.6

Did you verify the download OK?
How did you create the USB?

I have used the same pen drive to install 15.6 on the internal SSD originally as well as the portable SSD after verifying the down load. I had turned the online repos on. The error message was in respect of the online repo. I should have mentioned it in my post. Sorry. Unfortunately I had failed to note the detailed contents of the message.

How can these posts be shifted to a new thread?

But I think the question is not:
ā€œwhat device did you install fromā€ … but:

What tool did you use to write the image to the pen drive (dd command, or Ventoy, or SUSE Imagewriter, or something else?)

I has written the USB with SUSE Imagewriter. But that does not matter as on the next attempt I ran into the same problem and have noted the details of the error message.

Here it is:
YAST2
Wrong Digest
The expected checksum of the file /mnt/var/tmp/AP_OxTHB2VS/x86-64/mariadb-10.11.11-150600.4.10.1.x86-64.rpm is xxxx(I am not typing the long checksum) but the current checksum is (no information)
The file has changed … since the repository creator signed it.

On seeking further details in the next message the info is
Package Mariadb is broken (Update repository with updates from SUSE Linux Enterprise 15)

The problem is therefore in the online repository not in my USB.

PrakashC

Have you compared the downloaded ISO with its shasum?

Of course I did that before writing to USB drive. And have used the same to install 15.6 on two earlier occasions. First on the internal SSD, that is the one which started giving trouble after about 6 months. And the second on portable SSD which is working fine.

As I have mentioned in my earlier post the problem is with the file (rpm) in the repository. I have detailed the file name too.

PrakashC

Trying to repeat an update/install when there’s a corrupted downloaded rpm, You need to clean the zypper cache, since the corrupted package download will still be there:
sudo zypper clean

Possibly SATA cable, not SSD.

Usually it is glitching hardware.
Clean your PC inside including PSU, reattach cables, check cables, use UPS.

This is nonsense. A not matching checksum of a package is a sign of a corrupted download…not of a dusty computer.

You’re not experienced enough.

https://bugzilla.opensuse.org/show_bug.cgi?id=1131540

Also I managed to corrupt packages by overclocking memory. System works OK for some time, then zypper up destroys some updated packages - but not all.

I do not think I can help with your grub problem (which you posted about in a different thread).

But if I read the original link you posted about, you had an issue where when running LEAP-15.6 from your external SSD, your screen would go black and PC would be mostly unresponsive?

I do not know for certain if I properly described your original issue, but it reminds me of an issue I had with a recent external SSD enclosure working together with an external Samsung SSD. I had the black screen freeze symptoms that i think might match what you experienced with your external SSD.

My external enclosure for my external SSD connects to my PC via USB-3.1. So in my case, I immediately suspected that this black screen, was due to the interface between my laptop and the external enclosure going to sleep. Either my computer running LEAP-15.6 was putting the computer’s USB port to sleep, or the SSD enclosure firmware was putting its USB port to sleep.

I posted here about this problem in post #67 (I think) in this thread:

I put in place a couple of things to solve it. One of them worked (or maybe both were needed to make it work). I do not know which.

What I did was setup the LEAP-15.6 on the external SSD to have my PC not to time out its USB that was associated with the SSD enclosure. And further, I created a cronjob (on the external SSDs LEAP-15.6) that when running from that LEAP-15.6, does a tiny write or read to the USB enclosure’s SSD every 3 minutes to stop the enclosure from going to sleep due to inactivity.

Ever since then I have had no black screens (before then I had a couple dozens, where only a reboot would recover).

…

As for your grub problem, hopefully some others can help you there.

Yep … why even reply in this thread when the OP hasn’t responded since 3 Aug … a full week ago.

The OP should not fracture a problem into multiple threads.