Good morning,
I recently updated my system with the normal system update tool, and now I am unable to login or boot to the xserver.
It appears to me it has to do with network manager, as per the screen shots, but I have no idea clue to what extent that is true.
For what its worth, this is the update with kernel 6.10.8
Thanks for looking/advising,
SCP
Please check again, this thread is tagged Leap 16 and the current kernel is 6.12.0-160000.6 for Leap 16.
This is my kernel directory:
If this is a different version than the absolute latest kernel, that’s fine. It could be kernel 1.0.8. This is what I have from the latest update that gave me the boot loop. Said again, it is leap, it is leap 16, and it is with the latest update.
Also, as an addition, all of the supposed missing files do actually exist.
If I need to tag this as something OTHER THAN Leap 16, please let me know what I have to adjust this to.
You are apparently on Leap 15.6 (despite the tag reading Leap-16) and the current kernel for Leap 15.6 is kernel-default-6.4.0-150600.23.78.1.
So I wonder where you found the faulty kernel that appears to be from a non-official repo for Leap 15.5: uninstall it and try again.
Also, showing your repo list by:
zypper lr -d
might help us understand what happened.
Please use pre-formatted text (use the </> button above the editing area) including the command line, the result and the trailing prompt.
Please be aware that posting images instead of computer output can turn down many willing to help.
I cannot boot into the system, how can do enter the command and copy the output?
At the boot screen you should be able to choose one of the other kernels still installed on your system (in “Advanced options for Leap…”, scroll down if you don’t see them)
All three kernels I have show the same infinite loop problem. One of the updates must have altered how the network stack is initialized, in my best (uneducated) guess.
Apparently you logged in in a virtual terminal in your last photo…
So select a previous kernel, press “E” for edit and add the number 3 at the end of the line beginning with “linux”, then F10 to boot.
Login as root, then you should be able to perform some maintenance on the system, for instance disabling any non-essential repo and performing a “zypper up” again.
The network message is likely a red herring. You screwed up your system with additional repositories (the develeopment kernel for Leap 15.5 on your Leap 15.6 is a sign).
Please show a picture of your screen from the requested output zypper lr -d
Somehow some files in /usr are missing (or for other reasons cannot be accessed). Boot live medium, do filesystem check for the root partition. What filesystem is used for root?
what I have for the grub boot command:
linux /boot/x86_64/loader/linux splash=silent systemboot=1
I added a 3 at the end of that line as such:
| linux /boot/x86_64/loader/linux splash=silent systemboot=1 3
It still is unbootable in the same manner.
They are indeed there, I have checked. It is the XFS file system.
Who are “they” and what did you check?
“they” being the files which are referenced in the first two screen shots. They exist in the locations that the kernel message says they do not exist in. As far as I can tell they are normal files, and if necessary I can put them on pastebin
To be clear: that was trying to boot from a live usb that allows me to boot from the hard drive.
From my normal grub, I have this:
linux /boot/vmliuz-6.10.8-…root=UUID=… splash=silent preempt=full quiet security=apparmor mitigations=auto
and I added the 3 to the end of it after “auto” with the … just being truncated since I have to type all of this out.
When I go THAT direction, through my normal grub menu, I wind up with
Failed to start MTP client/server
Failed to start Postfix Mail Transport Agent
[base-manager] couldn’t check support for device '/sys-devices/pc1000:00/0000:00:14.3 not supported by any plugin
Those file are shell scripts and another message that you overlooked is “no shell” for the user. Apparently, shell is missing. I do not know what shell this user is using, but some scripts use /bin/sh, some /bin/bash. /bin/sh is normally a link to the bash.
@arvidjaar
Sorry, I don’t quite understand. Is this your train of thought or is this that I need to do something? I can go talk back and forth without much issue and I am not a complete linux idiot, but I’m not an aristocrat either.
Thanks for clarifying
You need to check whether /bin/bash and/or /bin/sh exist.
Try to find one of the former kernels, for instance 6.4.0-150600.23.70 and do the same
(the 6.10.8 is guaranteed not to work)