Hi, I have update Tumbleweed on Feb 12 through zypper dup. Not sure what happened, my PC is restarted automatically (which doesn’t happen usually) during the update and stuck at CLI. If I check dmesg, it says “Start load kernel module failed”. Please guide me on how can I fix the same.
If you use btrfs and have snapshot enabled, you can boot from snapshot in grub and rollback with sudo snapper rollback.
If you don’t have snapshots or a previous kernel to load, you can try to dup again. That tends to solve most irrecoverable issues here. Options:
- Try to do it from emergency mode if you can get to it and it mounts. You can get to emergency mode by pressing E in the grub selection, adding “emergency” to the linux line and pressing F10.
- Try to do an upgrade from a live USB. You’ll need to create a pendrive with a live iso of the same distro you’re using.
- If you can’t upgrade because it doesn’t recognize the linux, you can do a
zypper dupfrom the live pendrive. I recently did that, you can follow the steps in this post, but do the version mounting the proc already.
Hi, what are your thoughts about attempting to regenerate init? By passing:
# dracut --regenerate-all --force
It doesn’t hurt to try. I’d backup the originals first, then regenerate.
Thanks Ciello for the guidance. I have opted for option 2 and tried to upgrade with an USB. The upgrade is finished and am still stuck at CLI. I could login as localhost with root password. Not sure how to proceed further from here. Is KDE plasma having issues?
Somehow - it doesn’t recognize my user as well. It was before. How do I check my data and take the back up at least? I am worried sick on this.
If I start startx - i could open the GUI but don’t see any of my data in Documents.
If I skip to give the root password, it started “Starting default.target” and says “You are in emergency mode” and asks for root password again.
Surprisingly, the old root password is still working even though user doesn’t exist.
Hi, what are your thoughts about chroot on this situation? How to Chroot in Rescue Mode | Support | SUSE
May need corrective action , pass > update-bootloader --reinit
Instead of dracutas per guide suggestion.
Hi Panorain, Thanks fro your response. I tried the same and still getting into emergency mode.
Are sysroot and the partitions containing your system mounting? Also, what journalctl says?
And if you’re concerned about your user data make a backup while you still have access to it. You can either do it with using cp and the directories paths in the CLI or mount the drive from the Live USB and use the GUI to copy it.
After exploring the file system, I could find the folder with my username and see all the data available. I am just copying the same and will go for clean installation after the back up.
Thanks for your time. It is fine as of now I guess.
Finally did a fresh/clean installation and all good now. Thank you all for your invaluable guidance.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.