On logging in this am i had a message to say there was 1350 udates, ok… install them.
The system was no longer responding well afterwards so i rebooted even though i wasn’t prompted to do so.
The system is now a broken Leap / Tumbleweed system.
How can i undo / repair what has gone wrong?
At boot time i only seem to be able to get anywhere by loading the bootloader!
This can only happen if you’ve mistakenly tried to add a TW package (via 1-click). Can you boot at all? Can you boot up in console mode (no X-server) with internet connectivity?
Check the configured repos, and disable/remove any non-Leap 15 repos.
zypper lr -d
You’ll need to run
zypper dup
to try and “downgrade” the packages back to a “Leap 15.0” consistent state again. This may involve solving a few dependency choices when prompted.
I did attempt a one click install yesterday to upgrade Python-certbot, process failed.
It appears to boot, i’m presented with a black blank screen. Can’t login to the system directly or remotely.
Can’t login via the rescue system on the installation DVD either.
On using the Avira Linux Rescue DVD to attempt to recover files and directories (Backup) i’m told the filesystems on all the partitions are unknown and or damaged.
Currently attempting to recover / repair filesystems so that i can recover some data. Spent a good few hours updating a couple website yesterday, hoping to recover my work if nothing else at the mo.
Data recovery successful or otherwise, after trying i’ll probably try recovering data by using the install DVD to re-install / repair to get a backup. Fail or otherwise succeed, i’ll probably go for fresh install and start again.
Me no appy… It’s going to be a very long day today!!!
Data recovered, i’ll now pause, have a coffee and consider my options
That’s the main thing. The pragmatic option may just to be reinstall at this point. Let’s see what others advise.
BTW, I take it that you still get a grub boot menu screen presented?
I do, but have absolutely no idea as to what this gives me.
Thank you for your support.
Filesystem repaired has given me access to data but hasn’t helped getting the system up and running or accessible in any way. Well not in a way i’m aware of.
Well, it may be worth a shot to try and boot to console mode. The success of this will depend on how broken your system is of course. Anyway, this is done by editing grub on the fly as described here
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.grub2.html#sec.grub2.menu_change
At the grub boot screen, press ‘e’ then scroll down with the arrow keys until you get to the entry with starting with ‘linux’ or ‘linuxefi’. Move to the end of the parameter list and add ‘3’ (separated by a space from the last parameter). Press ‘F10’ to boot the system with the change that you made. Hopefully, you can get to a working console. If you can login successfully and have wired internet connectivity you may be able to use zypper to reinstate your system to a consistent state again. YMMV.
Actually it would be worth trying rollback to previous snapshot, before TW “upgrade”.
Thanks for chiming in here. I’m sure that the OP would be grateful for any specific guidance you could give with rolling back.
Read documentation https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.snapper.html#sec.snapper.snapshot-boot and if there are specific questions ask them.
First follow deano_ferrari’s instructions to boot the system. Next, if you indeed have btrfs for your rootfs ( i.e. / ), do
sudo snapper list
This will present you with a list of snapshots, each with an indexnumber at the beginning of each row. Now, have a careful look at the dates and pick an indexno right before you semi-upgraded to Tumbleweed. I’ll replace that indexno with #### in the command below, replace that with the actual indexno. Do
sudo snapper rollback ####
then reboot. That should bring you, incl. repos etc. back the situation before adding the TW repo to your system.
Firstly appologies for not posting back sooner.
Secondly a big thank you to those that have offered help and support.
Unfortunately suggestions here and solutions elsewhere were failing to resolve my problem as I couldn’t even get logged into the system in any way after a few tries.
I discovered that ALL superblocks had become removed / deleted in some way and several attempts to try and recover / create a superblock failed. I wanted a system back up and running asap too.
Having successfully recovered my data though, by exporting the data from the partition on the master hard drive to a slave hard drive as a copied image from which I then extracted the data I needed, I decided that the quickest, safest and the most secure way forward was to start again with a fresh install of the OS.
I don’t think I could of trusted a recovered system as there may of been a little something somewhere that wasn’t quite right that may of exposed the system to risk.
All’s now sorted and i have a server i know i can trust, one that is safe and secure.