Today in a pc of a friend a tried to update. Too much packages (around 2500) and several conflict. Using Myrlyn I tried to select manually several packages (50 to 100) and updated partially. After updating probably 400 - 500 packages unfortunately I had switch off the system and when I tried to swtich on the boot hang. The only message I see on screen is “localhost login”.
Tried “Advanced options for OpenSUSE Tumbleweed” doesn’t help. Even using the oldest version (7.0.9-1) boot doesn’t complete.
Then try to perform the full upgrade via zypper dup from the localhost login. Login as root and perform the upgrade.
Or login as the user and do sudo zypper dup It neither works, it can still be fixed by booting from a USB, but @Giorgio_os let your friend first do what @hui said
login as root I get “Have a lot of fun …” and prompt become reddish.
write “zypper dup” and I get
zypper: symbol lookup error: lib64/libcurl.so.4: undefined symbol: ngtcp2_comm_get_tls_early_data_rejected2
Yes, the system is severe damaged. Hopefully you or your friend have some backup of the important data.
Download the latest Tumbleweed snapshot ISO and dump it to an USB pen drive as suggested by @knurpht. Boot from the USB pen drive and choose “Update” instead of “Installation”.
1 Like
If you haven’t tried, and it’s enabled, boot to a previous Snapshot.
Unfortunately not. And this is the first and most important problem to solve.
Tried all four possibilities.
Even “openSUSE Tumbleweed, with Linux 7.0.9-1 (recovery mode)” that seems the oldest, hang after a while.
If you have a separate /home, in case you need to reinstall it you don’t format it and you don’t lose any data
Then first what I would do (well, in case I hadn’t a backup, which is not the case), is boot a rescue (or any Linux) system from an USB stick, mount that /home partition somewhere and back it up. This before I would try any of the magic suggested above to recover.
3 Likes
Upgrade from usb doesn’t works because;
Cannot upgrade the bootloader because of a mismatch of the boot technology. The upgraded system uses GRUB2 for EFI boot while the installation medium has been booted using Avvio con Systemd.
This scenario is not supported ...
Does this come directly when booting from the stick?
I don‘t have it mind,as i have done this type of recovery long time ago, but do you have the usual summary screen before the update happens? On the summary screen, you need to choose „grub2-efi“ under the bootloader section.
The headlines on the summary screen are clickable, so you should be able to find the bootloader setting.
Thanks for all useful hints.
In same hardware I have LinuxMint 22 and using it I access openSUSE home and make a backup copy of home folder.
Luckily openSUSE home is in separate partition, I knew but I forgot I can install without formatting home partition. I imported setting from existing user then I saw exactly same screen (and settings).
Now only a big problem remain, probably because I deleted boot loader. Now at boot I get an error message:
Boot Device Not Found
Please install an operating system on your hard disk.
Hard Disk (3F0) ...
Please start this Linux Mint system and show the result of
lsblk -f -o NAME,PTTYPE,PARTTYPE,UUID,LABEL,FSTYPE,MOUNTPOINTS,FSAVAIL,FSUSE%,HOTPLUG
Probably I’ve not been clear: no bootloader at all then nothing start. Of course I hope that both Linux are still there but I can’t start anything.
Sorry! I did not read carefully enough.
Can you start a LIVE-System or the openSUSE rescue system (from USB or DVD)?
If so, please show the result I asked for in post #14.
~$ lsblk -f -o NAME,PTTYPE,PARTTYPE,UUID,LABEL,FSTYPE,MOUNTPOINTS,FSAVAIL,FSUSE%,HOTPLUG
NAME PTTYPE PARTTYPE UUID LABEL FSTYPE MOUNTPOINTS FSAVAIL FSUSE% HOTPLUG
sda gpt 0
├─sda1
│ gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac 2054338D54336526 Ripristino ntfs 0
├─sda2
│ gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b 1433-F888 vfat /boot/efi 54,5M 43% 0
├─sda3
│ gpt e3c9e316-0b5c-4db8-817d-f92df00215ae 0
├─sda4
│ gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 56C45345C4532691 Windows_10 ntfs 0
├─sda5
│ gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac CEC68B9CC68B8405 ntfs 0
├─sda6
│ gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 A446883746880C6C DATI ntfs 0
├─sda8
│ gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 7d650f0f-b9ce-471d-ab8c-1a035660c750 opSUSE_Tumb_root ext4 0
├─sda9
│ gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 881bb5b8-441e-4ad6-9540-31ee02501eca oSU_Tum_home xfs 0
├─sda10
│ gpt 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f d857a1db-d0f2-4bea-8491-56476a3be25d swap [SWAP] 0
├─sda11
│ gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 08f921f3-9711-48eb-a23b-b818b0d9ae72 LinuxMint_22_1 ext4 / 80,1G 13% 0
└─sda12
gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 a3dd0636-75e3-40a1-ad19-24240cf36c86 ext4 0
sdb dos 1
├─sdb1
│ dos 0xb 14BF-27A9 SG2DBOOT vfat /media/anto/SG2DBOOT
│ 161,4M 18% 1
└─sdb2
dos 0xc 14AA-17D9 SG2DISOS vfat /media/anto/SG2DISOS
264,4M 0% 1
sr0
Using Super Grub Disk I can start both LinuxMint and openSUSE. Then both os are “working”.
Of course I need a working bootloader too.
According to your posts #1 and #4 your openSUSE Tumbleweed system is (was) broken due to an aborted update ???
Did you fix this in the mean time?
If not it might be better to repair that broken update first and then the broken bootloader.
I’ve not been clear, sorry.
At present both os can be started using Super Grub Disk and seems working normally. By the way openSUSE has been reinstalled completely.
The only (big) problem left is bootloader. When I switch on the system I don’t get anything but error message I wrote.