Upgraded to Fedora 29 from 28, now system system stuck at startup

asked 2019-04-02 23:49:24 -0600

ayu_ssh gravatar image

I followed the step as in https://fedoramagazine.org/upgrading-....

First thing: the grub menu doesnt show Fedora 29 after reboot. It shows Fedora 28 only with a new kernel version which came post a "dnf update".

Now when I start the system, there are a lots of failed statuses: Failed to start RealtimeKit Scheduling Policu Services Failed to start Accounts Services Failed to start firewalld - dynamic firewall daemon Failed to start Modem Manager Failed to start Avahi nDNS/DNS-SD stack Failed to start Virtual Machine Failed to start Disk Manager Failed to start NTP client/server and finally stuck at : "Started D-Bus System Message Bus".

I have to go into emergency mode to log into my account. Also, post login, my account password doesnt work for any command(eg: sudo dnf install xxx throws Sorry, try again).

I am able to gain login as root user to gain root access. All this started after I did a dnf update.

[root@localhost ~]# dnf history
ID     | Command line             | Date and time    | Action(s)      | Altered

-------------------------------------------------------------------------------
   100 | system-upgrade upgrade   | 2019-04-03 09:10 | D, E, I, O, U  | 2673 **
    99 | remove sssd              | 2019-04-02 21:58 | Erase          |   21   
    98 | system-upgrade upgrade   | 2019-04-02 20:09 | D, E, I, O, U  | 2677 *<
    97 | upgrade                  | 2019-04-02 18:53 | Update         |    1 > 
    96 | update                   | 2019-04-02 09:22 | E, I, O, U     | 1048 E<

Can someone please guide me on the steps to recover my system. Thanks in advance

edit retag flag offensive close merge delete

Comments

Run

 systemctl list-unit-files dbus\* |grep -v org
systemctl --global list-unit-files dbus\* |grep -v org

and show the results

villykruse gravatar imagevillykruse ( 2019-04-03 03:37:45 -0600 )edit

if you had the same update luck a a host in Berlin last year, the d-bus components do not match and thats why it's not starting. Problem is, you can't use rpm if dbus is down.

Solution: Use a livedisk, boot from usb. open terminal. mount your systems hddisk to /mnt/ . chroot /mnt/ . dnf reinstall d-bus* .

You do come from booted system, so dbus is up and running and no program inside the chroot can complain about it. It is possible, that you need to link a dbus socket into the chroot, but try it as above first.

rdtcustomercare gravatar imagerdtcustomercare ( 2019-04-03 16:30:48 -0600 )edit

btw: when you have entered "chroot /mnt" you shoud execute "passwd" first, to set a root password and UNLOCK the root account that way. makes things easier in your emergency shell next time.

rdtcustomercare gravatar imagerdtcustomercare ( 2019-04-03 16:33:45 -0600 )edit