System update failed. Directories missing.

I ran system update, it's failed Running systemd-sysusers... done Running pre scripts... done Running post scripts... done error: Running %post for akmod-vhba: bwrap(/bin/sh): Child process exited with code 1; run journalctl -t 'rpm-ostree(akmod-vhba.post)' for more information System update failed: 0: Command failed: /usr/bin/rpm-ostree upgrade 1: /usr/bin/rpm-ostree failed: exit status: 1 Location: src/steps/os/linux.rs:228 I ran the command and received this output: Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6409]: Building /usr/src/akmods/vhba-kmod-20250329-1.fc43.> Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6418]: ERROR: Files needed for building modules against ke> Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6418]: 6.17.4-300.fc43.x86_64 could not be found as the f> Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6418]: directories are missing: Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6418]: /usr/src/kernels/6.17.4-300.fc43.x86_64/ Oct 29 14:36:13 bazzite rpm-ostree(akmod-vhba.post)[6418]: /usr/lib/modules/6.17.4-300.fc43.x86_64/build/ I've checked the paths don't exist but this does. /usr/lib/modules/6.16.4-116.bazzite.fc42.x86_64/build/ /usr/src/kernels/6.16.4-116.bazzite.fc42.x86_64/ Any Idea how I can sort this?
Solution:
Ran 'sudo rpm-ostree reset' again, it's working now. Heres the 'rpm-ostree status' output. `State: idle Deployments:...
Jump to solution
1 Reply
Solution
Wolf
Wolf3w ago
Ran 'sudo rpm-ostree reset' again, it's working now. Heres the 'rpm-ostree status' output. State: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable Digest: sha256:69cbc671b6f3c1c5a1711f5140b5034e0ef3d1df04e5f6c04c37518abce9126b Version: 43.20251029 (2025-10-29T18:51:11Z) ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable Digest: sha256:5d86b5f6db5361d4c74f4ed2c9503a694502d91e61f872ceb3c93e48503f2401 Version: 42.20251019 (2025-10-19T16:29:32Z) If it happens to anyone else it may be worth telling them to run 'sudo rpm-ostree reset' again.

Did you find this page helpful?