My problem is which snapshot?? I deleted as many as I could recognize as unimportant last year, … but the list is still pretty incomprehensible.
Hard to even tell which was the borked snapshot from today!
This is not the output from the command requested by @hendersj
And please don’t use screenshots for terminal output. Simply copy the initial command and the output and paste it here in the forum via the preformatted text button </>.
Please copy/paste the text rather than taking a screenshot. Screenshots can be difficult to read. And the -d is really, really important, because that gives us the URLs so there’s no question how the repo is set up or where you’re getting the updates from. When you copy the text, also copy the command you executed so there’s no question for those reading what command you ran. For example:
jhenderson@localhost:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-----------------------------+------------------------------------------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------------------+--------
1 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | 99 | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | openSUSE-Leap-15.5-1 | openSUSE-Leap-15.5-1 | No | ---- | ---- | 99 | rpm-md | cd:/?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001 |
3 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages -> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/update/leap/15.5/backports_debug/ |
4 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/backports/ |
5 | repo-debug | Debug Repository | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.5/repo/oss/ |
6 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.5/repo/non-oss/ |
7 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/oss/ |
8 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/non-oss/ |
9 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.5/repo/non-oss/ |
10 | repo-openh264 | Open H.264 Codec (openSUSE Leap) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap/ |
11 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.5/repo/oss/ |
12 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterpr-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/sle/ |
13 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/sle/ |
14 | repo-source | Source Repository | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/source/distribution/leap/15.5/repo/oss/ |
15 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/oss |
16 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/non-oss/ |
jhenderson@localhost:~>
The URI column is crucial for us to see, and you don’t get that without adding a parameter - -d gives us all the info we need. (though I note that $releasever isn’t in there; you can test if the repos use it by using zypper --releasever=15.6 lr -d and see if anything still says it’s 15.5; I didn’t actually know that before, but just tried it and confirmed that that will work as a way to identify which repos need to be manually edited or disabled prior to upgrading).
For which snapshot to use to get back to “functional”…If you’re not sure which one is the right one, I’d start with the earliest ‘pre’ snapshot on Jan 16 (today), 452 (which seems to be the one you’re on, according to the datestamp and description on 456, which is the current snapshot).
What I’m saying about the logs is that if you copy them before rebooting, then you won’t have to figure out which snapshot is the one the logs need to be pulled from. I’m recommending taking the steps to do the upgrade again, but being very prescriptive as to the commands you should run from where you are right now.
So I’d update the snapshot you’re on to the latest 15.5 packages, and then do the upgrade to 15.6 as I described, capturing all logs before rebooting after the upgrade is complete (again, as I described).
# zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------------+--------
1 | hardware | Ha-> | Yes | (r ) Yes | No | 99 | rpm-md | https://download.opensuse.org/repositories/hardware/15.5/ |
2 | packman | pa-> | Yes | (r ) Yes | Yes | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.5/ |
3 | repo-backports-update | Up-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/backports/ |
4 | repo-debug | De-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.5/repo/oss/ |
5 | repo-debug-non-oss | De-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.5/repo/non-oss/ |
6 | repo-debug-update | Up-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/oss/ |
7 | repo-debug-update-non-oss | Up-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/non-oss/ |
8 | repo-non-oss | No-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.5/repo/non-oss/ |
9 | repo-oss | Ma-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.5/repo/oss/ |
10 | repo-sle-debug-update | Up-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.5/sle/ |
11 | repo-sle-update | Up-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/sle/ |
12 | repo-source | So-> | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/source/distribution/leap/15.5/repo/oss/ |
13 | repo-update | Ma-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/oss |
14 | repo-update-non-oss | Up-> | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.5/non-oss/ |
15 | virtualbox | Vi-> | Yes | (r ) Yes | Yes | 120 | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/15.5/x86_64 |
I would consider that less than readable, … but here you go.
Problem there - it is not possible to update the current 15.5 snapshot, as it breaks (=not bootable)!
Using preformatted text formatting helps. That’s the </> button in the forums editor toolbar. (That’s what I used for the sample I provided).
I’ll edit yours to format it properly.
zypper up fails or renders the system unbootable? Let’s start by ensuring the system is on the latest 15.5 files before trying to get to 15.6.
I would disable the virtualbox repo, as that is probably not changing to 15.6 with the $releasever variable.
Agreed.
Done.
OK, so with the state that the system is in right now, does a zypper up to the last available packages work?
If not, then you can try reverting to an earlier snapshot (if you know when you tried what, that would help narrow down which snapshot is likely to be a good one to revert to). But be aware that snapshots may well contain configuration items (I don’t think /etc is included by default, but I could be mistaken - I honestly haven’t looked that closely).
If an up works, then we can look at the upgrade to 15.6.
I mentioned before, but running zypper --releasever=99.99 lr -d would provide some insight into which repos releasever will work with. Anything that shows a “99.99” in the URL will change. Whether what it changes to is a valid/correct directory may be another matter. For example, if a path for 15.5 has “/15.5/” as part of its URI, but the 15.6 release uses “/openSUSE_15.6/”, then releasever isn’t going to help, because it’s just a variable substitution. (I used “99.99” there because it’ll be really obvious when listing the repos which ones releasever will work with and which ones they won’t - it’s just a display, doesn’t change any configuration when used with zypper lr.)
No; tried again Friday, updating only packages. Same result - nonbootable root snapshot.
/etc seems to be included in the root snapshot, … what a mess.
Wish there were some way to figure out WHERE the update breaks the current snapshot.
TFTR!
I would definitely start just going back one snapshot at a time to see what’s happening.
Something else that would be useful is to see what you see when booting after the upgrade - you say it’s not bootable, but is there anything on the screen at all? If so, what? (This is a case where a photo might be useful)
If not, if you get a grub menu, try adding ‘s’ in the Linux load line (to boot single user mode) - does that start (you should get a terminal prompt that asks for the root password).
The boot result is the list of snapshots, and message to select a bootable snapshot.
Good idea, … will test.
What, something like this?
@hendersj you can’t up 15.5 anymore, many repositories have been deleted or have pending delete requests.
Main repos still seem to be available, at least in my testing.
But yeah, that’s why I think disabling the Virtualbox (and now that I look again, Packman probably) repos would be a good idea.
I suppose running zypper dup without an up probably would work well with a recent update as well, after making sure all the repos either support $releasever or are disabled (or the URLs are changed to the 15.6 release URLs.)
@hendersj yes, but there is nothing new going there, so an up will not do anything…
Assuming it got the last updates that were released the end of December, that’s also true.
Have only been able to force specific updates (e.g. Firefox) since September, … there are 400+ currently pending for 15.5.
All repos currently show current:
# zypper lr
Repository priorities in effect: (See 'zypper lr -P' for details)
90 (raised priority) : 1 repository
99 (default priority) : 6 repositories
# | Alias | Name | Enabled | GPG Check | Refresh
---+---------------------------+----------------------------------------------------------------------------+---------+-----------+--------
1 | hardware | Hardware tools (15.5) | No | ---- | ----
2 | packman | packman | Yes | (r ) Yes | Yes
3 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes
4 | repo-debug | Debug Repository | No | ---- | ----
5 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ----
6 | repo-debug-update | Update Repository (Debug) | No | ---- | ----
7 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ----
8 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes
9 | repo-oss | Main Repository | Yes | (r ) Yes | Yes
10 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ----
11 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes
12 | repo-source | Source Repository | No | ---- | ----
13 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes
14 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes
15 | virtualbox | VirtualBox for openSUSE 15.5 - x86_64 | No | ---- | ----
No, … only a text box listing snapshots - no logo, no GUI.
I think a picture would definitely be helpful here. Are you able to select a snapshot, or is it a static list?
Do you ever see the grub screen on reboot?
I might be inclined to do an upgrade from media. It sounds like something could potentially be really wrong with this system if you haven’t been able to run updates since September.
This may be a case of it being necessary to reinstall entirely if an upgrade from media (which should be the same as a ‘dup’) doesn’t work.