# Image Datastore does not support transfer mode: ssh

**URL:** <https://forum.opennebula.io/t/image-datastore-does-not-support-transfer-mode-ssh/6975>\
**Category:** Operations\
**Created:** [March 4, 2019, 5:28pm UTC](https://forum.opennebula.io/t/image-datastore-does-not-support-transfer-mode-ssh/6975 "2019-03-04T17:28:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![angriukas](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@angriukas](https://forum.opennebula.io/u/angriukas)\
**Post date:** [March 6, 2019, 6:56am UTC](https://forum.opennebula.io/t/image-datastore-does-not-support-transfer-mode-ssh/6975/4 "2019-03-06T06:56:29Z")

</div>

Have accidentally found the way how to solve that:

1. Create qcow2 storage
2. Change TM\_MAD from qcow2 to shared -\> extra attributes related to ssh will be added.
3. Change TM\_MAD back to qcow2

This sequence will create following attributes:  
CLONE\_TARGET\_SSH = SYSTEM  
DISK\_TYPE\_SSH = FILE  
LN\_TARGET\_SSH = SYSTEM  
TM\_MAD\_SYSTEM = ssh

Exactly same approach should be made when creating storage for ‘Raw Device Mapping’ (for other storage backends probably too).  
Described issues reproduced on testing system also.  
Could be that 5.8.0 version contains bug related to storage (some default values are not set). Would be nice that support could add their comments regarding that.

---

_[View the full topic](https://forum.opennebula.io/t/image-datastore-does-not-support-transfer-mode-ssh/6975)._