System completely broken after

English Install/Boot/Login
1

I updated my tumbleweed using: zypper dup --no-allow-vendor-change

It proceeded and finished.

During the execution i noticed a lot of Pearl related errors referring to .pm modules and later some rpms showed sourcecode during installation. Also lot of services where stopped and refused to restart.

Then after installation i rebooted the machine.

Now it can’t start the login service and i can’t login.

I started from the rescue dvd and did a chroot to the system.

Then i tried to run zypper again to possibly fix things, but it refuses to run due to a parsing error in zypper.conf.
zypper.conf is totally fine.

journalctl is not having journals from last boots.

Now i have these questions:

-how was it possible to ruin then system? The install proceeded and due to what i suppose to be an error in the pearl installation subsequently ruined a lot of other packages.

-how can i recover? I don’t know which packages are broken and zypper is not working. So how can i recover the system without new installation?

2

Hard to guess. Nothing similar has happened here.

So how can i recover the system without new installation?

Honestly, I recommend a new install. That’s what I would do in your situation.

3

Boot from an working Snapshot and than:

snapper rollback

Boot normal…

4

Well it seems to be reproducible…

When i restore a working older image and update from there, at some point during the update, either at perl packages or systemd packages the system gets destroyed…

5

I tracked it a little further…the problems begin after i install a new glibc 2.25.

After that i get segmentation faults, coredumps, etc. can’t even shutdown system.

6

Hi Connormcl,

I experience the same errors, You have described. Two of my machines are suffering from it, one running in 32 and one in 64 bit.

I have reinstalled earlier versions of tumbleweed and everything works fine, hardware failure is thus excluded.

After upgrade to the latest packages, the login service stops working shortly after being launched.

If I reinstall Tumbleweed from an .iso image, dracut also fails to make the initrd image. I have tried this on a 32 bit system multiple times.

The errors have begun with upgrades to the 4.10.2 kernel.

If You know a solution to the problem, please let me know.

Best wishes,

Tillaromhay.

7

Do you have 32 or 64 bit system?

8

I have both 32 and 64 bit systems, that are broken.

The problem with 32bit system is with the login service, also prohibiting to start the login manager.

If I switch the screens to console login, I get automatically logged out in short time.

The 64bit system stalls already in the boot process at the start of the root service.

The 32 system is broken since an update around Mar.15.

I tried to reinstall with images from Feb.2017 but the system breaks down again, if I pull the actual updates.

Thank You in advance.