Hi,
So a few days ago I installed Tumbleweed on a new NVMe SSD and installed some essential software that I require, nothing major and I had a chance to play around with it, I even turned the system On and Off a few times and everything seemed to work fine with the minor discrepancy of the keyboard not correctly inputting the right keys as always but I of course fixed it.
Now everything at this point was working perfectly I honestly couldn’t fault anything, the CPU and memory usage given that it was a fresh install everything was plush until the next day when Tumbleweed didn’t automatically sign-in which is what I set it to typically do even though I have a password enabled.
I only have two guesses and I really wish someone will help me fix this. My first guess is the next day even though it was a fresh install I think I performed sudo zypper refresh and sudo zypper dup and I honestly remember restarting the system and it still worked fine. My second guess is that I had an older NVMe SSD with Leap 16 installed and I just temporarily removed the new NVMe SSD with the latest Tumbleweed installed so I can migrate my files over to the newer one basically and the process was fine until I removed the older NVMe SSD with Leap 16 installed and put back the newer NVMe SSD with the latest Tumbleweed installed and when I tried to start the system the next day, the system simply didn’t auto sign-in but became stuck on this Grub page.
I should mention I have tried just one thing to fix the issue, thankfully considering it was a recent install, I still had/have Tumbleweed as a bootable on a usb stick, so I plugged that in, pressed F12, booted from the USB and went to More and attempted a Rescue, I’d never really done it before but was hoping something would just work and at the end of it doing its thing it asked for a login and then password and I’m guessing that it’s the one I used to create the system but for whatever reason it doesn’t work. I thought it maybe just a keyboard layout thing but I typed my password on the login bit just to see the password and the layout seems okay.
Could someone please help figure this out and help me log back in? Thanks
Hi,
It could be the NVMe that you removed.
When you boot hit Esc to see in text mode the problem. It could be looking for the NVMe that you removed.
If it is you can correct it in your /etc/fstab.
I tried that, it didn’t do anything other than load the grub again. The first image is what it is stuck on and the second is me unsuccessfully trying to Rescue from a USB stick, I don’t know what the issue is though the login or password.
Hi @hendersj @oldcpu I don’t mean to be rude but if you’re not too busy I’d appreciate your help on this and if it’s a lost cause I made another enquiry over here How to migrate/copy and paste files from Tumbleweed over to Leap?
Thanks
??? So not even the rescue iso boots? It should automatically login to an xfce desktop with a few basic tools, no username nor password.
In extreme cases you should be able at least to switch to a VT (CTRL+ALT+Fn) and login as “root” without password.
I looked at your second image and agree with @OrsoBruno … if you look closely (bottom of image), it’s asking for the “rescue login” , which is NOT the login(s) you’ve defined … it expects the username “root” and no password required.
Once you’ve logged in with “rescue root”, then you can perform drive mounts and do things like a “cp” / etc commands to retrieve files off the drive /etc.
(cropped image)
hey, so it asks for a login and you can see it as you type but then immediately below it, it demands a password, like I’m said previously I’m assuming it means the login name and the password used to create the system but that doesn’t seem to work and I’ve tried numerous times using different methods of typing as well.
I didn’t see the xfce desktop there but I must have missed it trying to rescue it. T’ll look again but honestly when booting from the usb it just looks like the typical bootable to install solution and of course the Rescue but I’ll check again and get back to you.
Wait a moment, a possible misunderstanding here. I write about a Rescue CD like this one: openSUSE-Tumbleweed-Rescue-CD
If you used the “normal” offline install media, that is a different story.
I checked with a NET install media (TW 20260324 for the records), going down the boot menu to “More”, then “Rescue System”.
It lands on a “rescue login:” (no XFCE), “root” logs in without a password.
Of course if you enter anything else than “root” you are asked for a password, but any password yields “Login incorrect” since no other username is defined in the rescue system.
Hi @Numan_Suse , This reads a bit confusingly, but it sure is the problem. If any drive that is listed in /etc/fstab is removed, the system very likely going into rescue mode. That happened to me many times. Just a typo or change of UUID or any other issue the listed drive can’t be found is enough. All the messages are so intimidating but the solution should be rather simple: Just remove the missing drive from /etc/fstab or restore the entry so it fits to the (still existing) drive.
To achieve that you may use an editor in the rescue terminal after logging in as “root”, e.g. vi or vim. I suck at those, so I can’t give much advice. If you have another live system to boot from, you can use that and edit /etc/fstab.
Deleted due to failed trial of editing.
This wouldn’t happen to be an MSI motherboard with an early 2015 UEFI BIOS, would it? On my brother’s A78M-E35, anytime anything unusual happens during shutdown, or if something crashes the DE, or anything else unusual happens, the BIOS forgets how to find the openSUSE entry on the ESP partition (totally missing when running efibootmgr), and to fix it I must chroot in from a rescue boot to run grub2-install to put it back into the BIOS. The symptom when this happens is Grub’s boot menu appears when expected, but then halfway through boot it jumps back into POST, then puts Grub’s boot menu back so it can happen all over again. 
