On 1/10/26 10:47 AM, Barry Scott wrote:
On 10 Jan 2026, at 17:49, Paolo Galtieri <[email protected]> wrote:
I have tried to upgrade my F42 system to F43 with no success. I have
downloaded all the F43 files it just never installs them. Here is
what I have tried:
Are you following these instructions? https://docs.fedoraproject.org/en-
US/quick-docs/upgrading-fedora-offline/ <https://docs.fedoraproject.org/
en-US/quick-docs/upgrading-fedora-offline/>
sudo dnf upgrade --refresh
sudo dnf system-upgrade download --releasever=43
sudo dnf5 offline reboot
This just boots back to F42.
Please use dnf and not a mix of dnf and dnf5.
There is a command to view the logs of the upgrade that you can use to
look for problems.
sudo dnf system-upgrade log
Then to see the last log add its number from the list.
sudo dnf system-upgrade log --number=XXX
sudo dnf upgrade --refresh
sudo dnf autoremove
sudo reboot
As does this
sudo dnf clean all
sudo dnf system-upgrade reboot
As does this.
When it boots up I get the following message:
In emergency mode. After logging in, type "journalctl -xb" to view
logs, "systemctl reboot" to reboot, or exit.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press enter to continue.
You need to debug why this is happening.
Did you do
sudo journalctl -xb
to find the reason the system is in trouble?
What did you find?
Barry
When I press enter the system boots up, but it fails to start
vmware.service, ipmi.service, mariadb.service and dhcpd.service.
After I login and retry to start dhcpd.service it starts up, but the
others all fail.
sudo systemctl restart mariadb.service
Job for mariadb.service failed because a fatal signal was delivered
causing the control process to dump core.
See "systemctl status mariadb.service" and "journalctl -xeu
mariadb.service" for details.
Job for ipmi.service failed because the control process exited with
error code.
See "systemctl status ipmi.service" and "journalctl -xeu ipmi.service"
for details.
[pgaltieri@terrapin ~]$ systemctl status ipmi.service
× ipmi.service - IPMI Driver
Loaded: loaded (/usr/lib/systemd/system/ipmi.service; enabled;
preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Sat 2026-01-10 09:30:26
PST; 12s ago
Invocation: 12a78a847faa48499de851a13e2938c6
Process: 38601 ExecStart=/usr/libexec/openipmi-helper start
(code=exited, status=1/FAILURE)
Main PID: 38601 (code=exited, status=1/FAILURE)
Mem peak: 3.1M
CPU: 54ms
Jan 10 09:30:26 terrapin.homenet192-168-10.com systemd[1]: Starting
ipmi.service - IPMI Driver...
Jan 10 09:30:26 terrapin.homenet192-168-10.com openipmi-helper[38601]:
Startup failed.
Jan 10 09:30:26 terrapin.homenet192-168-10.com systemd[1]:
ipmi.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 09:30:26 terrapin.homenet192-168-10.com systemd[1]:
ipmi.service: Failed with result 'exit-code'.
Jan 10 09:30:26 terrapin.homenet192-168-10.com systemd[1]: Failed to
start ipmi.service - IPMI Driver.
sudo systemctl restart vmware.service
Job for vmware.service failed because the control process exited with
error code.
See "systemctl status vmware.service" and "journalctl -xeu
vmware.service" for details.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An ExecStart= process belonging to unit vmware.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit vmware.service has entered the 'failed' state with result
'exit-code'.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 1364 (vmware-authdlau) remains running
after unit stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 57042 (vmware-authdlau) remains running
after unit stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 57043 (logger) remains running after unit
stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]: Failed to
start vmware.service - SYSV: This service starts and stops VMware
services.
Subject: A start job for unit vmware.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit vmware.service has finished with a failure.
The job identifier is 74825 and the job result is failed.
Notice that in these messages it never says what the exit code is, it
just says 'exit-code'
I have upgraded my system from F39 -> F40 -> F41 -> F42 with no
issues. This is the first time I've had an upgrade fail with no error
messages.
So what do I need to do to upgrade to F43 from F42?
Paolo
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/
code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/
[email protected]
Do not reply to spam, report it: https://pagure.io/fedora-
infrastructure/new_issue
I followed the instructions listed here
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
sudo dnf system-upgrade log
shows the following
The following boots appear to contain offline transaction logs:
1 / 631b02825fc24dfdaf4bc0686e47e6f0: 2025-04-15 22:57:07 41→42
This is dated April 15 and is the upgrade from F41 to F42.
journalctl -xeu mariadb.service
An ExecStart= process belonging to unit mariadb.service has exited.
The process' exit code is 'dumped' and its exit status is 6.
Jan 11 08:46:15 terrapin.homenet192-168-10.com systemd[1]:
mariadb.service: Failed with result 'core-dump'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit mariadb.service has entered the 'failed' state with result
'core-dump'.
Jan 11 08:46:15 terrapin.homenet192-168-10.com systemd[1]: Failed to
start mariadb.service - MariaDB 10.11 database server.
Subject: A start job for unit mariadb.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit mariadb.service has finished with a failure.
The job identifier is 2882859 and the job result is failed.
Jan 11 08:46:15 terrapin.homenet192-168-10.com systemd[1]:
mariadb.service: Consumed 268ms CPU time, 81.6M memory peak.
Subject: Resources consumed by unit runtime
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit mariadb.service completed and consumed the indicated resources.
journalctl -xeu vmware.service
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An ExecStart= process belonging to unit vmware.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit vmware.service has entered the 'failed' state with result
'exit-code'.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 1364 (vmware-authdlau) remains running
after unit stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 57042 (vmware-authdlau) remains running
after unit stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]:
vmware.service: Unit process 57043 (logger) remains running after unit
stopped.
Jan 10 09:41:58 terrapin.homenet192-168-10.com systemd[1]: Failed to
start vmware.service - SYSV: This service starts and stops VMware services.
Subject: A start job for unit vmware.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit vmware.service has finished with a failure.
The job identifier is 74825 and the job result is failed.
Doesn't really say much.
Paolo
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
