→ Applies to: SynetoOS 6.x

Symptom

A SynetoOS 6 update stops at 66% on the step Synchronizing EFI partition and ends with the status Update requires assistance.

The script 31-sync-efi.sh copies the active EFI System Partition (ESP) to the second boot disk. Before copying, it checks that the firmware boot order contains an entry pointing to \EFI\rocky\shimx64.efi. If it finds none, it treats the active ESP as not bootable and stops, so that it does not replicate a possibly broken ESP to the other disk.

IMPORTANT
Do not reboot the appliance until you complete this procedure, including Step 6.

In /tmp/software_upgrade_progress.log, the script 31-sync-efi.sh returns exit status 1 with this error:

EXAMPLE OUTPUT

2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|START: ./31-sync-efi.sh
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|ERROR: no firmware boot entry in the boot order starts \\EFI\\rocky\\shimx64.efi
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|[EFI-SYNC] ERROR: The active ESP is not bootable; not copying it to the other disk.
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|real   0m0.045s
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|user   0m0.010s
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|sys    0m0.036s
2026-10-07 13:46:47|66.27|Synchronizing EFI partition...|END: './31-sync-efi.sh' returned 1
2026-10-07 13:46:47|66.27|Operation failed|Command failed with exit status 1.
2026-10-07 13:46:47|99|Update requires assistance|Update process failed.

Solution

Complete the update manually by running the remaining update scripts, skipping scripts 31 and 45.

Step 1. Connect to SynetoOS appliance via SSH as admin

ssh admin@<your_ip_address_or_hostname>

Step 2. Get root privileges

sudo su -

Step 3. Confirm where the update stopped

tail -n 20 /tmp/software_upgrade_progress.log

NOTE
Check that the last script started is 31-sync-efi.sh and that it returned 1.

IMPORTANT
The scripts before 31 (05 to 30) have already run. Do not run them again.

Step 4. Go to the update scripts folder and list its contents

cd /usr/share/software-upgrade/scripts/os6_os6_patch/

ls

EXAMPLE OUTPUT

05-clean-pulumi-backups.sh     25-reconcile-services.sh   50-update-edge-cluster.sh
13-dnf-downloadonly.sh         30-post-upgrade-config.sh  70-configure-post-setup-routing.sh
19-clean-boot.sh               31-sync-efi.sh             90-verify-post-state.sh
20-dnf-upgrade.sh              35-zpool-upgrade.sh        debugdata
22-prune-unwanted-packages.sh  45-verify-boot-chain.sh    debugdata-autoremove

Step 5. Run the remaining scripts in order

./35-zpool-upgrade.sh

./50-update-edge-cluster.sh

./70-configure-post-setup-routing.sh

./90-verify-post-state.sh

IMPORTANT

• Run each script one at a time and wait for it to finish before starting the next.
• Skip 31-sync-efi.sh and 45-verify-boot-chain.sh. Both depend on the firmware boot entry and will fail again for the same reason.
• If any script ends with an error, stop and contact Syneto Support. Do not run the next script.

NOTE
The update is complete when 90-verify-post-state.sh finishes without errors.

Step 6. Check the firmware boot entries

efibootmgr -v

NOTE
Check that BootOrder includes an entry whose path ends in \EFI\rocky\shimx64.efi.

IMPORTANT
Because scripts 31 and 45 were skipped, the EFI partition was not copied to the second boot disk. 
If no boot entry points to \EFI\rocky\shimx64.efi, contact Syneto Support before the next reboot.