Failed to finalize previous deployment

Experiencing a similar issue on my ASUS Laptop to the one described by another user in February. https://discord.com/channels/1072614816579063828/1343354081871401020/1343354081871401020 Attempting to update or rebase does not work, and gives this error in rpm-ostree status.
Warning: failed to finalize previous deployment
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
check `journalctl -b -1 -u ostree-finalize-staged.service`
Warning: failed to finalize previous deployment
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
check `journalctl -b -1 -u ostree-finalize-staged.service`
1 Reply
Archaic
ArchaicOP3d ago
Running the journalctl command above gives
Apr 14 15:57:21 Laptop systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 14 15:59:26 Laptop systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Apr 14 15:59:26 Laptop ostree[9954]: Finalizing staged deployment
Apr 14 15:59:27 Laptop ostree[9954]: Copying /etc changes: 22 modified, 2 removed, 119 added
Apr 14 15:59:27 Laptop ostree[9954]: Copying /etc changes: 22 modified, 2 removed, 119 added
Apr 14 15:59:27 Laptop ostree[9954]: Refreshing SELinux policy
Apr 14 15:59:28 Laptop ostree[9954]: Refreshed SELinux policy in 868 ms
Apr 14 15:59:28 Laptop ostree[9954]: Finalized deployment
Apr 14 15:59:28 Laptop ostree[9954]: bootfs is sufficient for calculated new size: 167.5 MB
Apr 14 15:59:28 Laptop ostree[9974]: /usr/sbin/grub2-probe: error: failed to get canonical path of `composefs'.
Apr 14 15:59:28 Laptop ostree[9954]: error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
Apr 14 15:59:28 Laptop systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Consumed 1.838s CPU time, 438.8M memory peak.
Apr 14 15:57:21 Laptop systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 14 15:59:26 Laptop systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Apr 14 15:59:26 Laptop ostree[9954]: Finalizing staged deployment
Apr 14 15:59:27 Laptop ostree[9954]: Copying /etc changes: 22 modified, 2 removed, 119 added
Apr 14 15:59:27 Laptop ostree[9954]: Copying /etc changes: 22 modified, 2 removed, 119 added
Apr 14 15:59:27 Laptop ostree[9954]: Refreshing SELinux policy
Apr 14 15:59:28 Laptop ostree[9954]: Refreshed SELinux policy in 868 ms
Apr 14 15:59:28 Laptop ostree[9954]: Finalized deployment
Apr 14 15:59:28 Laptop ostree[9954]: bootfs is sufficient for calculated new size: 167.5 MB
Apr 14 15:59:28 Laptop ostree[9974]: /usr/sbin/grub2-probe: error: failed to get canonical path of `composefs'.
Apr 14 15:59:28 Laptop ostree[9954]: error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
Apr 14 15:59:28 Laptop systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 14 15:59:28 Laptop systemd[1]: ostree-finalize-staged.service: Consumed 1.838s CPU time, 438.8M memory peak.
ujust regenerate-grub gives the following:
/usr/sbin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1
/usr/sbin/grub2-probe: error: failed to get canonical path of `composefs'.
error: Recipe `regenerate-grub` failed with exit code 1
I've attempted to use Bazzite Rollback Helper to rebase to the latest bazzite-asus:stable image, however while that seems to run fine, after completing the reboot and checking rpm-ostree status I can see the same error is there, and nothing's actually changed in the backend.

Did you find this page helpful?