Ask Your Question
1

Problem reboot to upgrade from 26 to 27

asked 2017-11-16 14:18:07 -0500

btaillefer gravatar image

updated 2017-11-17 11:27:04 -0500

Hi everyone,

I followed every steps described on the fedora magazine website to upgrade my Fedora Spins Cinnamon from 26 to 27, and all 3 command to get upgrades went okay (one downloaded like 1k upgrades, around 1.6G so I assume this is okay).

When I use the command to reboot and do upgrade, it goes to where the upgrade should start, just after the fedora build to choose (here 26 as it's not installed yet). Then I got my normal cpu over temperature (never caused problems, even to install 26 one week ago), and I barely see a message popping then it reboot again. From there, back to 26 like everyday.

What can I do to troubleshoot this ?

Edit - Using journalctl -b -1

systemd[1]: Starting System Upgrade using DNF...
dnf[711]: Erreur : Échec de la synchronisation du cache pour le dépôt « updates »
systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start System Upgrade using DNF.
systemd[1]: dnf-system-upgrade.service: Unit entered failed state.
kernel: audit: type=1130 audit(1510938551.521:81): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
systemd[1]: dnf-system-upgrade.service: Failed with result 'exit-code'.
systemd[1]: Rebooting: service failed
edit retag flag offensive close merge delete

Comments

1

Can you choose another kernel or is it the same with everyone of them?

kaestchen gravatar imagekaestchen ( 2017-11-17 01:21:39 -0500 )edit
1

Run as root/admin journalctl -b -1 where -1 means previous boot and -2 would mean one before it and etc. You can use this command to view system log from boot with failed upgrade attempt.

ozeszty gravatar imageozeszty ( 2017-11-17 01:54:04 -0500 )edit

Thanks for your answers, both of them were helpful in a way. By trying to choose another kernel (have something like fedora 4.11.13, 4.11.12 and 4.11.8), I did have some graphical result by starting the fedora 4.x.8, 3 dots appeared on a grey background, then reboot, but this almost the same log, and error for the same thing.

btaillefer gravatar imagebtaillefer ( 2017-11-17 11:38:46 -0500 )edit

I have exactly the same problem on my laptop. https://ask.fedoraproject.org/en/ques...

Martin Ueding gravatar imageMartin Ueding ( 2017-11-18 04:19:08 -0500 )edit
1

I have filed a bug for this.

Martin Ueding gravatar imageMartin Ueding ( 2017-11-18 04:30:25 -0500 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2017-12-07 03:52:12 -0500

ceres2009 gravatar image

Hi, finally for me the comment 50 from Martin Uding's Bug Report solved the issue. https://bugzilla.redhat.com/show_bug.cgi?id=1492036#c50

edit flag offensive delete link more
0

answered 2017-11-20 13:38:13 -0500

btaillefer gravatar image

updated 2017-11-20 15:22:27 -0500

What I did :

sudo dnf repolist
sudo dnf config-manager --set-disabled [repo name without stars]
sudo dnf repolist      /!\(check if only star repo)/!\
sudo dnf update

Then follow what's described in fedora magazine article for upgrading from 26 to 27.

Worked like a charm.

edit flag offensive delete link more

Comments

didn't work for me, sadly. Still the OPs behaviour.

ceres2009 gravatar imageceres2009 ( 2017-11-27 02:10:04 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2017-11-16 14:18:07 -0500

Seen: 1,926 times

Last updated: Dec 07 '17