Hide Forgot
Description of problem: After running `rpm-ostree deploy 32.20200702.0` on a MacBook Pro (with dual EFI partitions), Fedora Silverblue fails to restart. Attempt to use GRUB to rollback to 32.20200701.0 fails with following message: ``` APFSSTART:1584: Mounting with apfs_efi_osx-1412.101.1 efi_fusion_pairing:686: Container <sha> efi_fusion_pairing:691: fusion uuid: <zeros> efi_container_create:990: Volume attached is internal nx_kernel_mount:1385: : checkpoint search: largest xid 5730425, best xid 5730425 @ 193 er_state_obj_get_for_recovery:4639: No ER state object for volume Preboot - rolling is not happening, nothing to recover. er_state_obj_get_for_recovery:4639: No ER state object for volume Preboot - rolling is not happening, nothing to recover. System BootOrder not found. Initializing defaults. ``` Version-Release number of selected component (if applicable): 32.20200702.0 How reproducible: Always Steps to Reproduce: 1. Partition a MacBook Pro to run Silverblue with version 32.20200701.0. Mine is a mid-2015 15" Retina model. 2. Run rpm-ostree deploy 32.20200702.0 3. Reboot Actual results: Computer does not reboot. Booting to GRUB displays the message above - changing the kernel and then running rpm-ostree rollback is not possible. Expected results: Upgrade is successful. Barring that, GRUB menu allows me to boot to a prior kernel version and run a rollback. Additional info:
Note that the only way I could recover from this situation was to reinstall via a live-boot USB, pin my verison to 32.20200701.0, and restore my data from a backup.
Might be unrelated, though an issue with the same final error message showed up yesterday too in Fedora CoreOS: https://github.com/coreos/fedora-coreos-tracker/issues/563.
I think this might be corruption of the ESP. rpm-ostree doesn't touch the ESP (see https://github.com/coreos/bootupd ) but it is mounted by default and I think we've seen reports that simply mounting it can corrupt things in some cases.
On a whim I thought, "perhaps the two EFI partitions could be an issue" - so I went full steam ahead and wiped it out, installed Silverblue 32 from live USB, then upgraded to the latest in the fedora:32 branch. The initial APFSTART message disappears - after booting to GRUB all I see is "System BootOrder not found. Initializing defaults."