# Node goes offline after updating to 0.34.6

**URL:** <https://forum.storj.io/t/node-goes-offline-after-updating-to-0-34-6/5118>\
**Category:** troubleshooting\
**Tags:** docker, storagenode, unraid\
**Created:** [March 11, 2020, 12:34am UTC](https://forum.storj.io/t/node-goes-offline-after-updating-to-0-34-6/5118 "2020-03-11T00:34:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [March 11, 2020, 2:10am UTC](https://forum.storj.io/t/node-goes-offline-after-updating-to-0-34-6/5118/4 "2020-03-11T02:10:26Z")

</div>

> [@Narvath](#):
>
> the docker is situated on a Unraid machine

> [@Usedserialsdb error: database disk image is malformed](https://forum.storj.io/t/usedserialsdb-error-database-disk-image-is-malformed/2335/28):
>
> Unfortunately Unraid is unreliable platform for the storagenode. The storagenode uses a sqlite databases, and Unraid will damage the sqlite very often because of their bug: Unraid mount user’s filesystem after the docker daemon start The community app for storagenode v3 written by unraid community member uses the -v option instead of --mount and thus loses data every reboot because of p.2 and [difference between -v and --mount options](https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior) You can’t fix the p.2, but can fix the p.1 as describe…

---

_[View the full topic](https://forum.storj.io/t/node-goes-offline-after-updating-to-0-34-6/5118)._