# Abysmal Upload Success Rate

**URL:** <https://forum.storj.io/t/abysmal-upload-success-rate/4943>\
**Category:** troubleshooting\
**Tags:** unraid\
**Created:** [February 29, 2020, 5:05am UTC](https://forum.storj.io/t/abysmal-upload-success-rate/4943 "2020-02-29T05:05:01Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![mi5key](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mi5key/32/1139_2.png) [@mi5key](https://forum.storj.io/u/mi5key)\
**Post date:** [March 3, 2020, 9:33pm UTC](https://forum.storj.io/t/abysmal-upload-success-rate/4943/25 "2020-03-03T21:33:53Z")

</div>

> [@Cyber-Hoarder](#):
>
> To manually replace the -v with --mount, this will require manually setting additional values, doable but would require knowing about the issue and knowing where to look under advanced.

I replaced the -v with --mount via a docker run on the command line. Question is, will this persist in a next reboot? I’m unclear as to where this config would be on unraid but I am investigating when I have time.

My Upload Success Rate has increased to 47.484% after changing.

> [@Cyber-Hoarder](#):
>
> Coming from someone who uses storj in unraid with no issues, my recommendation would be run everything through a cache, never allow HDD’s to spin down and manually start the pod after a reboot to ensure all shares are available.

I don’t have issues with unraid either, aside from the sqlite db corruption which like you said is fixed. I’m very careful with this pod, treating it with white gloves.

---

_[View the full topic](https://forum.storj.io/t/abysmal-upload-success-rate/4943)._