How to Solve "Mount Image Repository Failed" in Hyperion

Written By Sebastian Sime (Super Administrator)

Updated at October 5th, 2026

Table of Contents

→ Applies to: SynetoOS 6.x and above

IMPORTANT
Use this procedure when the Image Repository storage pool still points to an old volume path (for example flash/syn-volumes/<old_volume_uuid>) and must be redefined with the new name, UUID and path.

 

Symptom

Error “Mount image repository failed at step 2 (Create virtual volume): storage volume with mountpoint ‘/flash/syn-volumes/<old_volume_uuid>’ not found after refresh..” appears.

IMPORTANT
The ID in this path is the <old_volume_uuid> used in Step 3.

 

Solution

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. Identify the storage pool definition that uses the old volume (replace <old_volume_uuid> with the correct information)

grep -rl <old_volume_uuid> /etc/

EXAMPLE

[root@syneto-os]# grep -rl 1af0ea0e-4db4-4f43-9bcf-f00d09608981 /etc/
/etc/libvirt/storage/ImageRepository-syneto-os.xml

NOTE
The file name without .xml is the pool name (in this example ImageRepository-syneto-os).

 

Step 4. Back up the storage pool definition (replace <pool_name> with the pool name from Step 3)

virsh pool-dumpxml --pool <pool_name> > /tmp/pool_backup.xml

EXAMPLE

[root@syneto-os]# virsh pool-dumpxml --pool ImageRepository-syneto-os > /tmp/pool_backup.xml

 

Step 5. List the volumes

zfs list | grep syn-volumes

 

Step 6. Look for the volume that contains the ISO files (replace <zpool_name> with the pool name shown in the previous output)

ls -lha /<zpool_name>/syn-volumes/*

EXAMPLE OUTPUT

/flash/syn-volumes/be22185f-8d44-48f6-bcc9-9b545c62bfa9
total 26K
drwxr-xr-x  3 root root  3 Oct 16  2025 .
drwxr-xr-x 68 root root 68 Aug 20 16:20 ..
drwxr-xr-x  2 root root  5 Aug 22 15:15 ISO

The volume that contains the ISO folder is the new Image Repository volume. Its full path is the <new_volume_path> and its ID is the <new_uuid> used in Step 7.

 

Step 7. Edit the /tmp/pool_backup.xml file

vi /tmp/pool_backup.xml

IMPORTANT
Change only the following lines (replace <new_pool_name>, <new_uuid> and <new_volume_path> with the correct information)

<name><new_pool_name></name>
<uuid><new_uuid></uuid>
...
<target>
  <path><new_volume_path></path>
</target>

EXAMPLE

<name>ImageRepository</name>
<uuid>be22185f-8d44-48f6-bcc9-9b545c62bfa9</uuid>
...
<target>
  <path>/flash/syn-volumes/be22185f-8d44-48f6-bcc9-9b545c62bfa9</path>
</target>

Save and EXIT

:wq

 

Step 8. Remove the old storage pool definition (replace <pool_name> with the pool name from Step 3)

virsh pool-undefine --pool <pool_name>

EXAMPLE OUTPUT

Pool ImageRepository-syneto-os has been undefined

NOTE
This removes only the libvirt definition of the pool. The files in the volume are not deleted.

 

Step 9. Define the new storage pool from the backup file

virsh pool-define --file /tmp/pool_backup.xml

 

Step 10. Start the new storage pool (replace <new_pool_name> with the correct information)

virsh pool-start --pool <new_pool_name>

 

Step 11. Enable autostart for the new storage pool (replace <new_pool_name> with the correct information)

virsh pool-autostart --pool <new_pool_name>

 

Step 12. Restart the syneto-giove service

systemctl restart syneto-giove.service

 

Step 13. Check the new storage pool

virsh pool-list --all

EXAMPLE OUTPUT

 Name              State    Autostart
--------------------------------------
 ImageRepository   active   yes

NOTE
The new pool must show as active with autostart yes.