How to Fix the Syneto OS5 to Syneto OS6 Update Failures

Written By Christian Castagna (Super Administrator)

Updated at April 21st, 2026

→ Applies to: SynetoOS 6.x

IMPORTANT
The following steps should only be performed if the upgrade from SynetoOS 5 to SynetoOS 6 did not complete successfully.


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. Check the state of SynetoOS

If the SynetoOS web interface is reachable, proceed with the steps described in paragraph “Reachable web interface”.
If the SynetoOS web interface is not reachable, proceed with the steps described in paragraph “Unreachable web interface”.


Web Interface is Reachable


Step 1. Run syneto-edge-update

syneto-edge-update

 

Step 2. Check real-time logs updates

journalctl -fu software-upgrade


Web Interface is Not Reachable


Step 1. Identify the failed step(s) from the logs

cat /tmp/software_upgrade_progress.log

EXAMPLE OUTPUT

51.82|Upgrading system packages ...|END: './20-dnf-upgrade.sh release-6.0' returned 0
51.82|Performing post-upgrade configuration ...|START: ./30-post-upgrade-config.sh
51.82|Performing post-upgrade configuration ...|warning: Converting database from bdb_ro to sqlite backend
51.82|Performing post-upgrade configuration ...|warning: Converting database from bdb_ro to sqlite backend
51.82|Performing post-upgrade configuration ...|7 files removed
51.9205|Performing post-upgrade configuration ...|Removed \"/etc/systemd/system/auditd.service\".
51.9205|Performing post-upgrade configuration ...|Removed \"/etc/systemd/system/auditd.service\".
52.021|Performing post-upgrade configuration ...|syneto 0.0 B/s | 0 B 00:00
52.021|Performing post-upgrade configuration ...|Errors during downloading metadata for repository 'syneto':
52.021|Performing post-upgrade configuration ...|- Curl error (7): Couldn't connect to server for https://yum.syneto.eu/LX/syneto-appliance/rc/release-6.0/latest/repodata/repomd.xml [Failed to connect to yum.syneto.eu port 443: Connection refused]
52.021|Performing post-upgrade configuration ...|Error: Failed to download metadata for repo 'syneto': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
52.021|Performing post-upgrade configuration ...|
52.021|Performing post-upgrade configuration ...|real	0m4.940s
52.021|Performing post-upgrade configuration ...|user	0m1.567s
52.021|Performing post-upgrade configuration ...|sys	0m0.940s
52.021|Performing post-upgrade configuration ...|END: './30-post-upgrade-config.sh' returned 1
52.021|Operation failed|Command failed with exit status 1.


The item highlighted in yellow (./30-post-upgrade-config.sh) indicates the script that returned the error (there may be more than one script that returns an error). In Step 3, you will need to run all the scripts that – according to the logs – returned the message Command failed with exit status 1.

 

Step 2.  Move to os5_os6 folder

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

EXAMPLE OUTPUT

[root@syneto-os-56d8a4af os5_os6]# ls -al
total 1132
drwxr-xr-x   2 root root    4096 Aug  8 12:00 .
drwxr-xr-x. 11 root root     185 Aug  8 11:27 ..
lrwxrwxrwx   1 root root      36 May 19 17:29 05-clean-pulumi-backups.sh -> ../common/05-clean-pulumi-backups.sh
lrwxrwxrwx   1 root root      41 May 19 17:29 07-prepare-snapshot-index.sh -> ../data-migration/prepare-rps-metadata.sh
-rwxr-xr-x   1 root root     248 May 19 17:29 10-prepare-upgrade.sh
lrwxrwxrwx   1 root root      27 May 19 17:29 20-dnf-upgrade.sh -> ../common/20-dnf-upgrade.sh
-rwxr-xr-x   1 root root     970 May 19 17:29 30-post-upgrade-config.sh
lrwxrwxrwx   1 root root      39 May 19 17:29 35-migrate-rps-to-zfs.sh -> ../data-migration/migrate-rps-to-zfs.sh
-rwxr-xr-x   1 root root     804 May 19 17:29 40-prepare-cluster-recreate.sh
lrwxrwxrwx   1 root root      35 May 19 17:29 50-update-edge-cluster.sh -> ../common/50-update-edge-cluster.sh
-rwxr-xr-x   1 root root     119 May 19 17:29 60-restore-edge-cluster-databases.sh
-rwxr-xr-x   1 root root     522 Jun 12 16:57 70-configure-post-setup-routing.sh
lrwxrwxrwx   1 root root      44 May 19 17:29 90-invalidate-cache-post-update.sh -> ../common/90-invalidate-cache-post-update.sh

AVAILABLE SCRIPTS

Script Description
05-clean-pulumi-backups.sh Clean Pulumi backups
07-prepare-snapshot-index.sh Prepare snapshot index
10-prepare-upgrade.sh Prepare upgrade environment
20-dnf-upgrade.sh DNF system package upgrade
30-post-upgrade-config.sh Post-upgrade configuration
35-migrate-rps-to-zfs.sh Migrate RPS to ZFS
40-prepare-cluster-recreate.sh Prepare cluster recreation
50-update-edge-cluster.sh Update Edge cluster
60-restore-edge-cluster-databases.sh Restore Edge cluster databases
70-configure-post-setup-routing.sh Configure post-setup routing
90-invalidate-cache-post-update.sh Invalidate cache post-update

 

Step 3. Re-run the failed script(s) manually (replace <script_name> with the script name)

sh <script_name>.sh

EXAMPLE

sh 30-post-upgrade-config.sh
sh 20-dnf-upgrade.sh release-6.0

Some scripts require a release argument.

 

Step 4. Mark the upgrade as complete

echo "yes" > /var/storage/software_upgrade_acknowledged.flag

Run this command only after all scripts through step have completed successfully. 
Skipping it will leave the upgrade in an unfinished state at the system level.