# Node offline internal error

**URL:** <https://forum.storj.io/t/node-offline-internal-error/2118>\
**Category:** troubleshooting\
**Tags:** unraid\
**Created:** [October 7, 2019, 3:25pm UTC](https://forum.storj.io/t/node-offline-internal-error/2118 "2019-10-07T15:25:16Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 8, 2019, 8:20pm UTC](https://forum.storj.io/t/node-offline-internal-error/2118/19 "2019-10-08T20:20:42Z")

</div>

Unfortunately the community made app have a bug. It must use the `--mount type=bind` instead of `-v`  
The second problem - the unraid mounts a disk array after the docker start  
The third problem - the Unraid after update have a bug which leads to corruption of sqlite databases for most of applications which uses the sqlite, include storagenode:

> **[Downgraded back to 6.6.7 due to Sqlite corruption](https://forums.unraid.net/topic/80439-downgraded-back-to-667-due-to-sqlite-corruption/)**
>
> After finding corruption every few days in my docker containers (Plex, Sonarr, and SABnzbd), I finally bit the bullet and downgraded back to 6.6.7. I had been doing google searches for issues with 6.7 and Sqlite, and I ran across one that stated that...

Please, consider to move your node from this platform if it’s possible.

---

_[View the full topic](https://forum.storj.io/t/node-offline-internal-error/2118)._
